Agentic Fluidity - OpenCode is OpenClaw for coding

One of the reasons OpenClaw got so popular was how fluidly you can chat with and operate your agents. Pull up your phone, send a quick message on WhatsApp, and you’re in business.

As we focus more on agent orchestration¹ in 2026, I think an important aspect will be access fluidity. How do you hop into your agent’s context from any device, terminal, or IDE and just start coding?

Claude Code supports this in a limited way, while others like Cursor and Codex take a cloud-based approach.

The best option I’ve found for this “on-the-go” agentic coding is an open-source one — OpenCode.

OpenCode - your best “on-the-go” option for agentic coding.

Server-client architecture #

OpenCode uses a native server-client architecture. You can simply spin it up in a regular terminal tab, just like claude or codex.

But the power move is running it as a server and connecting multiple clients.

A client can be your terminal tab, a mobile device, or a desktop computer. Each terminal tab becomes a new, isolated CLI session that connects to the server.

Couple this with Tailscale, and you can securely connect to a dev machine running an OpenCode server from anywhere.

Getting started #

I’d start by using opencode like a regular CLI tool. Once it feels familiar, switch to server/web mode.

# advertises server as opencode.local
opencode web --mdns

# attach to a session
# equivalent to starting a new claude code session
opencode attach http://opencode.local:4096 --dir /path/to/project

The beauty is you can open that opencode.local URL in any browser, and it’s fully synced.

Credit to my co-host Iury for tooting the OpenCode horn early, and my Instacart colleague Spencer for questioning my luddite tmux ways.²

I’ll write a future post singing OpenCode’s other praises. For now, if you’re exploring the bleeding edge of agent access fluidity, don’t sleep on it.