TerminalOs — DevOps skill for Claude Code


---

The problem

You keep four windows open to do one job. A terminal for the shell. A second terminal for `docker logs -f`. A third for `htop`. A browser tab for whatever dashboard someone installed on the box. Each of them logs in separately, each one asks for the key passphrase again, and none of them knows what the others are looking at.

Phosphor opens **one SSH connection per host** and multiplexes everything through it — the interactive shell, container logs, `docker` commands, `/proc` snapshots, SFTP transfers, port forwards. One login. One tunnel through your proxy. One place where the state lives.

And because that state is already in the app, it also exposes an **MCP server**: Claude Code and Claude Desktop can use your servers through your connections, your keys and your access policy — with every call written to an audit log.

---

What it does

Docker, without leaving the terminal


The container list is a sidebar, not a separate app. Inspect, stats, mounts, environment and live logs with `--tail` and a filter, streamed over the SSH connection you already have. Environment values whose name looks like a secret (`PASS`, `KEY`, `TOKEN`, `SECRET`) are masked in the UI and never copied into the audit log.

No Docker Engine API to expose, no socket to tunnel: it shells out to `docker` with JSON output, which works on every box where Docker already runs.

Metrics that cost one channel


Per-core load, memory with the cache br