Troubleshooting

Available today

Most problems are wiring problems, and most wiring problems announce themselves in one command.

Start with mla doctor

mla doctor

doctor is the first move for anything that feels off. It reports the two lifecycles separately, so you can tell which one is broken:

• Workspace binding: is this folder activated and bound to a workspace?
• Session capture: is capture active, or muted?

If doctor is clean, the connector is wired correctly and the issue is elsewhere. If it flags something, fix that first before chasing anything downstream.

The MCP server is not visible in Claude Code

The agent queries governed memory through the MCP server. If it cannot:

• Confirm the server is configured with mla mcp as its command, in your Claude Code MCP config.
• Confirm you are logged in (mla whoami) and the folder is activated (mla workspace show). The MCP server authenticates as you and is scoped to the bound workspace, so both must be true.
• Restart the Claude Code session after adding the server, so it picks up the new MCP configuration.

Note

A GUI-launched agent can have a different PATH than your terminal. If mla runs in your shell but the agent cannot find it, make sure the mla binary is on the PATH the agent actually inherits.

Injection is missing something I expected

If a decision you think is settled is not showing up in context, it is almost always still pending review. Injection only carries trusted knowledge.

• mla status shows the current scan-cache counts, including how many pending items are waiting.
• Open mla review and accept the item. Once accepted, it is injected. See Reviewing & promoting knowledge.

A command errors right after I logged in

If every command starts failing right after a successful mla login, check for a shared-key control token set in your environment. With a user-token session on disk, that is a deliberate hard error rather than a silent identity downgrade. Unset the variable, or run mla logout first. See Configuration & privacy.

After a binary upgrade, hooks behave oddly

Run mla rewire. It re-installs the hooks and wiring idempotently and needs no token. mla upgrade --check tells you whether a newer signed release is available.

Capturing a report for an issue

mla debug bundle --trace-id <id> writes a local, inspectable zip for a specific trace so you can attach it to an issue by choice. Nothing uploads, and raw payloads are excluded unless you explicitly include them.

Uninstalling cleanly

mla uninstall

This removes the entire local footprint: ~/.meetless, the Claude Code hook and MCP entries, and the /mla skill. It prints how to remove the binary itself. It is local only; server-side data and other repositories’ workspace markers are left untouched. Use mla uninstall --dry-run first if you want to see what it would remove.