// coding agents

RunCode agent plugin

Connect Codex, Claude Code, and your local developer tools to a RunCode cloud workspace. The plugin mints short-lived workspace-scoped SSH access, pins the gateway host key, and keeps the remote work on the cloud machine instead of your laptop.

Codex

Install the RunCode plugin, then ask Codex to connect to a RunCode workspace or configure SSH aliases for Codex App remote projects.

Claude Code

Use the same RunCode plugin from the slash command menu or plain language prompts.

Your tools

RunCode can write reversible SSH config aliases so VS Code Remote-SSH, JetBrains Gateway, git, scp, rsync, and plain ssh connect too.

Install for Codex

Add the RunCode agent plugin marketplace, then install the runcode plugin. Start a new Codex thread after installing so the skill is available.

codex

# add the RunCode marketplace, then install the plugin (one time):
codex plugin marketplace add runcode-io/runcode-agent-plugin
codex plugin add runcode@runcode

First time on this machine? Ask Codex to use RunCode and run runcode login. You click Authorize in the browser; the helper saves the token locally.

Install for Claude Code

In Claude Code, install the same RunCode plugin. The skill appears as /runcode:ssh, and Claude can also invoke it from plain-language requests.

claude code

# inside Claude Code:
/plugin marketplace add runcode-io/runcode-agent-plugin
/plugin install runcode@runcode

# or from a shell:
claude plugin marketplace add runcode-io/runcode-agent-plugin
claude plugin install runcode@runcode

Work through the helper

For a single task, let the agent connect once and route commands through the runcode helper. A successful connect attaches one sticky workspace until you explicitly disconnect.

prompt

You:  spin up my api workspace and run the test suite

Agent:  runcode connect api --start --wait --json
        runcode context --json
        runcode exec -- pytest -q
        87 passed in 12.4s - all green on the workspace.

>Connect to my API workspace and run tests.

>Start my dev server and forward the port.

>Configure SSH hosts for Codex App.

>What is the git status on my workspace?

Use Codex App remote projects

For longer-running Codex App work, configure SSH aliases and add the generated host in Codex App Settings. Codex then runs directly on the remote filesystem and shell.

ssh hosts

runcode login
runcode config-ssh

# then add the generated host in Codex App:
# Settings > Connections > SSH > runcode.<workspace>

The same aliases work with VS Code Remote-SSH, JetBrains Gateway, plain ssh, git, scp, and rsync.

Command cheat sheet

runcode login Authorize this machine in the browser and save an API token

runcode list List your workspaces

runcode connect <ws> Attach a workspace; --start boots a stopped one, --wait blocks until SSH answers

runcode context One-shot digest of cwd, git state, project markers, and tool versions

runcode exec -- <cmd> Run a command on the attached workspace

runcode start <ws> Boot a stopped workspace without attaching

runcode ssh <ws> [-- cmd] Open an interactive shell or run one command on a workspace by name

runcode port-forward <port> Expose a workspace port locally

runcode config-ssh Write SSH host aliases for Codex App, VS Code, JetBrains, git, ssh, scp, and rsync

runcode stop [ws] Power a workspace down and pause compute billing

runcode disconnect Detach the local helper from the workspace

runcode doctor Preflight OpenSSH, token, API base, and reachability

Every command with its flags is in the CLI reference.

Need the lower-level SSH model and security details? See Connect over SSH.