Troubleshooting

Fast Diagnosis

flowchart TD
  A[Chat or provider issue] --> B{Provider saved?}
  B -- no --> C[Add or import a provider]
  B -- yes --> D{Runtime applied?}
  D -- no --> E[bun orginabox runtime status / apply]
  D -- yes --> F{Sandbox healthy?}
  F -- no --> G[Check sandbox logs and compose ps]
  F -- yes --> H[Check gateway or session logs]

Common Issues

Symptom	Likely cause	Fix
Chat opens but no reply appears	The sandbox is down or the worker is not connected	Run docker compose ps, then docker compose logs -f sandbox orginabox-worker
Chat uses the wrong provider or model	A newer provider config is staged but not applied	Run bun orginabox runtime status, then bun orginabox runtime apply
Provider changes saved in the wizard but nothing changed in chat	The runtime bundle still points at the old applied state	Re-apply the runtime before sending another prompt
runtime apply reports no usable default model	No active provider has a default model	Set a default model on the preferred provider, then apply again
runtime status shows warnings	Provider auth or model metadata is incomplete	Fix the provider row, then re-run bun orginabox runtime apply
A gateway receives messages but the agent does not answer	The gateway is healthy, but the session cannot resolve a working runtime	Check bun orginabox runtime status first, then inspect gateway logs

Chat Checks

1. Confirm the sandbox is healthy with docker compose ps.
2. Confirm the runtime is applied with bun orginabox runtime status.
3. Confirm at least one provider is active and has a default model.
4. Retry chat after bun orginabox runtime apply finishes.

Provider Checks

• Use bun orginabox provider list to confirm the provider row exists.
• Use the setup wizard or provider commands to set a preferred provider and a default model.
• If you imported credentials from another tool, re-apply the runtime after the import so the sandbox sees the new auth bundle.

When To Escalate

If bun orginabox runtime apply succeeds but chat still fails, capture the sandbox and worker logs together. The next most common cause is a gateway-specific issue, not the provider runtime itself.