Skip to Content
TaresSoftware FactoryTroubleshooting

Troubleshooting

Check the setup

tares factory doctor

Run it after crew up, and whenever a station misbehaves. It prints a line for each thing the crew needs and, for each problem, the command that fixes it.

The stations run without their factory skills

The Tares plugin is also installed from the marketplace (tares@tares) at another version, and Claude Code loads that one. Remove it, or update it to the version your tares package ships:

claude plugin uninstall tares@tares

Doctor says when the two differ. When the installed tares is older than the plugin needs, a session says so when it starts: upgrade with uv tool upgrade tares.

crew up or spec says the endpoint does not answer

On your own machine, the crew’s sessions reach Tares through tares mcp. Start it and keep it running:

tares mcp --transport streamable-http

With auth on, start it with TARES_AUTH_TOKEN set. If yours runs elsewhere, set TARES_FACTORY_MCP_URL. On Tares Cloud the endpoint is always running; sign in again with tares login.

The stations use the wrong key

The crew follows your tares login. Doctor shows the key the stations use and the one this terminal uses, by key id, and flags a TARES_AUTH_TOKEN that overrides the saved login.

Language servers

Builders and the reviewer search less when Claude Code can find a definition, its references and its callers through a language server. Doctor reads each handed-over repo’s languages from its manifests, at the repo root or one folder down, and says whether Claude Code has a server for each. A server counts when its plugin is enabled for you and its binary is on your PATH. For a missing one, it prints what to run:

LanguageFound byInstall
Pythonpyproject.toml, setup.py, setup.cfg, Pipfile or requirements.txtnpm install -g pyright, then claude plugin install pyright-lsp@claude-plugins-official
TypeScripttsconfig.jsonnpm install -g typescript-language-server typescript, then claude plugin install typescript-lsp@claude-plugins-official
JavaScriptpackage.jsonthe same as TypeScript
Gogo.modgo install golang.org/x/tools/gopls@latest, then claude plugin install gopls-lsp@claude-plugins-official
RustCargo.tomlrustup component add rust-analyzer, then claude plugin install rust-analyzer-lsp@claude-plugins-official

When only one half is missing, doctor prints only that half. tares factory crew up offers the same install and runs it only on your yes.

A station waits for you

A station that asked for a permission, a prompt or an answer stays stopped until you reply. The console shows it as waiting for you, with its last message and the command that opens it. Open it in a terminal and answer there:

tares factory crew attach <station>

To stop asking for the same thing, allow it as a standing rule from your Home.

A station is quiet or stopped

The watch brings back a station that stops, under the same name. If the watch is not running, start the crew again with tares factory crew up. Doctor warns when idle_wake is on and the watch is not, because nothing would wake the stations then.

When your Claude plan’s limit is full, the crew waits for the reset. Turn on pace to slow the crew before it gets there. Pace the crew

A station runs an older Claude Code

Doctor lists each station’s Claude Code version and warns about an older one. Move every station onto the installed version:

tares factory crew update

Move onto a new Claude Code

cmux says “Waiting for you” after every turn

cmux says it about a minute after each station’s turn ends, even when the station needs nothing. Doctor reads ~/.config/cmux/cmux.json and, while the option is on, tells you to add:

{ "notifications": { "agentIdleReminder": false } }

The option applies to every cmux session, not only the crew’s. Doctor never edits your cmux file.

Still stuck

Write to help@glassflow.ai, book a call , or open an issue .

Last updated on