Appendix

A. Mode A unavailable surfaces

Mode A is Matcha CLI in this build: local files, and a Provider you bring your own key for. There is no MatchaCode account and no official cloud.

Some command names still parse. They are leftovers in the binary, not procedures. Do not walk through product OAuth, device-code login, in-app update, share URLs, or a plugin marketplace. If a substitute exists, the table names it.

A disabled surface is a hard stop. The CLI does not look up DNS, open HTTP or WebSocket, queue, or retry for it.

What Mode A does teach

Use these. They are the local + BYOK path.

  • Talk to the model through the Provider you configured, and list that Provider’s catalog (cached locally).
  • Store a Provider API key on this machine.
  • Local sessions, workspace, skills, plugins, memory on disk, and MCP servers you configure yourself.
  • Local usage, traces, and crash files.
  • Assistant and tool execution on this machine, including local LSP servers.
matcha login --provider xai

The same shape works for openai, anthropic, ollama, and openai_compatible. That is BYOK. It is not a MatchaCode login.

User-visible names that are not procedures

These entries can still be typed. Treat them as unavailable. Use the substitute when one exists.

NameWhy it is outUse instead
matcha login --oauth / --oidc / --device-auth / --device-codeAccount OAuth and device-code loginmatcha login --provider <id>
/login (typed; omitted from menus)Same; prints BYOK examplesmatcha login --provider <id>
Welcome-screen product OAuth / device-code chromeNo MatchaCode accountProvider key on the welcome configure path
matcha update (and in-app auto-update)No installer or update channelBuild from source
matcha setupRemote config syncLocal ~/.matcha/config.toml / MATCHA_*
matcha share, /share (hidden from CLI and slash menus)No share URL/export, matcha export
matcha workspace (hidden from CLI)No computer hub or remote workspaceLocal /dashboard, matcha worktree
/docs webNo in-app web docs URL/docs in the TUI
/feedback (omitted from menus)No feedback upload
/marketplace, matcha plugin marketplace …No remote marketplaceLocal /plugins, matcha plugin install <path>
/imagine, /imagine-videoMedia tools are not registered
/voice (fail-closed until revealed)No speech-to-text serviceType in the composer
/announcements remote pushNo remote announcement feed. /release-notes is not a substitute/docs and matcha --version
/release-notes / /changelogNo remote changelog; typed command fail-closes and tells you to use /docs/docs and matcha --version
/privacy remote policy / training opt-inNo remote coding-data plane/privacy opens local Settings → Coding data
/usage manageNo MatchaCode bill, subscription, or account usageBare /usage / /cost (local metering)
/flush, /dream inferenceNo memory LLM jobs/memory on/off, /remember, local store
matcha trace without --localNo diagnostic export endpointmatcha trace --local
Web fetch / web search toolsProvider web tools are offUser-configured local MCP, if you need it
Cloud Agent / remote workspaceNo product cloud workspaceLocal /fork, /config-agents, matcha worktree
Conversation cloud syncSessions stay on diskmatcha sessions, /resume
Product relay / headless WebSocket relayNo hosted relaymatcha agent stdio, local matcha leader
Remote skills / chat-mode catalogNo product catalogsLocal /skills
Managed MCP gatewayNo hosted connectorsmatcha mcp, /mcps
Git plugin source (unapproved egress)Remote git plugin install is offLocal plugin path
Remote settings / campaignsNo control plane~/.matcha/config.toml, /settings
Review comment uploadNo commercial account
Telemetry / OTLP / error / heap / auth-diag uploadNo diagnostic exportLocal crash files
HTTP hook URLsUnapproved user egressLocal command hooks (/hooks)
User-configured LSP socketUnapproved user egressLocal LSP servers

Forty-eight surfaces stay off

The table above is the user-visible subset. Forty-eight further surfaces in this build stay disabled. They are not procedures either. Most never appear as commands.

  • Account, device-code, and product-identity login.
  • Remote session lists, conversation sync, and writeback.
  • Share URLs, cloud assistant, remote workspace, and workspace hub (matcha workspace).
  • Product relay and relay session sync.
  • Remote skill catalogs, managed MCP, MCP marketplace, remote git plugin sources, and plugin marketplace.
  • Remote settings, managed config sync (matcha setup), remote chat-mode catalogs, and remote sub-assistant bundles.
  • Feedback upload, review-comment upload, account usage, billing, and subscription chrome.
  • Remote privacy / training opt-in, remote announcements, campaigns, and /release-notes.
  • Trace upload, product telemetry, OTLP export, auth-diagnostics upload, error reporting, and heap-profile upload.
  • matcha update.
  • Arbitrary LSP sockets, speech-to-text, web fetch, web search, image and video generation, HTTP hook URLs.
  • Memory embedding, /dream, and /flush inference jobs.

Related: Configure a Provider (BYOK); Memory; Migrating from Grok Build.