the Map
See active work.
Each supported session appears with its person, tool, account, repository, branch and active claim. Your own sessions stay separate, so kn0t can catch overlaps between them.
Keep your tools. Add coordination.
Across your tools. Across your team.
kn0t shows active work across Claude Code, Codex, Gemini CLI, Copilot CLI and OpenCode. It holds overlapping changes on the developer’s machine and sends the agreed order back to the affected sessions. Code, diffs, prompts and transcripts stay local.
01Watch.
Sessions, claims, repositories and accounts on one Map.
02Hold.
The later conflicting change pauses locally before it lands.
03Settle.
Agents and people agree the order; kn0t sends it to every affected session.
01 / the product in motion
One collision, start to finish.
Each machine checks changes locally and shares only the coordination facts a team needs. The agents do not need a direct connection to each other.
two developers · one overlapping changeschematic · demo data
02 / the desktop app
Local by default.
The desktop app indexes repositories, checks changes, applies personal rules, manages accounts and keeps the record. Core features work without the network.
code index
Track dependencies, not just files.
A local index maps functions, methods and direct dependencies in supported languages. Unrelated changes in the same file can stay out of each other’s way, while dependent work in another file remains visible.
wiring
Connect a repository in one click.
kn0t adds the supported tool hooks it needs and leaves unrelated configuration alone. Disconnecting removes only kn0t’s entries.
projects and timeline
Group repos and review events.
Group related repositories on the Map and review coordination, account, connection and guardrail events in one timeline. Loose ends also appear as native notifications.
03 / integrations
Built for each supported tool.
Each tool exposes different hooks and permissions. kn0t adapts to those differences and uses only the responses each tool can support.
claude codecodexgemini clicopilot cliopencode
native hooks and plugins
Use the hooks the tool already provides.
Supported tools report session starts, writes and commands through their own hook or plugin systems. There is no forked CLI, repository migration or replacement vendor binary.
The Agents surface detects installed supported CLIs and can open the vendor’s visible installer or updater after explicit confirmation. Vendor credentials remain with the vendor.
native MCP tools
Let agents read and answer coordination messages.
declare_intentDeclare a planned file operation and receive the local decision.kn0t_inboxFetch coordination messages addressed to this person or thread.kn0t_proposePublish a contract authored by the calling session.04 / languages
Language support.
Every watched Git repository gets file-level collision checks. Languages marked full also get function and method tracking, plus direct-call relationships. Parsing stays on your machine.
full · functions, methods and direct callsheld at the file · same-file changes
language
file types
support
TypeScript
.ts.tsxfull
JavaScript
.js.jsxfull
Python
.pyfull
Go
.gofull
Rust
.rsfull
Java
.javafull
C#
.csfull
Ruby
.rbfull
PHP
.phpfull
C
.c.hfull
C++
.cc.cpp.hppfull
Kotlin
.ktfull
Swift
.swiftfull
Terraform
.tf.tfvarsheld at the file
Ansible
.yml.yamlheld at the file
CloudFormation
.yaml.jsonheld at the file
Generated files, dependency folders and build output are excluded. Files outside watched folders are not seen.
05 / the harness
Optional session supervision.
Launch the same vendor command through kn0t to identify the session from the start, release claims when it exits and help an idle negotiation resume. Sessions launched normally still keep the rest of the product.
the supervised session
Launch a supported agent through kn0t.
The agent keeps its normal interface, keystrokes and exit codes. kn0t does not modify the vendor binary. Supervision is optional, and a fault falls back to the plain command.
identity at launch
Track the session from launch to exit.
A supervised session gets its identity and coordination hooks at launch. kn0t knows its process and working directory, so closing the window or crashing releases its claims promptly.
the idle thread
Notice when one side goes quiet.
If an idle thread has unanswered coordination messages, kn0t can notify you or offer to resume the session where the tool supports it.
auto · solo and above
Let an idle agent answer safely.
With auto on, a supervised agent can read and answer coordination messages while its write and command tools are removed. The terminal announces the turn, and your first keystroke cancels it. Unsupported tools fall back to a notification.
06 / accounts and rules
Set accounts and rules once.
Choose which account may use each repository, check supported files and commands, and search past sessions from the same local app.
identities
Keep agent accounts separate.
Use an existing vendor home or create an isolated one with its own launcher. Work, personal and client accounts remain distinct. Vendor sign-in stays with the vendor.
bindings
Choose which accounts may use each repo.
Set each account to allow, ask or deny for a repository or project. Team rules can set a minimum that a developer may tighten but not loosen.
path guardrails
Set rules for file paths.
Check file patterns before a supported change runs. Rules can deny, ask or warn, apply to one repository, and run always, while you are away or during quiet hours.
content guardrails
Check content before it is written.
Built-in rules cover common secrets, keys, tokens, email addresses and card numbers. Custom patterns cover your own policy. Matched text is omitted from the timeline and audit export.
command guardrails
Check shell commands.
Inspect Bash commands for risky transfers, unexpected push targets and destructive removal outside the repository. Each tool uses the strongest response its own permission system supports.
the record
Search past sessions locally.
Search supported transcripts and kn0t events by repository, tool, account or time. Open the local source or export the event record as JSON or CSV.
07 / Team
Connect the team.
Team adds a shared Map, cross-machine collision checks, projects, roles, managed policy, posture, devices, audit and owner-controlled billing.
authenticated team Map
See work across enrolled machines.
The Team Map shows live sessions, claims, tangles, repositories and agreement history. Filter by state, repository, project or agent.
teams and access
Control team access.
Manage invitations and member, lead, admin and owner roles. Role or membership changes revoke stale sessions, and team-scoped reads default to no access.
team projects
Share the same project map.
Members see the same repository groups and filters. Admins can create, rename and assign repositories, with version checks for concurrent changes.
managed policy
Publish rules to every machine.
Admins publish guardrails and repository bindings with enforced or advisory locks. Each machine evaluates them locally and keeps the last known policy while offline.
posture and audit
Check policy without tracking activity.
Policy fingerprints show which seats are current, need attention or have changed. Leads see team totals and administrative history; members see their own seat.
devices and billing
Manage devices and seats.
Users can name and revoke their own devices. Owners set the licensed seat count and manage billing through Stripe. Joining past that count waits for the owner to raise it.
08 / the contract with you
Clear limits, stated plainly.
kn0t coordinates supported agent work and applies rules through those integrations. It does not write code or decide the agreement.
deterministic v1
No LLM call. No automated patch.
Structural crossings come from live claims, symbols, and dependency relationships. Agents and people author proposals. kn0t records who agreed and delivers the result. When auto answers coordination mail, that turn runs your own agent on your own account under a policy you set; kn0t itself makes no model call, and unattended turns can never ratify each other.
work content stays local
The shared service receives coordination, not the work itself.
Code, diffs, prompts, transcripts, content-rule payloads, and matched secrets remain on your machine. Team signals are people, tools, repositories, claimed paths, state, and contract messages.
shared service unavailable
Your machine remains authoritative.
Local tangles, bindings, guardrails, and the record keep working. Remote queues retry within bounds and the Team Map shows that cross-machine awareness is stale until the connection returns.
kn0t unavailable
kn0t steps aside and the change goes through.
The wait is bounded and the outage is visible. Local coordination and guardrails cannot apply while their engine is down, so kn0t never pretends to be endpoint security.
kn0t does not
host repositorieswrite codechoose the contractupload transcriptsinspect every processturn posture into an activity feedRun agents in parallel without losing track.
Start with your own sessions. Add Team when work needs to coordinate across machines.