Date: 2026-09-10

Troubleshoot performance and stability

Performance depends on model latency, tool execution, repository size, rendering, MCP servers, and token limits. Diagnose the slow phase rather than disabling safeguards.

Use the current implementation

Use --verbose or --debug for non-secret diagnostics, reduce prompt and attachment scope, avoid unnecessary MCP servers, and inspect tool/runtime timing when available. Check session health before retrying a long operation.

Boundaries and safety

A faster response may omit verification or exceed a token/usage limit. Do not treat a timeout as proof that a tool did not change a file; inspect the working tree and session state.