Files, logs, terminal
Browse and edit the workspace, tail logs live, open a real shell — brokered through the hub, executed by the local agent.
Your agents run somewhere — a server, a laptop, a container you spun up last week. AgentPod is where you see those places and reach into them: files, logs, a terminal, health, cleanup. Point it at what you already run.
AgentPod does not run your agents and does not ask you to move them. It ships a descriptor per harness that knows how to ask that harness what it is running, where its config and logs live, and how to start and stop it — wrapping each one's native interface rather than reinventing it.
Each operation is gated on a capability the station declares. A request for one it has not declared is refused at the hub, before anything reaches the machine.
Browse and edit the workspace, tail logs live, open a real shell — brokered through the hub, executed by the local agent.
What a station reports about itself, and start, stop or restart. Every action is written to the audit trail before it is dispatched, not after.
Plan a disk reclaim and inspect the plan before applying it. See what an agent has actually changed in its working tree.
One command on the target host. It downloads the right binary, installs a service, and enrolls with your hub.
# linux and macOS, amd64 and arm64
curl -fsSL https://github.com/SuperJackfruitLabs/agentpod/releases/latest/download/install.sh \
| sudo bash -s -- https://hub.example.com <TOKEN>
Without root, pass --user to install under your login session instead.
Binaries are published for linux and darwin on amd64 and arm64.
apn scan checks the agent runtimes on a host for the two ways they get
taken over: a listener bound to every interface, and credential files other users can
read. It needs no hub, no account and no network, and exits 0, 1 or 2 so it works in
cron.
apn scanA check that cannot determine an answer says so. It is never reported as a pass.
When there is nothing to attach to yet, AgentPod can create the runtime and enroll it for you, on any of these.
The hub is a Bun service over Postgres. The console is a static site. The node agent is a single Go binary. There is no account here to sign up for — clone it, run it, and the fleet is yours.