monoceros open

Attaches an editor to the named workbench over the SSH attach point, or drops you into a shell. The container is already running - open just points your tool at it.

monoceros open <name> <tool>

<tool> is one of:

Tool	Opens
`code`	VS Code, attached over Remote-SSH to the remote `.code-workspace`
`codium`	VS Codium, the same flow via the “Open Remote - SSH” extension
`shell`	an interactive shell in the container (same as `monoceros shell`)

What it does

monoceros apply already wrote an SSH host monoceros-<name> and a per-container key for you. open launches the editor pointed straight at that host and opens the in-container workspace directly - no host or path to type. The transport is portless (it tunnels through Docker), so nothing is published to the host network.

For the manual connect flow, the required extensions and troubleshooting, see the IDE guides.

Prerequisites

code / codium: the workbench must be applied and running (monoceros apply <name>, check with monoceros status <name>) - open attaches to a running container, it doesn’t start one. The container also needs runtime ≥ 1.2.0 (the SSH attach point); refresh an older one with monoceros upgrade then re-apply. The editor and its Remote-SSH extension must be installed.
shell: no extra setup - it brings the container up itself if needed, exactly like monoceros shell.

Windows / WSL

Works from WSL. monoceros apply also writes the Windows-side SSH config and key, and open finds a Windows-installed editor even when it isn’t on the inherited PATH. You need Docker Desktop (provides docker.exe) and the Windows OpenSSH client (bundled since Windows 10).

Examples

monoceros open acme code      # attach VS Code
monoceros open acme codium    # attach VS Codium
monoceros open acme shell     # a shell in the container