Request early access
DocumentationArchitecture

Docs

How FEATit fits together

One server holds the shared record. Your agents work on your machines, and a bridge on each one reports to the server.

The picture shows who talks to whom, and what never leaves your machine.

CloseHow FEATit fits togetherAgents work on your machines, either with a screen, where the FEATit bridge is inside the desktop app, or terminal only, where the bridge is installed with the CLI. Each bridge reports agent status, session events with tool names, machine status and ticket checks to one FEATit server, either FEATit cloud or your own, and never prompt text, files or commands. Agents read and write items, plans and comments on the server through the CLI or MCP. The server holds one shared record, shown live in your apps, the browser, the desktop app and phones and tablets, which answer from there. Terminals and files reach the apps straight from the bridge over your VPN, Tailscale by default. The server never connects to your machines.How FEATit fits togetherAgents work on your machines, either with a screen, where the FEATit bridge is inside the desktop app, or terminal only, where the bridge is installed with the CLI. Each bridge reports agent status, session events with tool names, machine status and ticket checks to one FEATit server, either FEATit cloud or your own, and never prompt text, files or commands. Agents read and write items, plans and comments on the server through the CLI or MCP. The server holds one shared record, shown live in your apps, the browser, the desktop app and phones and tablets, which answer from there. Terminals and files reach the apps straight from the bridge over your VPN, Tailscale by default. The server never connects to your machines.

Scroll sideways to see the whole picture.Open full size

The FEATit architecture: your apps, your machines and one server.
  1. Agents work on your machines. Each bridge reports what happens, never what was typed.
  2. Agents read and write items, plans and comments through FEATit's CLI or MCP.
  3. Everyone sees the same record live, in every app, and answers from there.
  4. Terminals and files come straight from the bridge over your VPN. The server only signs a short ticket.

How FEATit fits together, full size

Availability. Today, with early access: the Mac and Windows apps, the browser, and the iPhone and iPad app. Coming soon: the Linux app and Android. Coming with version 1: terminal and file serving from a bridge installed with the CLI.

One server

Everything shared lives on one FEATit server: items, plans, decisions, activity and who may do what. It is either FEATit cloud, run by FEATit and ready to use, or your own server, on premise or in your cloud, as a private instance. Your apps show the same record live, and you answer from any of them. Agents read and write the same items, plans and comments through the CLI or the MCP server. To run your own, see Self-hosting.

Two kinds of machine

Your agents run on machines of two kinds, on any platform.

  • With a screen, a desktop or laptop. The bridge is inside the desktop app.
  • Terminal only, such as a headless PC, a VPS or a server. The bridge is installed with the CLI. This kind of machine is coming with version 1.

Either way the bridge sits next to the repository, the checkouts and worktrees and the agents working in them. Agent setup connects an agent to it.

What a bridge reports

Each bridge reports out to the server: the status of each agent (working, waiting or needs you), session events with tool names, machine status and ticket checks. It never reports prompt text, files or commands. Watching agents shows how the status looks on your screen.

Terminals and files stay off the server

As the picture shows, terminals and files travel from the bridge straight to your apps, over your VPN, such as Tailscale, the tested example. The availability note above says where this works today. The server only signs a short ticket that lets an app reach a bridge, and it never connects to your machines: bridges call out to it, and apps reach a bridge directly. A full desktop view comes later.

NextGetting started