Troubleshooting

Operations1 min read

Diagnose the exact boundary that failed before changing configuration.

Port is busy: Identify the listener before killing it; an expected local service may already be healthy.
Run has no output: Inspect the run event stream, runtime dispatch response, and persisted status separately.
401 or 403: Check actor context, session expiry, API-key scopes, org/project binding, and step-up requirements.
Connector unavailable: Check connection ownership, required scopes, Token Vault exchange, and gateway source health.
Wallet action blocked: Read the capability response, simulation, policy decision, approval expiry, and kill-switch state.
Deploy looks stale: Compare deployed source revision before debugging application behavior.

First diagnostic pass

$ node scripts/setup-agent-local-env.mjs --strict$ pnpm dev:ai:local:check$ pnpm readiness:env:audit

Was this page helpful?