What you can do to a station
Open an adopted station in the console and you get a set of panels. Which ones appear depends on what the station declares it can do.
Capability gating
Section titled “Capability gating”Several operations are gated on a capability the station declares:
| Capability | Gates |
|---|---|
fs.write |
Writing to the filesystem |
terminal |
The interactive shell |
lifecycle |
Start, stop, restart |
cleanup |
Planning and applying a disk reclaim |
changeset |
Reading the working-tree diff |
A request for a capability the station has not declared is refused at the hub, without contacting the node. Reading is not gated this way — the read paths are available wherever the station supports them.
Browse the tree, preview a file, jump straight to a path with quick-open, and edit where
fs.write is declared.
Under the hood these are the node’s own verbs — fs.list, fs.read, fs.write,
fs.mkdir, fs.move, fs.delete — executed on the host by the local agent, never by the
hub reaching in.
Tail the harness’s logs live. The node knows where each harness keeps them, because the descriptor for that harness knows.
Terminal
Section titled “Terminal”A real interactive shell on the host, brokered through the hub. Requires the terminal
capability.
Config
Section titled “Config”Read and edit the harness’s own configuration file, in place and in its own format — AgentPod does not convert it to something else and hand it back.
Health
Section titled “Health”What the station reports about itself, asked live. The console shows this next to the node’s own online/offline state, which is a different question: a node can be perfectly online while a station on it is not.
Lifecycle
Section titled “Lifecycle”start, stop, restart. Requires the lifecycle capability.
Every lifecycle action is written to the audit trail before it is dispatched, not after. An action that is attempted and fails still leaves a record — an audit log that only lists successes is one that hides exactly the events you most need.
The response is the station’s health after the action, so you can see the result rather than assume it.
Cleanup
Section titled “Cleanup”Two steps, deliberately:
POST /api/stations/:id/cleanup/plan what would be removed, and how much it freesPOST /api/stations/:id/cleanup/apply do itThe plan is shown to you first. Nothing on disk is touched until you apply it. Requires the
cleanup capability.
Changesets
Section titled “Changesets”What the agent has actually changed in its working tree — status for the summary, diff
for the detail. Requires the changeset capability.
This is the panel for the question “what has this thing been doing”, answered from the files rather than from what the agent says about itself.
Activity
Section titled “Activity”The audit trail for the station: what was done, when, and by which principal.
Where a station has a Matrix identity, talking to the agent is messaging it. See Stations for the two identity modes.
Posture
Section titled “Posture”A banner surfaces exposure problems found on the host — the same checks
apn scan runs locally.
- Attaching an editor — your own editor against a remote station
- Checking for exposure