review · segments

Evaluate Solo's remote agent capabilities and SSH-driven viability

claude 36 events 1 segments master

segment 1 of 1

Determine whether Solo can run or manage coding agents on a remote host via SSH

Done

Conducted read-only steps: read CLAUDE.md, solo.yml, inspected Solo HTTP API discovery file (~/.config/soloterm/http-api.json), ran solo-cli commands, and checked listen address via lsof. Found zero references to remote/SSH/host in the 178KB discovery API model; API bound to 127.0.0.1:24678 only; CORS restricted to loopback origins; spawn endpoint has no remote host field; Solo is a macOS .app with no Linux build. Concluded Solo cannot natively drive remote hosts and SSH is only possible via a local SSH wrapper process, which is fragile for interactive agents.

outcome

Solo is confirmed as a fundamentally local single-machine orchestrator; no remote host or SSH transport exists in its model; remote agents via SSH would require Solo to spawn a local ssh client command, managing only the local PTY.

next steps

—

key decisions

Solo has no concept of remote hosts or SSH; cross-machine coordination is not supported natively.

open questions

Could Solo's API be tunneled over SSH for remote control?
Is there a future Solo Linux build planned?

20 hours ago → 20 hours ago