AI 0.1.95 / Support
Troubleshoot AI
Diagnose provider, access, quota, context, and recommendation failures safely.
Provider is not ready
Run the Testing connection check and ai-setup. A missing provider, endpoint, model, or credential keeps AI unready. For 401 or 403 responses, verify the provider account, API key, endpoint format, and model entitlement. For 429 responses, wait for the provider window or lower site limits.
Endpoint is rejected
Use an HTTPS, publicly routable provider endpoint. Localhost, private network addresses, malformed URLs, and unsafe redirects are rejected by default.
Command is missing or denied
Confirm Social Terminal is active and the current actor matches the AI access policy. Run help ai and ai-status. The server may deny a command even if stale browser markup still displays it.
Context appears wrong
Run ai-reset, confirm short context is enabled only once, and repeat the request in a new terminal session. Context is actor-scoped and expiring; it is not shared durable memory.
Recommendation will not run
Verify AI Pro, guarded runs, the optional allowlist, read-only classification, owning add-on availability, current-user command access, and any required one-time approval. A mutating or browser-only command is intentionally unavailable.
If diagnosis is still unclear, export the sanitized support bundle and include the timestamp and failure class—never the API key or full prompt.