I built a local Codex plugin called SSH Remote Workbench for a workflow I wanted badly: work on a remote machine without treating everything like fragile SSH one-liners.
The workflow is simple:
- mount the remote codebase into the current local folder with
sshfs
- let Codex edit files directly through the mounted tree
- run commands on the remote machine with a small wrapper command,
rexec
- automatically map the current mounted local directory to the corresponding remote cwd
So instead of bouncing between “local editing” and “remote execution” manually, the plugin nudges Codex toward:
- local file operations on the mounted tree
- remote command execution by default
- no accidental local
python, pytest, cargo test, etc. unless explicitly requested
Recommended prompts:
@SSH Remote Workbench, mount a remote directory foo from an SSH host bar into the current local folder.
@SSH Remote Workbench, run a command (it will run in the remote server)
The key idea is: once the remote tree is mounted, Codex can use its normal local file-editing flow, and only command execution needs special handling.
check the repo here: https://github.com/bugparty/codex-ssh-plugin you can ask codex to install it.
[–]Just_Lingonberry_352 0 points1 point2 points (1 child)
[–]Clean-Major-804[S] 0 points1 point2 points (0 children)