*A comparison for teams trying to figure out where their vibe-coding agents should actually plan — before anyone opens the IDE.*
Every team that's gone all-in on Cursor, Windsurf, or Claude Code eventually hits the same wall: the agents are fast, but the *team* isn't in sync. Someone always ends up asking "wait, where did we agree to do this?" The honest answer is usually: buried in someone's private chat with their agent, or not written down at all.
Four tools get reached for at that point. Here's how they actually differ.
The shape of the problem
It's not "we need a doc tool" — every team already has one. It's "we need the place where a team *and* their coding agents plan together, live, with a record of who decided what." That's a narrower job than general note-taking, and it's the one this comparison is about.
Notion AI
Notion has moved a long way past inline rewriting: Notion Agent handles multi-step tasks on its own, Custom Agents run on schedules or triggers, and as of Notion 3.6 (July 2026) External Agents let you @-mention Claude or Cursor on a shared board and watch them work. So "an agent can't touch a shared doc" isn't the real gap anymore. What's left is where that agent operates: it works through Notion's MCP integration, and like most hosted document MCPs — including Campfyrr's own — that's a whole-page-content interface, not a block-level patch API, so a big edit still means the page gets resent and rewritten wholesale. The real difference is the in-app surface: Notion has nothing like typing an instruction directly into the doc and watching an agent write into it live, block by block, next to the humans working alongside it.
Google Docs AI (Gemini in Docs)
Similar shape to Notion AI: inline completion and rewriting help, layered onto a general-purpose word processor. Strong at what it's built for — polishing prose, summarizing a long doc — but it isn't agent-native in the sense a vibe-coding team needs. It doesn't take a command like "map out the API changes for this feature" and write a structured plan into the doc; it assists the sentence you're already writing.
A shared Cursor rules file
This is the tool most technical teams reach for first, because it's already sitting in the repo. A .cursor/rules or equivalent file is genuinely useful for keeping individual agents consistent with team conventions — but it's a static config file, not a planning surface. It doesn't hold a conversation, doesn't show who proposed what, has no history you can scrub through, and nobody's actually *collaborating* on it live. Two engineers editing the same rules file at the same time are editing a text file, not planning together.
Campfyrr
Campfyrr starts from a different question: what if the planning doc itself was the place the agent worked, with the whole team watching it happen live?
- Command-driven, not chat-driven. There's no sidebar. Press Enter on an empty line, type an instruction, and the agent's output streams directly into the shared document — the same one everyone else is looking at.
- Provenance on every block. Hover any paragraph and see who — or which agent, with what prompt — wrote it. Not a diff view you have to dig for; it's right there.
- Zero-auth entry. No signup wall. Open a link, land in a live doc, start planning.
- Sandbox + non-destructive history. Let an agent take a real swing at a rewrite in an isolated fork — promote it back if it's good, or throw it away. Nothing about the working copy is at risk. Scrub the revision history and restore any point.
- True multiplayer. Every person's cursor, and the agent's, visible to everyone identically — not a bolted-on "AI plus one human" model.
- Plain Markdown underneath. No proprietary format. Claude, Codex, or any other agent reads and writes the doc cleanly.
Where each one actually wins
| | Best for | | --- | --- | | Notion AI | Assigning agents to a shared workspace — strong once you accept full-page rewrites over per-block editing | | Google Docs AI | Polishing prose in a document you're going to send outside the team anyway | | A shared Cursor rules file | Keeping individual agents' *code* conventions consistent — not planning | | Campfyrr | The shared page a team plans and specs on, live, with agents writing directly into it and a permanent record of who decided what |
Worth knowing before you switch: Campfyrr doesn't have real auth/permissions yet — anyone with a doc's URL can edit it, which is fine for scratch docs and fast-moving teams but a blocker if you're planning anything sensitive. It's not trying to replace Notion or Google Docs as a general workspace; it's built for the specific moment before the IDE opens, when a team needs to agree on what they're about to build.
---
Synced from Campfyrr: (pending) · content authored 2026-09-08