kn0t another
AI tool.
Coordination for the agents you already use.
Run Claude Code, Codex, Gemini, Copilot and OpenCode in parallel. kn0t shows what each supported session has claimed, holds overlapping work before it lands, and sends the agreement back to the agents. You step in only when they cannot agree.
Every supported session on one live Map, with its person, tool, repository and claimed files.
When a second session touches claimed code, kn0t holds that change on your machine.
The agents agree an order in-session. A person decides only when they cannot.
Parallel agents do not share context.
Parallel sessions save time.
One developer can run several coding sessions at once, across tasks, repositories and worktrees.
Each session sees only its own work.
Your Claude changes an interface while your Codex builds against the old version. Both changes can look correct in isolation, even when they cannot work together.
The conflict appears later.
The first warning is often a failed test, a review comment or a merge conflict, after both sessions have moved on.
The same problem exists across terminals, worktrees and teammates.
kn0t checks each supported change against work already in progress.
Watch, Hold, Settle.
01Watch
kn0t shows active sessions, repositories and claimed files on one live Map.
02Hold
When a later change overlaps an active claim, kn0t holds it and names the other thread. The first thread keeps working.
03Settle
The agents agree an order, then the held change retries with that agreement in context. If they cannot agree, kn0t asks a person. Supervised sessions can also resume an idle exchange without gaining access to write or command tools.
Keep agents in the right place.
kn0t keeps agent accounts separate, applies your repository rules and makes supported session history searchable. It does not choose the work or write code.
Keep each agent account separate.
Work Claude, personal Claude and a client's Codex can share one laptop without sharing credentials or repository access. Adopt an existing account or create an isolated vendor home, then launch it with claude-perso that opens the agent signed into the right account. Sign-in stays with the vendor.
Set which accounts may use each repo.
Set each account to ✓ allow, ? ask or ✗ deny for a repo. When a denied account tries to change it, kn0t holds the change and tells the agent which identity is allowed.
Check files, content and commands.
Check paths, proposed content and Bash commands. Use built-in secret and risky-command checks or your own patterns, scoped by repository and schedule.
Search past sessions.
Search supported local transcripts and coordination events by repository, tool, account or time. The index stays on your machine.
Start with your sessions. Add your team.
Keep your agents and accounts straight.
Run supported coding tools across work and personal accounts. kn0t keeps those accounts out of the wrong repositories and checks their changes against your rules.
One view across every supported tool.
A team can use Claude Code, Codex, Gemini CLI, Copilot CLI and OpenCode in the same repositories. kn0t gives their separate sessions one shared claim map.
It sits beside those tools. It does not host your repositories or replace an agent.
auth/session.ts
middleware
Your agents can use different tools. They still share one Map.
Exactly what leaves your machine.
Work content stays local.
The personal Map, edit decisions, transcript record, and search index run on your laptop. Account and billing requests are separate from that work content.
Coordination signals only.
Your machine shares who is working, in which repo, and which file paths are claimed, so your teammates' agents can steer around yours. Contract proposals and decisions are shared too. Team coordination does not include file contents, diffs, prompts, or transcripts.
Code content stays local.
Not your files, not your diffs, not your prompts, not your transcripts. The record and its index live in one file on your disk. If it would show what you wrote, it does not go up.
If the shared service goes down, the app on your machine keeps coordinating and enforcing its current rules.
If the kn0t app itself is unavailable, kn0t steps aside within a fixed time limit and the change goes through.
Three ways teams use kn0t.
Parallel sessions, cross-repository changes and shared rules.
Two of your agents change the same interface.
kn0t holds the later change and carries the agreed order back to both sessions.
see the use case →02 · engineering managerA shared package changes across repositories.
kn0t follows the dependency and sends the compatibility agreement to both sessions.
see the use case →03 · head of engineeringTeam rules reach every enrolled machine.
Posture shows whether those rules are current without uploading prompts, transcripts or activity history.
see the use case →