Every agent,
every host,
one view.

Development is distributed. Its monitoring is not.

A single engineer now runs several agents concurrently, across more than one machine, against more than one metered subscription. Each agent reports only inside its own window, on its own host, and none of them signals completion, failure or a request for input outside it.

The cost is not compute. It is supervision overhead — the repeated manual checks, and the interval between a session halting and the operator noticing. Archipelago removes both by presenting the full estate in one place.

Every session, on one line.

A compact indicator reports the number of active sessions. Expanding it lists each one: the agent, the task, the host, the project and its elapsed time. The panel can be pinned or repositioned. Sessions are removed on completion, so the list reflects current state rather than accumulating history.

Native integration, no instrumentation

Archipelago reads each agent from the store it already maintains. Nothing is installed into the agents, no wrapper process is required, and there is no plugin to be invalidated by an agent release.

Admission control. Freeze suspends the admission of new sessions while continuing to track those already listed; scanning resumes on an explicit action. The setting persists across restarts.

Notifications that resolve to a location.

An alert that reports only that something requires attention still leaves the operator to locate it. Archipelago renders its own notifications adjacent to the indicator, and selecting one navigates directly to the originating tab or conversation — resolved by exact identifier rather than by matching window titles.

Remaining quota, and continuity when a plan is exhausted.

Each subscription is reported as remaining capacity rather than consumption to date. Claude, GPT and Codex, GLM, Kimi and Antigravity are supported directly, alongside a generic JSON definition for any provider exposing a quota endpoint — so adding a provider does not require a new release.

Archipelago operates against subscriptions you already hold, on your own hardware, under your own credentials. It does not resell capacity, share accounts between users, or route work through a third party.

It observes. Nothing leaves.

Archipelago reads the state your agents already keep, and that is the whole of its access. It does not act on your behalf, it does not require an account, and it reports nothing to anyone.

Windows. Linux. macOS Soon

Corporate licensing and deployment.

Team size, the agents in use, the number of hosts, and any network restrictions applying to them. That is normally sufficient for a specific response and an accurate quotation.