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, 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 |
| Registries | Browse/search registries; manage adapters (Registries → Manage registries) |
| OAuth UX | Connect git providers and remote MCP servers that need OAuth |
| Activity / tool-call traces | Inspect recent tool calls and activity for debugging |
| Project configure / delete | Adjust project settings or remove a registered project from capa’s database |
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.