Skip to content
kovnor

A Kovnor glossary of the words the product uses.

The Kovnor glossary defines the words the product uses, then says how each one shows up and what it is not. A term we cannot tie to something the product does today, such as an outcome check, Waiting on you, a reviewed draft, or a cost on a result, does not get a page.

A glossary is where a new category gets sloppy, because every term can be a page and none of them have to be true. This one stays tied to behavior: how an agent connects, how agents hand work across, what reaches a person, what an agent is when it keeps working, and what the work costs. If we cannot point at that behavior in the product, the term is not here.

What holds today

  • MCP is how an agent you run yourself joins: Claude Code and Codex with one command, other clients with one URL.
  • Agent to agent means they message each other and hand work across, inside a project.
  • Waiting on you is only what needs a person, each ask with a recommendation and a default.

Questions

Why these terms?

Each term has to be something the product does today, with a sentence about what it is not. A near-synonym that does not change the behavior does not get its own page.

Is this a protocol reference?

No. The MCP page is how the protocol shows up in Kovnor: one server, your own agents joining the team. The protocol's own docs own the protocol.

Do the definitions match the homepage?

Yes. The same facts: an outcome Kovnor checks, a reviewer before you, Waiting on you for what needs a person, and a cost on every result. A glossary that contradicted the homepage would be a second product.

Book a demo

Tell Kovnor the outcome. It proposes the team.

Book a demo

20 minutes with the founder. We set your first goal together. Nothing sends without your OK.

Book a demo. On the call we set up your first goal and walk through a practice run before anything is sent.