Compare · CLAUDE.md
Use a CLAUDE.md for one person in one repo. Use Firmament when a team needs knowledge that learns from what works, stays current on its own, and is shared under your control.
Firmament isn't a replacement for your CLAUDE.md or AGENTS.md. Keep them. Firmament is where they go next: import what you already wrote, let your teammates' agents add to it, and give every agent knowledge it can write to and read back, not just a file it's handed.
Free for a team of three. 30-day trial of everything.
| A CLAUDE.md file | Firmament | |
|---|---|---|
| Free, and lives in your git repo | ✓ | Import it in five minutes |
| Set up in seconds | ✓ | Five minutes, one MCP URL |
| Import CLAUDE.md, AGENTS.md, or Cursor rules | it is the file | ✓ |
| Learns from what actually worked in production | – | ✓ |
| Signals: reinforces rules that keep passing, retires ones that break | – | ✓ |
| Agents write back what they learn (a living wiki) | – | ✓ |
| Stays current as facts change, with no one editing the file | – | ✓ |
| Shared across the whole team, with human approval | – | ✓ |
| Spans many repos and tools, not one folder | – | ✓ |
| Works in Claude Code, Cursor, any MCP client | copy-paste per tool | ✓ |
| Secrets and personal data screened out at write time | – | ✓ |
No, and you shouldn't. Import your CLAUDE.md, AGENTS.md, or Cursor rules in five minutes and keep editing them in git if you like. Firmament reads what you already wrote and makes it the shared, living copy every agent on the team learns from. The file was the seed, not something to throw away.
A file is a snapshot, frozen until someone edits it. Firmament watches what actually happens: a rule like "run migrations before deploying payments" gets reinforced every time it works and retired the moment it stops being true. And it isn't read-only. Your agents write back what they learn, building knowledge pages the whole team can use. The knowledge carries a track record, not just an author.
That's the point of it. Your CLAUDE.md helps your agent in your repo; the lesson your teammate's agent learned this morning never reaches yours. In Firmament, one agent learns something, a human approves it, and every agent on the team has it, across every tool and every repo.
Yes, until it isn't. One person, one repo, rules that rarely change, and a file wins. The moment it goes stale, a teammate's agent repeats a mistake yours already fixed, or you find yourself copy-pasting it between Cursor and Claude Code, the file has quietly become the slow option.
In fairness
If you are one person, in one repo, with rules that rarely change, a CLAUDE.md is genuinely the right tool: free, simple, and already in your git history. Firmament starts earning its place the moment a second person joins, a second repo appears, or the file starts going stale faster than anyone keeps up with.
Compare Firmament with