Development updates, tutorials, and tips
A multi agent plan board is one shared plan that several AI agents and the people around them read and write at the same time. What Develosaur's board actually does to make that work, the four mechanisms behind it, and one real session from digest to handoff.
I found myself in a quite strange position, where I felt way too confined, by some tools, and way too lazy for 80% of others, I'm talking about project management tools.
"Put this design doc into a develosaur board" turns headings into branches and everything else into their content, in one call, because a design doc is already organized the way a board wants it.
A board and a git history are two separate systems, and nothing joins them unless something writes the join. One line in a commit message, generated by the handoff verb, answers "which commit fixed this" for good.
gemini mcp add registers the board and /mcp auth signs you in, but the config key has to be httpUrl, not url, or Gemini CLI falls back to an older transport that will not work.
Add a remote server in the Cline MCP panel and sign in once. The board's rules are enforced by the server, not memorized by the model, so a smaller or local model follows the same work loop a frontier one would.
Add the server, sign in, done. Codex registers itself with the gateway on login, so there is no client id to request or paste anywhere first.
Add one address to mcp.json and Cursor signs you in the first time an agent uses it. No token to paste, and Cursor and Claude Code can work the same board without colliding.
A memory server and a project board both answer "my agent forgets everything," but they store different things. What a memory layer remembers, what a board plans, and why an agent usually needs the second one more.
The desktop app is not a client. It is a small server you run once on your machine, and every local agent reaches your boards through it with nothing to configure per client and nothing to paste per repo.
Two different ways to connect ChatGPT to Develosaur, a no-account sandbox that builds a temporary board in one message and a signed-in connector for your real boards, and exactly what each one gets you.
The full setup for connecting Claude Code to a Develosaur board, one command, a /mcp sign-in, and the project-scope option that gives an entire team the same server from one committed file.
Develosaur search is one verb with five modes instead of five different tools to remember, and the default mode, plain exact substring match, is the free one.
A tag on a Develosaur board decides whether work is even visible to the ranked list, and can carry its own written rule that the server enforces or quotes back when it is broken.
The board that plans Develosaur's own engineering is a Develosaur board, worked by AI agents claiming tasks off it. What that forces you to get right, and the guardrails an AI-heavy codebase needs that a solo human team never would.
There is no scoring formula behind Develosaur's TODO list. Four layers in a fixed order, an objective dial, and a pinned head you control, and every ranked task says exactly which layer put it there.
The working design I said no to, why a bearer key you copy and paste was the wrong first feature even though it was the faster one, and what OAuth sign-in buys instead.
Point Claude Code, Codex and Cursor at the same Develosaur board and none of them touch the same task twice. How 45-minute task leases, the frontier and the abandoned-by trail work, and what happens when there is not enough ready work to go around.
How two browser tabs sharing one Develosaur board could leave an edit permanently unresolved if one tab died mid-write, the fix that closed it, and the chaos rig built to catch this class of bug before a real board ever sees it.
An agent starting a fresh session knows nothing about your project. A list forces you to choose between dumping everything into its context or explaining it again. A graph lets it fetch what it needs, in order, and stop.
Whether by forgetting about specific .md, or getting too bloated, there's certain drift that happens if you don't track your agent or if you don't have a good source of truth, develosaur solves both memory, project tracking, and brainstorm board with one hit, a collaborative tool between humans and agents.
Most of the tasks, requests, or feature changes come through some feedback channels, or chats, emails, etc... it is very important to be able to on the spot catch these and place them so they don't get lost...