Conversation inheritance
Parent conversationFull path of messages
Child AInherited history
Child BInherited history
Useful continuity within a conversation tree. Cross-branch changes still need coordination.
Open source context coordination
Independent work.
Shared understanding.
Give each agent its own stream. Share the decisions that matter. See a changed assumption cross the project before it becomes a broken feature.
Try a one-minute scenario No install. No model key.
Nothing to connect.
Nothing to connect.
API agentOwn context
UI agentOwn context
QA agentOwn context
One shared contractAddressable. Versioned. Traceable.v1 → v2
A shared dependency connects independent contexts.
Synthetic interactive demo
One change. Three streams.
A fictional team is building usage-based billing. You control every step.
01/ 05
Three independent contexts
This is a small, in-browser illustration of Loomplane’s context model. The open-source runtime provides persistent revisions, a deterministic compiler, CLI, HTTP API, and MCP tools.
Read the architecture ↗The underlying ideaA conversation is a stream.
A conversation is a stream.
Knowledge can cross it.
Nested chats inherit a conversation’s path. Parallel work needs each agent to choose the context relevant to its task, then know when that context changes.
Explicit context dependencies
Stream ATask + selected context
Stream BTask + selected context
Shared capsule v2
Each stream stays scoped. Versioned references show precisely what changed and who depends on it.
Loomplane coordinates the information between agents. It does not change how a language model reads its input window.
The product thesisMake stale assumptions
Make stale assumptions
visible before the handoff.
The first use case is concrete: one agent changes an API contract while another implements its consumer. The broader opportunity is a shared context layer across tools, repositories, and teams.
Explore the business thesis ↗Start with a painful boundary.
API and UI agents need the same contract, with exact evidence and revisions.
Make the core useful and open.
Local storage, versioning, context packets, imports, and agent integrations are Apache-2.0.
Earn a managed-service business.
Managed sync, enterprise identity, policy, and deployment guarantees are the proposed paid expansion—not shipped capabilities.
Take it into your own workflow
Run the real workbench.
The current prototype runs locally with Node.js 24+. It works alongside your existing coding agents and requires no model API key.
From source · Node.js 24+
git clone https://github.com/davidbergman256/loomplane.git
cd loomplane
npm ci && npm run build
npm run loomplane -- demo
npm start