Network interruption

How AgentDock behaves when an agent's own network connection drops mid-session.

Every agent CLI AgentDock connects to — Claude Code, Codex, and Antigravity — makes its own outbound network calls to its provider. AgentDock does not proxy, retry, or intercept those calls; it runs the CLI as a local process (via SDK or PTY session) and surfaces whatever that CLI reports.

Documentation TODO

The exact behavior and UI messaging when an agent's network call drops mid-turn has not been independently verified against the running app for this page. In general, expect whatever error or retry behavior the underlying CLI/SDK itself implements to surface in the conversation, since AgentDock does not add its own network-retry layer on top.

What to check

Confirm the underlying issue isn't local detection or authentication — see Agent CLI not detected and Authentication problems.
Retry the same prompt; each agent CLI's own SDK/transport governs its retry behavior.
If the problem persists, collect diagnostic information and check the raw terminal drawer for the underlying CLI's own error output.