Firmament for Cursor
You fix something in Cursor this morning. A retry that finally worked. A rule about how your migrations actually run. Your teammate's Cursor never finds out. Neither does the Claude Code you open after lunch. Five engineers on Cursor is five separate brains, each relearning what the others already know.
Firmament doesn't replace Cursor or its rules. You keep both. Firmament plugs in over MCP and connects what your agents learn, so one shared brain sits behind all of them.
Free for 14 days. Every feature, no card needed.
You can, and keep doing it. But a committed rules file is only what someone remembered to write down, and it sits frozen until someone updates it. Firmament captures what your agents actually learn while they work, keeps it current as things change, and carries it across every tool, not just the repo Cursor is looking at.
No. Your .cursor/rules stay yours, in git if you like. Firmament is the shared layer on top, for the lessons worth giving the whole team, kept current without anyone editing a file.
No. Everyone keeps using Cursor exactly as they do now. Firmament rides along over MCP, so the sharing happens without anyone changing their setup.
The knowledge stays with you, not the tool. Connect the new agent to the same Firmament and it picks up where the last one left off.
In fairness
If you are solo, in one project, in Cursor only, Cursor's own rules are genuinely enough. Firmament starts to matter the moment a second person or a second tool shows up.
Firmament also works in