Every project-scoped call lands in an organization and project. Context resolution combines the current invocation with saved CLI state to choose that target.Documentation Index
Fetch the complete documentation index at: https://docs.metabind.ai/llms.txt
Use this file to discover all available pages before exploring further.
Resolution Model
- Values passed to the current command apply only to that command and take priority.
- Saved values from
metabind usefill in the rest. - Project-scoped commands need a complete org and project.
- Bootstrap commands can run before a complete project context exists.
- Metabind does not read project config from the current repository.
metabind use.
Saved Context
metabind use records the active project scope for later commands. It can update the full scope or switch one part of it.
When a project is saved without an organization, the CLI can try to find the owner by checking the organizations your account can access. If discovery cannot complete, save the missing organization before running project-scoped commands.
Clearing context removes the saved org and project while leaving identity and credentials in place.
Credentials
Operator CLI auth and project API keys serve different callers.- CLI operator auth is for people and command-driven automation.
- MCP hosts use project API keys.
- Rotating a project API key does not affect the CLI session.
- Logging out of the CLI does not delete MCP host credentials.
Parallel Runs
Processes running under the same OS user share the default Metabind config directory. UseMB_CONFIG_DIR to isolate concurrent work on different projects or accounts.
Each isolated config directory has its own saved context and auth store, preventing one run from changing another run’s active project.
Inspecting Context
metabind status shows CLI auth state, saved context, and project reachability. For a deeper project audit, use metabind doctor; it is read-only and returns findings with repair guidance.