Summary
Agent status rows for Codex, Amp, and Droid never appear in the worktree task tree when the workspace is an SSH remote. The same agents show up correctly when the project is local. Claude Code and Hermes do show up over SSH, so the SSH link itself is not fully broken — it looks like the per-agent hook status is not being routed back through the remote relay for some agents.
Environment
- Mode: SSH remote workspace (agent processes run on the remote host, Orca desktop is local)
- Orca desktop:
1.4.120.0 on Windows 11 25H2 (local)
- Remote host: Linux (
x86_64, Ubuntu, kernel 7.0)
- Codex CLI:
codex-cli 0.142.5
- Amp:
0.0.1783081993-g921ca9
- Claude Code:
2.1.199
Expected
Codex, Amp, and Droid sessions running in an SSH-remote worktree appear as agent rows in the worktree card / task tree, with live status (working / done / prompt preview), the same as they do locally.
Actual
- ✅ Claude Code — row shows, live prompt/status update correctly (over SSH)
- ✅ Hermes — row shows
Done / status (over SSH)
- ❌ Codex — no agent row appears at all
- ❌ Amp — no agent row appears at all
- ❌ Droid — no agent row appears at all
Locally (non-SSH) all of these show correctly.
Notes / suspected area
From the public source, agent status normally arrives via the per-agent hook services (src/main/codex/hook-service.ts, src/main/droid/hook-service.ts, src/main/amp/…, etc.) POSTing to the local listener. Over SSH this is instead routed through the relay (src/relay/agent-hook-server.ts, src/main/ssh/ssh-relay-session.ts, REMOTE_AGENT_HOOK_ENV, agent-hook-relay, per docs/design/agent-status-over-ssh.md). Because Claude/Hermes work but Codex/Amp/Droid don't, the failure looks specific to how those agents' hooks are installed/trusted or routed on the remote side — e.g. Codex requires a managed CODEX_HOME + a trust entry in config.toml, which may not be getting set up on the remote.
Repro
- Open an SSH remote workspace / worktree in Orca (Windows 11 desktop → Linux remote host).
- Launch Codex, Amp, and Droid sessions in that worktree (through Orca).
- Also launch Claude Code (for comparison).
- Observe the worktree card / task tree: Claude gets an agent row; Codex, Amp, and Droid do not.
Happy to grab logs or check hook-install status on the remote if you tell me where to look.
Summary
Agent status rows for Codex, Amp, and Droid never appear in the worktree task tree when the workspace is an SSH remote. The same agents show up correctly when the project is local. Claude Code and Hermes do show up over SSH, so the SSH link itself is not fully broken — it looks like the per-agent hook status is not being routed back through the remote relay for some agents.
Environment
1.4.120.0on Windows 11 25H2 (local)x86_64, Ubuntu, kernel 7.0)codex-cli 0.142.50.0.1783081993-g921ca92.1.199Expected
Codex, Amp, and Droid sessions running in an SSH-remote worktree appear as agent rows in the worktree card / task tree, with live status (working / done / prompt preview), the same as they do locally.
Actual
Done/ status (over SSH)Locally (non-SSH) all of these show correctly.
Notes / suspected area
From the public source, agent status normally arrives via the per-agent hook services (
src/main/codex/hook-service.ts,src/main/droid/hook-service.ts,src/main/amp/…, etc.) POSTing to the local listener. Over SSH this is instead routed through the relay (src/relay/agent-hook-server.ts,src/main/ssh/ssh-relay-session.ts,REMOTE_AGENT_HOOK_ENV,agent-hook-relay, perdocs/design/agent-status-over-ssh.md). Because Claude/Hermes work but Codex/Amp/Droid don't, the failure looks specific to how those agents' hooks are installed/trusted or routed on the remote side — e.g. Codex requires a managedCODEX_HOME+ a trust entry inconfig.toml, which may not be getting set up on the remote.Repro
Happy to grab logs or check hook-install status on the remote if you tell me where to look.