Web UI
The capa server serves a local Web UI (default http://localhost:5912) for credentials, project configuration, and day-to-day browsing of what capa manages. capa install opens it when secrets are missing; you can also open it whenever the server is up (capa start / capa status).
What you can do
Section titled “What you can do”| Area | Use it for |
|---|---|
| Credentials | Fill ${VarName} prompts; review stored project secrets |
| Capabilities editor | Edit skills, servers, tools, rules, hooks, sub-agents (including their provider targets), plugins, and related sections without hand-editing YAML alone |
| Plugin-owned rows | Entries unpacked from plugins can appear locked in lists so you do not casually edit plugin-owned items |
| Servers and tools | Turn MCP servers on or off, see which tools each server exposes, and check token savings; see Servers and tool exposure |
| Registries | Browse/search registries; manage adapters (Registries → Manage registries). When browsing from a project, items already in the project show an Installed check instead of Add |
| OAuth UX | Connect git providers and remote MCP servers that need OAuth. If a server needs OAuth, the servers section opens automatically so you can authenticate |
| Activity | Follow agent runs live, inspect traces, files, and skills per run, and analyze process flow; see Activity |
| Project configure / delete | Adjust project settings or remove a registered project from capa’s database |
Servers and tool exposure
Section titled “Servers and tool exposure”Each server card in the project’s tools section shows:
- An on/off toggle. Turning a server off disconnects it from capa; turning it on connects and lists its tools. The toggle lives in the running capa server only: it is not written to the capabilities file, and re-configuring the project (for example
capa install) turns declared servers back on. - Exposure: how many of the server’s tools agents can use (for example “12 of 30 tools exposed”), with each tool marked exposed or hidden according to the server’s expose setting. If the Tools section lists tools for that server, the card shows it as curated, and only those tools are exposed.
- When you add the first Tools entry for a server that currently exposes tools by policy, the UI asks you to confirm, because that switches the server to a curated list and hides its other tools.
The token savings panel estimates tokens saved versus exposing every server tool, based on what agents actually receive from capa’s tool list for the current tool exposure mode. In search mode, skill requires has no effect, so the UI hides the “associated skills” wiring on tools.
Activity
Section titled “Activity”With options.agentActivity enabled (the default), the project’s Activity section shows what agents did in this project:
- Live feed: runs appear as they happen (a live indicator shows the connection; it reads “reconnecting…” when the connection drops). Runs are grouped by the provider’s conversation and each prompt/generation, with the provider and full conversation id in the header.
- Run dialog: open a run to follow its spans live, search its traces, or go full screen. All turns shows every turn of the conversation, including overlapping, parallel, and sub-agent turns.
- Files panel: a tree of files the run read, modified, or deleted. Filter it, expand or collapse folders, and Export the list. Expanding a span highlights its files, and selecting a file highlights the spans that touched it.
- Skills panel: skills whose
SKILL.mdthe agent read or edited. Chips for capa-managed skills are clickable and open the skill’s details; provider built-in skills are not. - Process Analysis tab: a process-mining diagram of tool transitions across the runs in view (drag to pan, scroll to zoom). Export it as PNG, SVG, or Markdown.
Typical credential flow
Section titled “Typical credential flow”- Start or install so the server is listening (install starts it for you).
- Open http://localhost:5912 when capa prompts, or navigate there yourself.
- Enter missing placeholder values (or use
capa install -einstead; see Credentials). - Continue the install; values are stored per project in
~/.capa/capa.db.
Projects vs wrap paths
Section titled “Projects vs wrap paths”Register and configure real project directories (the ones that hold capabilities.yaml after capa init / install).
Wrap workspace paths are refused as projects. Shadow workspaces under ~/.capa/workspaces are for capa wrap only: do not treat them as the project root in the UI or run project-mutating CLI commands from inside them. See Wrap workspaces.