Feature Overview
This page maps AgentHub's main capabilities to the problems they solve.
Single-Agent Control Surface
From the Agents page you can:
- create, start, stop, reconnect, and delete agents
- choose
use_existingorcreate_worktree - point execution at the main node or a remote node
- keep one long-lived session instead of restarting from scratch after every browser refresh
Use this path when one person is directly driving one coding or automation session.
Structured ACP Output
AgentHub renders ACP sessions as structured timelines instead of plain terminal logs. That gives you:
- conversation history
- tool-call and command output context
- plan and reasoning segments
- debug and raw-event inspection when something looks wrong
Use this when task review, auditability, or deep debugging matters.
Team Workbench
/teams adds a multi-agent workflow surface with clear role boundaries.
Key concepts:
Conversation(# all) is the shared human-facing threadKanbanis the canonical task laneRunsand debug surfaces are execution artifacts, not the primary planning surfaceAgent ACPlets you inspect a specific member deeply when needed
Use this when planning, implementation, and review should be coordinated rather than collapsed into one session.
Agent Nodes And Actor P2P
AgentHub can register remote execution nodes and route agent execution to them over internal gRPC, while keeping actor control and mailbox delivery on the same p2p-aware control path.
Use this when:
- repositories or compute live on other machines
- you want one main control plane but many execution targets
- node-specific default worktree roots are required
- actor-to-actor coordination should still work even when execution leaves the main machine
Automation And Integration
AgentHub exposes authenticated OpenAPI discovery endpoints for:
- internal tooling
- typed client generation
- contract checks
- operational automation around agents and Teams
Use this when AgentHub needs to plug into a larger engineering system.
Operations And Safety
AgentHub also includes operational guardrails:
- safe-path restrictions for workdirs
- persistent session and history storage
- in-app notifications
- troubleshooting and recovery guidance