Description
When using CodeIsland with a Remote SSH host:
- Claude Code sessions are displayed correctly
- Claude Code
PermissionRequest events correctly trigger an approval popup in CodeIsland
- Approve / Deny works as expected for Claude Code
- Codex CLI sessions are also displayed correctly
- However, when Codex CLI requires user approval, the approval prompt only appears in the remote terminal and no approval popup is shown in CodeIsland
Since Claude Code approval works correctly on the same remote host, the Remote SSH connection and remote socket tunnel appear to be working properly.
The issue seems specific to remote Codex approval handling.
Steps to reproduce
- Add and connect to a Remote SSH host in CodeIsland
- Start Codex CLI on the remote server
- Ask Codex to perform an action that requires user approval
- Codex shows an approval prompt such as Allow / Deny in the remote terminal
- CodeIsland does not show the corresponding approval popup
On the same remote server, Claude Code approval prompts work correctly in CodeIsland.
Expected behavior
When remote Codex CLI requests approval, CodeIsland should behave similarly to remote Claude Code:
- Forward the approval request to the local CodeIsland app
- Show the approval UI
- Allow the user to choose Allow / Deny / Always Allow
- Send the decision back to the remote Codex CLI
Actual behavior
CodeIsland can display the remote Codex session and its status, but approval requests are not surfaced in the local UI.
The approval has to be handled manually in the remote SSH terminal.
Additional context
From the current implementation, it looks like remote Claude Code installs a PermissionRequest hook, while the remote Codex integration mainly handles events such as SessionStart, UserPromptSubmit, and Stop.
CodeIsland already appears to have richer Codex approval / user-input support through codex app-server for local Codex sessions.
So I wanted to confirm whether approval handling for Remote SSH + Codex CLI is currently unsupported, or whether this is a bug.
If it is not supported yet, it would be great to have remote Codex approval support added.
Environment
- CodeIsland version:
- Codex CLI version:
- macOS version:
- Remote server OS:
The Remote SSH connection uses ProxyJump, but Claude Code approval works correctly on the same host, so the SSH connection itself appears to be fine.
Description
When using CodeIsland with a Remote SSH host:
PermissionRequestevents correctly trigger an approval popup in CodeIslandSince Claude Code approval works correctly on the same remote host, the Remote SSH connection and remote socket tunnel appear to be working properly.
The issue seems specific to remote Codex approval handling.
Steps to reproduce
On the same remote server, Claude Code approval prompts work correctly in CodeIsland.
Expected behavior
When remote Codex CLI requests approval, CodeIsland should behave similarly to remote Claude Code:
Actual behavior
CodeIsland can display the remote Codex session and its status, but approval requests are not surfaced in the local UI.
The approval has to be handled manually in the remote SSH terminal.
Additional context
From the current implementation, it looks like remote Claude Code installs a
PermissionRequesthook, while the remote Codex integration mainly handles events such asSessionStart,UserPromptSubmit, andStop.CodeIsland already appears to have richer Codex approval / user-input support through
codex app-serverfor local Codex sessions.So I wanted to confirm whether approval handling for Remote SSH + Codex CLI is currently unsupported, or whether this is a bug.
If it is not supported yet, it would be great to have remote Codex approval support added.
Environment
The Remote SSH connection uses
ProxyJump, but Claude Code approval works correctly on the same host, so the SSH connection itself appears to be fine.