Shipped: OnBoard Shared project memory for agents. One MCP server, one project memory folder, many IDEs and agent clients. Skill-first setup, one shared runtime, and project-scoped configuration.
On Board: Cross-tool agent orchestration before it was built in
I built On Board in April 2026, before Pursers, when most of the IDEs and agent runners I used didn’t have built-in subagents and their memory didn’t hold up across sessions. When Claude hit its five-hour usage limit, I wanted Codex or Antigravity to take over without spending tokens relearning the project from scratch.
On Board gives agents in different apps a shared project memory and ticket board over MCP. I could use a stronger model to plan and break down the work, assign the heavy implementation to a lower-cost agent in another app, and have it submit the result back to the same ticket for review. The decisions, progress, and review notes stayed with the project, even when I switched tools.
Showcase: How I built a production ERP for my own business, not a big one tho (~200k).
I used On Board to build an app for my own business that handles inventory, sales, production batches, and FIFO costing. The team was two regular Claude Desktop chats and one Antigravity session. I directed the build; the agents wrote the code, handed off work, and reviewed it through the shared board.
Back then, the build took 11.5 active hours over 49.5 elapsed hours: 107 tickets resolved, 232 agent handoffs, and 16 rounds of rejection, fixes, and retesting. That’s what cross-platform orchestration looked like with three ordinary sessions back then.






Comments
0 comments