SSH into any container

Sometimes the browser is the wrong tool. You want your prompt, your shell history, your tmux config, your editor with your bindings. You want to poke at a process the agent doesn’t know about. You want to grep a half-gigabyte log without watching it stream through the UI.

Every workspace container in Loopyard listens on a local SSH port. From your own terminal:

ssh -p 2222 container-name@localhost

You’re dropped into the same session the agent is in. If the agent is running a command and you connect, you see it run; if you tail a file and the agent starts writing to it, you see the writes. It’s a real shared terminal, not a screen recording.

This isn’t a backdoor or an escape hatch. It’s an acknowledgement that people work in terminals and agents work in terminals, and there’s no reason they shouldn’t work in the same one. Edit a file from your shell; the agent sees it. Have the agent edit a file; you see it. The shell is the meeting point, not the agent’s private workspace.