← ClaudeAtlas

configure-codex-remote-sshlisted

Configure and verify the official Codex app against a paid Terminalbox pane over key-only SSH. Use when a user wants a persistent Codex development host, needs a safe Terminalbox SSH config entry, is troubleshooting Codex remote-host discovery or login-shell availability, or wants to connect an existing Terminalbox pane in Codex Settings → Connections.
Anchras/terminalbox-tools · ★ 0 · AI & Automation · score 73
Install: claude install-skill Anchras/terminalbox-tools
# Configure Codex Remote SSH Help the user connect one paid Terminalbox pane to the official Codex app. Be explicit that Terminalbox is independent from OpenAI: Terminalbox supplies the hosted Linux environment and SSH gateway; the user supplies an eligible OpenAI account or API access. ## Safety boundary - Never read, print, copy, upload, or ask for a private-key value. Work only with its filesystem path and the matching public key. - Inspect existing SSH configuration narrowly. Do not reproduce unrelated host entries or proxy details in the response. - Do not create a key, edit `~/.ssh/config`, replace a known-host entry, open a browser, or start a paid checkout without explicit user approval for that action. - Preserve existing SSH settings. Refuse to overwrite an existing alias unless the user chooses a new alias or explicitly approves the exact replacement. - Treat a fingerprint mismatch as a stop condition. Do not bypass host-key verification. - Do not claim the setup works until both a normal SSH command and Codex availability through the remote login shell have been verified. ## 1. Establish prerequisites Collect or confirm: - the pane slug shown on the Terminalbox dashboard; - a private-key path on the user's computer, without reading the key; - confirmation that the matching `.pub` key was added under Terminalbox Settings → SSH → Inbound access; and - a concrete, unused SSH alias. Default to `terminalbox-codex` when available. If the user has no p