Remix.run Logo
▲ afruitpie 7 hours ago

Native apps connecting to the OpenCode server is a great way to run sessions on remote hosts!

I wish Claude Code would adopt the same model. The desktop app deploys a separate engine that restarts and clobbers long-running sessions upon reconnect (Remote Control is their recommended solution but requires a Claude.ai account).

I’ve been vibe coding a native macOS Claude Code app that spawns a server that wraps Claude Code on remote hosts, but the UX and features are always lagging behind.

▲ghboo0927 an hour ago | parent | next [-]

Claude Code already has a server mode. The difference is that it connects through Anthropic rather than via a local socket.

▲avereveard 7 hours ago | parent | prev | next [-]

Claude code agents have a protocol that's usable for the same purpose it just listen locally but it's usable i have my own claw-like that has options for claude, codex, and pi (my subscription, wife subscription, and i got a yearly sub on glm when it was cheap)

▲nijave 4 hours ago | parent [-]

ACP?

▲dofm 6 hours ago | parent | prev | next [-]

I was experimenting with Paseo for this.

The Opencode desktop app could already connect to a remote web session; does it now talk to the server directly?

▲awkii 2 hours ago | parent | prev [-]

I've developed something similar for personal use. A harness who's only job is to delegate to other harnesses (i.e: AntiGravity, Codex, Claude Code, Hermes) to create an opencode-web-like interface across multiple hosts.

For Claude Code, don't use remote-connections. Your best option is to look at how the closed-source VSCode plugin interfaces with Claude Code. The way it works is that it reads files directly. This API, although unofficial, is likely very stable, because an old VSCode extension still has to interact with new version of Claude Code.

If there's any interest in this sort of thing, maybe I'll open-source it. I would have to cleanup the slop though.