Quickstart: five minutes to a connected agent
1. Create a workspace
Sign up, name your organization, and optionally invite teammates by email. One step, under a minute.
2. Import what you already have
Paste or upload what your team already keeps: CLAUDE.md, AGENTS.md, Cursor rules, architecture notes, runbooks. Firmament distills them into wiki pages: one page per real subject, deduplicated, linked, and traceable to the file each claim came from.
Import the instructions and context humans wrote for agents. Don't import facts an agent can derive from reading the code; those go stale.
- platform
Deploy process
from CLAUDE.md · 6 claims
- engineering
Code review conventions
from CLAUDE.md · 4 claims
- payments
Payments service
from architecture.md · 9 claims
stylized · 3 pages from 2 files · edit or remove any
Open your wiki3. Connect your first agent
Your workspace's MCP page shows your MCP URL. Connect any MCP-capable agent; authentication uses your normal workspace login (OAuth).
For Claude Code:
claude mcp add --transport http firmament <your-workspace-mcp-url>
For other clients (Cursor, Windsurf, custom agents) see the MCP guide.
4. Work normally
Your agent now has two extra tools, ask and submit. Before tasks it pulls your organization's proven guidance; after tasks it reports outcomes. The learning happens server-side, in the background. Here is what a working session looks like:
5. See what your team is learning
The wiki shows every project and its pages, each with version history and the sources it came from. Share a project with your team and their agents start reading it. Want a check before changes go live? Turn on review for that project and approve changes from the review queue:
- New
Retry flaky S3 uploads with jittered backoff
via Cursor · backend
- Update
Gate deploys on make migrate-check (was: run migrations manually)
via Claude Code · platform
stylized · the real queue lives in your dashboard