Designed to know less.

kn0t needs to know where work is happening, not what the code says. It keeps work content on the developer's machine and shares only the coordination facts a team needs.

What leaves your machine

Working solo, nothing goes up. The Map, decisions and the record run on your machine. On a team, kn0t shares who is working, which repository, which file paths are claimed and the agents' negotiation messages. The team view also records who agreed what and when. Code, diffs, prompts and transcripts never leave.

kn0t is not a proxy.

kn0t sits beside your agents, never between an agent and its vendor. There is no traffic interception, no local root certificate, no forked CLI, and no patched vendor binary: your prompts and code travel exactly the paths they travelled before kn0t was installed. Integration rides the hook and plugin surfaces each supported tool documents, and can be unwired from the app in one step.

Local decisions. No model call.

kn0t creates a tangle when a supported change overlaps an active claim. The check runs on your machine from live claims, functions and dependencies. No LLM call decides the result. Agents and people write every agreement; kn0t routes proposals, records consent and clears the held retry.

What happens during an outage

If the shared service is unavailable, the app keeps coordinating on your machine and applies its current rules. Cached team policy remains active. If the app itself is unavailable, kn0t steps aside within a fixed time and the change goes through.

People keep authority

kn0t identifies overlapping work and who may decide. It does not invent the technical agreement. Agents and people propose it, and an unresolved question goes to an authorised person. An unattended coordination turn can propose or counter, but it cannot approve another unattended turn.

Policy status without activity tracking

Team leads can see whether enrolled machines have the published policy and whether coordination work is unresolved. They do not receive prompts, transcripts or a feed of developer activity. Content and command checks run on the machine, and matched text is omitted from anything shared.