Agents — the catalog
Lists every agent you can reach, running or not.- Search filters by name, description, or tag as you type
- Category filters by tag, built from every tag in the catalog
Your Agents — what you’ve deployed
Lists the containers you manage. The stats bar shows running, stopped, and error counts — click one to filter, click again to clear. Search filters by name or image; sort by Name, Status, or Version. Each card shows the name, status badge, andname:version. Actions depend on state:
Deploy opens a modal for environment variables — import them from saved secrets, or set new ones (which are saved to the agent’s secrets for future deploys). Delete confirms, then stops the container and removes it from the registry.
An agent in an error state shows an inline link to its logs.
Add Agent
Three methods, plus Import from AgentKit marked coming soon.
Upload and GitHub both build the container image first — watch progress in Builds. Failures show an error in place of the redirect.
The agent card
Opens from Details in the catalog or an agent’s name in Your Agents. The top shows name, avatar, version, tags, and description. Header actions: Restart and Stop when running, Delete, and Start session for direct chat. Overview- Skills — each registered skill; one with a sample query opens a chat with it pre-filled
- Quick performance — recent trace count, total cost, p50/p99 latency
- Agent details — provider, project and docs URLs, ID, version, protocol, transport, default I/O
- Capabilities — streaming, push notifications, state history, and current chat reachability
- Access Control — which agents this one may call, and who can access it (public badge, or user/team/department/agent grants)
Builds
Every image build triggered from the browser, in a searchable paginated table. Each row: short build ID, version tag, image reference, status badge (success, building, failed, queued, cancelled), source repo link for GitHub builds, and start time. Opening a build shows a summary, a numbered step breakdown with durations when steps are recorded, and log output. Logs stream live while a build is still in building.Related
Agent Development Lifecycle
The same lifecycle from the CLI.
A2A agents and frameworks
What your container must expose.
Chat
Talk to an agent directly or via the orchestrator.
Observability
Traces, logs, and cost over time.
