u/TlyNxy

say you've got multiple agents working on the same project, each doing a different job, lets say one's researching, one's writing code, one's handling qa, whatever your setup looks like. classic pattern is agent a finishes its part and passes a summary to agent b so it knows what's been done.

problem is that summary is lossy. agent a strips out raw detail to save tokens, agent b gets the compressed version and ends up guessing/hallucinating to fill whatever's missing. chain a few of these handoffs together and by the end, the last agent's working off something that's drifted pretty far from what actually happened...

what i tried that didn't really work

• shared markdown file both agents read/write to. sounds simple but burns a ton of tokens keeping it updated, and in practice the agents don't reliably "internalize" what's written there, especially mid task. they skim it more than actually track it.
• summarized handoffs between agents. the lossy compression problem above. works ok for short chains, falls apart fast once you've got 3+ agents touching the same work.
• vector cache as shared memory. better than nothing but still a compressed/approximate version of the actual state, so drift is still possible, just slower.
• mainstream tools. tried a few but they didn't really fit my workflow, ended up spending more time setting them up than actually getting work done.

so i decided to building a note/task app for the past few months and multi-agent coordination turned out to be the hardest part, way harder than i expected. built it specifically around this problem.

what i did was stop passing messages between agents entirely. instead gave them a shared structured state they both read/write to directly, so agent b never needs agent a to "tell" it anything, it just reads the real current state straight from source.

concretely this is a note-first pm app with an mcp server. workflow looks like this:

• you write a plan as a plain note, normal messy human writing, checkboxes for tasks
• agents connect via mcp and can read the note directly, not a summary of it, the actual text
• when an agent picks up a task, it claims it in the shared state using connected notes/references, so each agent gets its own task progress that all the other agents can still view and read if needed
• as it works, it updates status and writes results/logs back into the same note, not a separate handoff file
• next agent (or you) reading that note sees the real current state, not someone's compressed account of it

bonus part is it doubles as regular task management too, my tasks, my team's tasks, and the multi-agent workflow all sit in the same system, so each agent is basically treated like a team member. everyone (human or agent) can see task status, and it reads the team calendar to assign work with everyone's busy days as context.

so there's no handoff step at all, just one source of truth every agent hits directly. anything append-only/immutable (like a git commit log) beats a compressed summary that can drift from what actually happened, that's roughly the model i went with.

So what you guys are doing for this, especially once you're past 2 agents. centralized state, event sourcing, something else entirely?

I’ve recently launched a Note-first workspace tool that translates messy product notes and feature briefs directly into structured Kanban, timeline, list, and graph views.

The Workflow:

1. You drop a raw feature brief or a brain-dump from a meeting into a markdown note or directly to your AI Agent
2. The agent parses or creates a note to organize tasks into folders, maps out a timeline, flags cross-task dependencies, and assigns items to your team members, and you can visualize it across the Kanban, Calendar, and Graph views.
3. As work happens, you or your team members can instruct it via text or comments to shift dates, re-route blockers, adjust priorities, or update statuses to "Done" across the workspace.

Long story short, you'd be using agent integration (using MCP with tools like Claude, Manus, etc.).. instructing it to prepare a timeline, create tasks, and assign them to your team. Your team members can also instruct to claim tasks, update them, set status to done, etc. And you can visually see everything through a simple Overview dashboard, Kanban, List, Calendar, and Graph view.

Now that the app is live, The tool works well with a indie or small team of devs where, they can plan, code, at the same time manage the project. but i would like to also see from PM point of view how this tool can help.. I want to get a honest product management perspective on this. Developers love the technical side of automation, but I know PMs own the actual operational risk, sprint velocity, and process control.

• Would you ever trust an AI agent to dynamically shift your sprint timelines or adjust priorities across the board based on a team member's input? Or does this instantly trigger a micro-management nightmare where you'd want actual person "Pending Approval" gate for every single adjustment it makes?
• Does having an AI automatically assign tasks to your team members based on a product brief feel genuinely helpful for reducing the work, or does it feel like a weird breach of team dynamics?
• PMs spend a massive amount of time grooming backlogs. Do you see an agent successfully keeping your folders and tasks organized based on your notes, or are you terrified it’s going to spam your board with multiple messy micro-tasks and ruin your sprint metrics?
• What would make you instantly uninstall the tool like this if you saw an agent manipulating the project layout? (e.g., silent failures, lack of a clear reasoning log/audit trail showing why it moved a card or changed a date, an agent modifying a timeline without stakeholder context?)
• If you're currently experimenting with AI to write your specs or PRDs, what's the biggest missing link you face when trying to bridge the gap between "AI writing a doc" and "AI updating the live project board"?

I'm trying to figure out if this level of administrative autonomy solves a massive operational headache for product teams, or if it just introduces automated chaos to a sprint.

Im not tying to make the post as a self promotion.. so im not sharing the link here.. but if anyone would like to see the product do DM me i would love to share.

Would appreciate your raw thoughts. Thanks!