Remote hosts

Your code's machine, first class.

Add an SSH host and the agent runs where the code lives. A small daemon keeps sessions going while you're away and replays what you missed when you reconnect.

Remote machines, first class.

Add an SSH host and BeyDock starts a small daemon there. Sessions keep running when you disconnect, and pick up where they were when you come back.

Remote machines, first class.

BeyDock copies its sidecar to the host and talks to it over SSH. The daemon stays up between connections and replays what you missed. Folders, worktrees and files are the host's, and MCP servers from your Mac reach it through a tunnel.

Better together

Plays well with your tools.

Terminal, changes and a browser sit next to the conversation, so checking the agent's work never means leaving it.

A real terminal in the session's folder, on this Mac or the SSH host.