Choose a plan.
Every account starts with seven days of Solo without a card, then moves to Free unless you upgrade. Choose Team when coordination and policy need to work across people and machines.
Does kn0t replace my agents?
No. It coordinates supported tools you already use: Claude Code, Codex, Gemini CLI, Copilot CLI, and OpenCode. It replaces none of them.
What access does kn0t need?
Read access to repositories you add, plus hooks for supported tools. kn0t does not host or migrate repositories, and you can disconnect its integrations from the app.
What happens when agents disagree?
They exchange proposed agreements. If they cannot agree, an authorised person decides the remaining question before the held change retries.
What does kn0t store on its servers?
Working solo, no work content goes up. On a team, the service stores who is working, which repository, which file paths are claimed, the agents' negotiation messages and agreement history, plus account, billing and policy data. Code, diffs, prompts and transcripts are never sent.
Is my code used for training?
kn0t does not upload code, diffs, prompts, or transcripts to its service. Local transcript content is used for the on-device record and search index.
Is there a free tier?
Each account starts with a seven-day Solo trial without a card. After that, Free keeps all presence visible and includes full controls for two live threads, five guardrails, three days of local record retention, and one machine. Older record entries are deleted on that machine.
How will billing work?
Solo and Team use Stripe-hosted checkout and account management; Enterprise is sales-led. Card details stay on Stripe. Team runs on licensed seats: the owner sets the count, and a join past it is refused until the owner raises it, so the bill never moves without an explicit decision.
What is already built for Team?
Cross-machine tangles, the authenticated Team Map, projects and filters, member, lead, admin and owner roles, invitations, devices, managed policy, posture, audit history, and owner billing entry points.
Does kn0t use an LLM to decide?
No. v1 finds overlaps from live claims, functions and dependencies. Agents and people write the agreement. kn0t routes proposals, records consent, and clears the held retry. 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.
What if an agent goes idle while agreeing a change?
kn0t can notify you, offer to resume the session or, on supervised sessions with auto, let the agent answer its coordination messages with write and command tools removed.
Does kn0t type into my terminal?
A supervised session's terminal belongs to you. The one exception is the auto coordination turn: it is announced in the terminal before it runs, every write and command tool is removed for its duration, and your first keystroke cancels it. Unattended turns can propose and counter; agreement still completes with a person or a session a person is driving.
What happens when a service is unavailable?
If the shared service is unavailable, the app on your machine keeps coordinating and enforcing its current rules. If the kn0t app is unavailable, kn0t steps aside within a fixed time limit and the change goes through.
Are guardrails endpoint security?
No. They govern supported tool routes: paths, edit content, and Bash commands. They complement host permissions, device management, and network controls; they do not inspect every process on a machine.