Gateway Issues

The gateway is the Rust backend component that routes messages between the console, agents, and external channels. When the gateway has issues, agents may appear unresponsive or disconnected.

Connection Issues

Symptom: Agents show “Disconnected” status or messages are not being delivered.

Solutions

1. Refresh the page — This re-establishes the WebSocket connection to the gateway.

2. Check your internet connection — The gateway requires a stable connection. Verify you can reach other websites.

3. Try again after a moment — The gateway may be temporarily restarting or under maintenance.

4. Clear browser cache — Cached connection state can sometimes cause issues. Hard refresh with Ctrl+Shift+R or Cmd+Shift+R.

Response Issues

Symptom: Messages send but responses never arrive, or responses are cut off mid-stream.

Solutions

1. Check the model — If the AI provider is experiencing issues, responses may fail. Try a different model or provider.

2. Check the audit log — Look for error events that indicate what went wrong. The audit log shows tool invocations, provider errors, and other details.

3. Simplify the prompt — Complex prompts with many tool invocations may exceed timeout limits.

4. Reduce concurrent activity — If multiple agents are processing messages simultaneously, responses may be slower.

Timeout Issues

Symptom: Responses take too long and time out, or are cut off with an error.

Agent Response Timeout

The gateway waits for the agent to respond before timing out. For complex requests, the model may need more time.

Solutions:

1. Use a faster model — Faster models (Claude 3.5 Haiku, GPT-4o Mini, GLM-4.7 Flash) produce responses more quickly.

2. Check AI provider latency — The response time depends on the AI provider. Check their status page for ongoing issues.

3. Reduce context — Large conversation histories increase request size and response time. Start a new conversation for fresh context.

Tool Execution

If an agent is using tools (web search, code execution), each tool invocation adds time to the response. The audit log shows which tools were invoked and how long each took.

Channel Connection Issues

If channels (Discord, Telegram, Slack) are not working:

1. Verify credentials — Check that the bot token or OAuth token is valid and not expired.
2. Check the audit log — Look for channel error events.
3. Reconnect the channel — Remove and re-add the channel in the Channels page.
4. Check the platform’s status — Discord, Telegram, or Slack may be experiencing outages.

When to Contact Support

If none of the above solutions work:

1. Note the exact error message.
2. Check the audit log for relevant error events.
3. Note the model and provider you were using.
4. Report the issue via our community channels on X.