npx foundry-design statusStatus reports configuration, installed MCP version, runtime health, and the live listener as separate checks. It never calls a configured server connected until the active session has received a listener heartbeat.
npx foundry-design doctor --repairnpx foundry-design resetFoundry configured the wrong folder
Current Foundry refuses to configure a home folder and searches upward for the nearest real project. Open the intended project folder, then run the reset command. It refreshes project and shared connections together.
Doctor shows two different Foundry versions
Run npx foundry-design reset from the project. It removes Foundry-owned legacy project MCP references, refreshes the shared machine bridge, and preserves files you customized.
Foundry does not open
Run the doctor command from the project root. Confirm Node.js 20.9 or newer is installed and check whether another Foundry runtime is already using port 4387.
The preview opens without Foundry controls
Restart the coding agent after setup, then start a new Foundry session. The authenticated preview URL must include the Foundry session parameters.
Apply with agent stays Queued for agent
The reviewed batch is stored locally because no coding agent is listening. Restart the agent, reopen the same project, and ask it to start Foundry and keep listening. The existing run remains available and will be claimed after reconnecting.
Handoff received does not progress
Foundry delivered the reviewed batch, but source editing has not started yet. Use Reconnect agent or restart the listener in the same project. An abandoned claim expires safely, returns to the queue, and cannot be updated by the stale claimant.
The agent stopped during source work
Foundry preserves the same run in Needs attention instead of silently repeating a partial edit. Choose Resume with agent. The next listener will claim that same run and reinspect the current source before continuing.
Claude is configured but Foundry tools are missing
Run the status command first. It checks the actual listener separately from configuration and reports invalid MCP configuration shapes. After installing or updating the Claude Code plugin, run /reload-plugins. After installing the Claude Desktop extension, begin a new task because an existing task cannot gain newly installed MCP tools.
The agent plugin updated but this task still cannot see Foundry
Agent tools are loaded when a task begins. Reload plugins where the host provides that action, then open a new task in the same project folder. Your local Foundry project and queued review state remain available.
I need to share a support report
Open the Foundry status menu and choose Copy diagnostics. The copied report contains product version, theme, connection state, counts, and run state. It excludes project content, paths, selectors, session IDs, tokens, and preview values.
Setup reports integration pending
Foundry could not find a safe supported web entry, so it opens a loopback-only Basic preview. Use the generated adapter guidance when you need exact source mapping and Apply with agent, then run doctor again.
A change cannot be included
The rendered element has not been mapped precisely enough. Choose the intended source mapping in Review before sending the change to the agent.
Verification needs attention
Review the requested and rendered values. Foundry waits for explicit retry authorization and never applies another correction automatically.