Where things run

What stays on your computers, what the PogCode server keeps, how your account state moves between the two, and who bills the models.

A Computer is one machine you installed PogCode on. Your files, your provider logins, the agent processes and your tools stay on it. Connecting more computers gives your account more places to run, not more copies of your data.

A direct connection, not a relay

Your browser connects straight to the Computer that holds the work, over a WebRTC peer connection; no relay carries your data. On the Computer itself, or on its local network, the connection stays local. When a network cannot make a direct connection, PogCode says so once instead of retrying forever. The browser also keeps a local copy of what it last saw, so a reload paints that copy at once and reconnects behind it, fetching only the changes since.

What stays on your computers

• Project files, working trees and every Thread's working state
• Your Claude, ChatGPT and API logins, and the agent sessions that use them
• Claude Code and Codex processes, terminals, language servers and the documents you edit
• Installed Skills and running MCP servers
• Secret values and MCP OAuth tokens

What the PogCode server keeps

• Your sign-in and the list of approved Computers
• Billing, if you pay for the service
• Signed release information for updates
• The handshake that introduces a browser to a Computer — never the data that follows
• The public catalog of Skills and MCP servers, copied from Skills.sh and the MCP Registry

How account state moves

Conversations, Agent definitions and configuration are signed events that travel directly between your Computers; the server is not involved. Any up-to-date Computer can show them, while files, diffs, Checkpoints, code intelligence and terminals still come from the Computer that owns them. Secret values never travel at all — only their names and types do. A Computer that was offline cannot overwrite newer state: when it comes back, it adds only what the account does not already have.

Replication keeps you going if a device is lost, once another device has the events. It is not a backup: export, retention and restore are separate, explicit actions.

Model usage and billing

Models are billed by your provider, on the subscription or keys you already have. Claude Code and Codex sign in with your provider on your own computer. PogCode is not in that path and adds no markup.

Updates

The daemon fetches a signed release index over HTTPS, checks its sequence and signature against a pinned key, downloads the exact version and switches to it. If the new version does not start healthy, it rolls back both the binary and its database.