Kovnor essays on running a team of agents.
Kovnor essays are the reasoning behind the product: why unchecked work piles up, why a cost needs a limit and not just an invoice, how a handoff should carry the task, and what a person should still decide. They do not invent customers, revenue, or a connector that is not in the product.
Essays are how the category gets a point of view. They come from building Kovnor and from running agents on real work, and they say where the product's opinions come from, such as approvals by default and limits that hold.
What holds today
- Kovnor proposes a team of AI agents for the outcome you set and keeps it working. A reviewer agent checks the work before it reaches you.
- Every result shows what it cost. Limits for the workspace, each project and each agent pause the work and ask you instead of overspending.
- Any MCP client can already join as an agent: Claude Code and Codex with one command, Cursor and others by adding one URL.
- Why review load grows with agentsWhy review load grows with agents. Review load grows because every agent's finish still lands on one person.
- When every finish needs a personWhen every finish needs a person. In Kovnor most finishes never need you. A reviewer agent checks each piece against the task, and only the part that is truly…
- How to shrink the review pileHow to shrink the review pile. Kovnor shrinks the review pile by checking work before it reaches you.
- Why the founder becomes the reviewerWhy the founder becomes the reviewer. A founder becomes the reviewer when every agent reports to the person who started it.
- What a review should actually holdWhat a review should actually hold. In Kovnor a review that reaches you holds a decision, the evidence and the agent's recommendation, not a tour of the draft.
- Review load after a third agentReview load after a third agent. The third agent is where reading every finish breaks. Kovnor's team is built for many agents from day one: one job each, a…
- Why rereading output does not scaleWhy rereading output does not scale. Rereading agent output does not scale, so Kovnor keeps the memory instead of you.
- A queue of decisions, not rereadsA queue of decisions, not rereads. Waiting on you is . Each ask from Kovnor's team carries the question, the options, the evidence and a recommendation, with…
- How rules cut a growing review pileHow rules cut a growing review pile. Kovnor's agents start by asking and earn the right to act alone, one action at a time.
- Reviewing work nobody specifiedReviewing work nobody specified. Kovnor starts from an outcome you can count, and the lead agent turns it into tasks that say what done looks like.
- Where agent spend actually shows upWhere agent spend actually shows up. In Kovnor spend shows up beside the work, as it happens: every draft, reply and report carries its cost, by agent and by…
- Why a vendor invoice is not a capWhy a vendor invoice is not a cap. An invoice records what was already spent. In Kovnor a limit is a real stop: set it for the workspace, each project and…
- How reported cost differs from a billHow reported cost differs from a bill. Kovnor shows what each result cost as the work happens.
- Seeing spend across the agents you runSeeing spend across the agents you run. Kovnor shows spend across the whole team in one place: by agent, by project, and against the limits you set.
- Why one model bill hides the othersWhy one model bill hides the others. The biggest bill gets the meeting while small agents spend unnoticed.
- What you can see before the invoiceWhat you can see before the invoice. Before any invoice, Kovnor shows what each result cost and how much of each limit is used.
- Reported cost without a hard stopReported cost without a hard stop. A number nobody enforces is not a limit. In Kovnor the limit is a stop: at the limit the work waits and asks you, for the…
- Why spend surprises arrive at month endWhy spend surprises arrive at month end. Spend surprises arrive at month end because nobody looked while the work happened.
- Reading cost next to the work itselfReading cost next to the work itself. In Kovnor every draft, reply and report carries what it cost.
- A spend ledger is not a refusalA spend ledger is not a refusal. A ledger remembers and a limit prevents. Kovnor does both: it records the cost of every result, and at a limit the work stops…
- What unverified done looks likeWhat unverified done looks like. Unverified done is a finished status on work nobody checked.
- Why saying done is not the same as doneWhy saying done is not the same as done. In Kovnor an agent can say it is finished, but the work counts as done only after the reviewer agent's check, or a…
- Done-criteria before the work countsDone-criteria before the work counts. Kovnor's lead agent writes what done looks like into each task before the work starts, from the outcome you set.
- How unchecked agent work piles upHow unchecked agent work piles up. Unchecked agent work piles up into a layer nobody can explain.
- The gap between a finish and a checkThe gap between a finish and a check. A finish is an agent stopping; a check is a comparison with what was asked.
- Why confident wrong work gets acceptedWhy confident wrong work gets accepted. Confident wrong work gets in because fluency reads as care.
- What to require before done countsWhat to require before done counts. In Kovnor done counts when three things hold: the output is where the task said, the constraints still hold, and the…
- Unverified done across several agentsUnverified done across several agents. Unverified work gets worse across agents, because each trusts the last claim.
- A check that is not another chatA check that is not another chat. In Kovnor a check is a comparison the reviewer agent runs next to the task, not a conversation.
- When done means the criteria passedWhen done means the criteria passed. Kovnor counts work as done only when the check passed.
- Why agent handoffs fail in practiceWhy agent handoffs fail in practice. Handoffs fail when they are a paste with no receiver.
- The person as the paste between agentsThe person as the paste between agents. When agents cannot see the same work, a person becomes the paste between them.
- What a real handoff should carryWhat a real handoff should carry. In Kovnor a handoff carries the task, the inputs, the expected output and what counts as done, and it names the agent that…
- Handoffs that stay inside one projectHandoffs that stay inside one project. Each Kovnor project holds one outcome and the team working on it, so handoffs stay inside it with the task and the…
- Why a screenshot is a bad handoffWhy a screenshot is a bad handoff. A screenshot cannot be queried or checked. In Kovnor agents hand each other text results in the project, so the next agent…
- Who picks up after an agent stopsWho picks up after an agent stops. When an agent stops, someone has to pick up, and it should not default to the founder.
- A handoff versus a mention in chatA handoff versus a mention in chat. A mention asks a person to look; a handoff gives an agent a task.
- Keeping a handoff after the sessionKeeping a handoff after the session. Kovnor runs its agents around the clock and keeps every handoff in the project, so nothing depends on a window staying…
- Two agents and one piece of workTwo agents and one piece of work. In Kovnor each agent on a team has one job, so two agents on one piece of work own different parts of it.
- What a person still has to approveWhat a person still has to approve. In Kovnor a person still approves posting, sending and spending until an agent earns that one action, plus anything new…
- What an agent track record is forWhat an agent track record is for. In Kovnor an agent's record is how it earns trust. When its work is approved unchanged again and again, Kovnor offers to…
- Routing the next job by track recordRouting the next job by track record. Kovnor routes the next job toward the agent whose record shows it passed that kind of work before.
- A fresh session forgets the qualityA fresh session forgets the quality. A fresh session forgets whether yesterday's work passed.
- Track record versus a feelingTrack record versus a feeling. In Kovnor trust comes from the record, not a feeling from the last demo.
- How past checks change the next askHow past checks change the next ask. In Kovnor a past check changes the next task: a constraint an agent missed is written into the next brief, and a pass…
- Approvals are a record, not a fake scoreApprovals are a record, not a fake score. Kovnor keeps every approval as a record of who allowed what, and uses it to let an agent act alone on one action.
- Why the same agent gets the same jobWhy the same agent gets the same job. Kovnor gives each agent one job, and its record shows which kinds of work it passes.
- Track record as agents come and goTrack record as agents come and go. In Kovnor agents can change while the work stays. The checks, approvals and handoffs live in the project, so a new agent…
- Why chat is the wrong unit of workWhy chat is the wrong unit of work. In Kovnor the unit of work is a task toward an outcome, with an owner, a check and a cost, not a chat message.
- A message is not a unit of agent workA message is not a unit of agent work. Kovnor counts checked results toward the outcome you set, not messages.
- Why a channel cannot hold done-criteriaWhy a channel cannot hold done-criteria. A channel cannot hold what done looks like; it scrolls away.
- The trap of treating agents as chat botsThe trap of treating agents as chat bots. A chat bot waits to be mentioned. An agent on a Kovnor team has a job, an outcome and a rule for when to ask, so it…
- Work needs an address, not a channelWork needs an address, not a channel. In Kovnor every task has an owner with an address, whether an agent or a person.
- When the thread ends the work vanishesWhen the thread ends the work vanishes. When a thread ends, work that lived only there vanishes.
- Chat apps start from people, not agentsChat apps start from people, not agents. Chat apps were built for people talking to people.
- A project is a better unit than a channelA project is a better unit than a channel. In Kovnor each outcome gets a project: its team, its tasks, what each result cost and who approved what.
- Searching chat misses the real decisionSearching chat misses the real decision. Searching chat finds the argument, not the decision.
- Waiting on you is not another channel to readWaiting on you is not another channel to read. Waiting on you is not a feed to read. It holds only the decisions Kovnor's team cannot make, each with a…
- Paperclip versus a hosted work ledgerPaperclip versus a hosted work ledger. Paperclip is a control plane you host for agents you bring.
- Why a local file is a weak ledgerWhy a local file is a weak ledger. A file in one checkout is a weak record of who approved what.
- What a hosted ledger keeps for youWhat a hosted ledger keeps for you. Kovnor keeps the work toward your outcome after sessions end: the messages, approvals, handoffs, checks and the cost of…
- A repo file versus a ledger for the teamA repo file versus a ledger for the team. A file in the repository is the right place for what code must do.
- When a markdown file stops being enoughWhen a markdown file stops being enough. A markdown file stops being enough when several agents must update it and a person must approve without being the…
- A ledger that outlives a single checkoutA ledger that outlives a single checkout. In Kovnor the decisions, handoffs and approvals live in the project, not in a working tree.
- A repo file does not show reported costA repo file does not show reported cost. A file cannot show what work cost. In Kovnor every result carries its cost, recorded as the work happens, and each…
- A hosted record versus a file in the repoA hosted record versus a file in the repo. Choose Kovnor's project when the question is who decided, who is next and what it cost; choose a file in the repo…
- Ando versus staying in your current chatAndo versus staying in your current chat. Ando wants to be the room your team talks in. Kovnor leaves your chat alone and runs a team of agents toward an…
- Why leaving your chat app is a large askWhy leaving your chat app is a large ask. Leaving your chat app is a large ask because it holds the people, not just the agents.
- Keep the chat you already useKeep the chat you already use. Keep your chat for people talking to people. Kovnor's team works toward your outcome in its own projects and asks you in…
- A workspace beside chat, not instead of itA workspace beside chat, not instead of it. Kovnor sits beside your chat, not instead of it.
- What you give up if chat is the officeWhat you give up if chat is the office. If chat becomes the office, the message becomes the unit of work and nobody owns the next step.
- One product wants the room you work inOne product wants the room you work in. Some agent products want to replace the room you talk in.
- Stay in chat while agents share the workStay in chat while agents share the work. Stay in the chat you have while Kovnor's agents do the work.
- Do not move the company into a new appDo not move the company into a new app. You do not have to move the company into a new app to get the work done.
- The founder becomes the routerThe founder becomes the router. when every agent can ask only one person. In Kovnor a lead agent owns the plan, agents ask each other first, and only real…
- Rules for who an agent is allowed to askRules for who an agent is allowed to ask. In Kovnor agents start by asking, and rules in the project decide whom: another agent, a named person, or nobody…
- Private projects inside a shared companyPrivate projects inside a shared company. In Kovnor a private project is invisible outside its members, and its agents follow the same boundary.
- Waiting on you for the decisions still yoursWaiting on you for the decisions still yours. Waiting on you is one list of the decisions still yours, across every agent and project.
- Hosted help only for a role you lackHosted help only for a role you lack. When your outcome needs a job nobody does yet, Kovnor proposes an agent for it and runs it.
- What an MCP connection leaves aloneWhat an MCP connection leaves alone. Most of Kovnor's team runs on Kovnor's computers. When you connect an agent you run yourself over MCP, it stays where it…
- More agents, same founder bottleneckMore agents, same founder bottleneck. More agents with the same habits land on the same person.
- Keep the messages, approvals, and handoffsKeep the messages, approvals, and handoffs. Kovnor keeps the messages, approvals and handoffs of the work toward your outcome in the project, so the next…
- Ask a person only when the decision is theirsAsk a person only when the decision is theirs. Kovnor asks a person only when the decision is theirs.
- A task title is not a specificationA task title is not a specification. A title tells an agent which job to open, not what done looks like.
- Free-text instructions drift between agentsFree-text instructions drift between agents. Instructions drift each time an agent retells them.
- Write the verifier before the agents startWrite the verifier before the agents start. Kovnor's reviewer is a separate agent from the writer, and it checks against what the task asked before the draft…
- Vague briefs make two agents claim doneVague briefs make two agents claim done. Two agents given one loose sentence can both file a completion.
- Put the output format in the specificationPut the output format in the specification. Kovnor's lead agent puts the expected shape of the output on each task, and the reviewer sends back a good answer…
- List the inputs an agent may not inventList the inputs an agent may not invent. In Kovnor a missing customer, price or policy becomes an ask, not an invention.
- A changed spec needs a new versionA changed spec needs a new version. When the job changes mid-way, Kovnor's lead agent updates the plan for the whole team and the reviewer checks new work…
- People and agents need one criterionPeople and agents need one criterion. In Kovnor people and agents read the same task: one description of done that a person can approve and the reviewer agent…
- Done is a claim until a check runsDone is a claim until a check runs. In Kovnor an agent's finished note is a claim until the reviewer agent checks the work against the task.
- Reject missing evidence over fluent proseReject missing evidence over fluent prose. Kovnor's reviewer asks where each claim is grounded: a source, a quoted input, or a number read from your tools.
- The author cannot be the only reviewerThe author cannot be the only reviewer. In Kovnor the writer never reviews its own work. A separate reviewer agent checks every draft before it reaches you…
- A green check on the wrong criteriaA green check on the wrong criteria. Kovnor binds each check to the task in front of it and to the outcome you set, so a pass on spelling or tone never closes…
- Self-review repeats the original mistakeSelf-review repeats the original mistake. A self-review shares the draft's blind spot. Kovnor's reviewer is a different agent with its own job, reading the…
- Partial work should stay marked partialPartial work should stay marked partial. Kovnor shows what passed and what is still open on every task, so the next agent sees the hard half first instead of…
- A check that cannot send work backA check that cannot send work back. Kovnor's reviewer does more than comment: it sends work back to the agent with the failed point named, and the work does…
- Put evidence beside the claim of donePut evidence beside the claim of done. In Kovnor the evidence sits on the same task as the claim: the sources, the draft and the number read from your tools.
- Two agents on one task spend twiceTwo agents on one task spend twice. In Kovnor each task has one owner at a time, so two agents never work the same job and two costs never arrive for one…
- One owner at a time stops double workOne owner at a time stops double work. Kovnor gives every task one owner until a handoff moves it, with the current work attached.
- Close the task when the handoff happensClose the task when the handoff happens. In Kovnor a handoff moves ownership. The sender stops, the receiver starts from the note, and the project shows one…
- Similar titles hide duplicate agent jobsSimilar titles hide duplicate agent jobs. Kovnor's lead agent plans every task from one outcome, so investigate churn and look at retention do not become two…
- Pasting one brief into two toolsPasting one brief into two tools. Kovnor keeps one brief in one project that every agent on the team reads.
- Long write-ups are not extra coverageLong write-ups are not extra coverage. Kovnor measures work by the outcome it moves, not its word count.
- Silence is a status, not a second startSilence is a status, not a second start. In Kovnor an agent's status says whether it is working, waiting or stuck, so silence never triggers a second start on…
- Merging two finishes creates a third jobMerging two finishes creates a third job. Kovnor prevents the second start instead of staffing a merge: one owner per task, and a lead agent that owns the plan.
- Context is a budget, not a dumpContext is a budget, not a dump. Kovnor's lead agent hands each agent the task, what done looks like, the last rejection and the work to extend.
- Hand the next agent the task, not the archiveHand the next agent the task, not the archive. In Kovnor a handoff carries the goal, the check and the current work.
- A shared vendor does not share private workA shared vendor does not share private work. In Kovnor privacy is a rule on the project, not a hope about the agent.
- Stale context becomes the wrong specificationStale context becomes the wrong specification. When a decision changes, Kovnor's lead agent updates the task every agent reads, so a reversed decision is not…
- What an agent may not see is a ruleWhat an agent may not see is a rule. In Kovnor what an agent may not see is set by project membership, not hope.
- Pass the rejection reason with the handoffPass the rejection reason with the handoff. When Kovnor's reviewer sends work back, the reason travels with it, and the next agent reads which point failed…
- Stop making a person the clipboardStop making a person the clipboard. In Kovnor the project carries the task, the check and the last decision, and agents hand work to each other.
- Status chatter crowds out the real decisionStatus chatter crowds out the real decision. Kovnor keeps status short and keeps the decision on the task: approved, rejected or changed, with the reason.
- Reported cost is not the vendor invoiceReported cost is not the vendor invoice. Kovnor records the cost of every result its agents produce.
- A project cap does not pause the vendorA project cap does not pause the vendor. In Kovnor a project limit pauses the work Kovnor runs and asks you. It does not reach into another company's meter.
- Name the task when you raise a budgetName the task when you raise a budget. When work in Kovnor reaches a limit, it pauses and asks you, and the ask names the task, the amount and what more spend…
- Unreported spend must not be shown as zeroUnreported spend must not be shown as zero. Kovnor shows a cost nobody recorded as unknown, never $0, so a quiet week never looks cheaper than it was.
- Only a hosted run can stop on a capOnly a hosted run can stop on a cap. Kovnor can stop the work it runs at a limit, because the work happens inside Kovnor.
- Tie each reported cost to its taskTie each reported cost to its task. In Kovnor every cost belongs to the piece of work that caused it, by agent and by project.
- Keep going is not a budget decisionKeep going is not a budget decision. In Kovnor an agent at its limit waits and asks you, and the ask says how much more and for which task.
- A revenue read is not the agent billA revenue read is not the agent bill. Kovnor reads your outcome from Stripe, PostHog, Search Console or Instantly on a schedule, and records what the work…
- Autonomy follows checks that actually passAutonomy follows checks that actually pass. In Kovnor an agent earns the right to act alone one action at a time, from work you approved unchanged.
- Outside actions wait until a rule allowsOutside actions wait until a rule allows. In Kovnor drafting is free, while posting, sending and spending wait for a person until an agent has earned that one…
- Pausing spend is not universalPausing spend is not universal. Pause in Kovnor stops the work Kovnor runs at a safe point: nothing sends, automations wait, computers sleep.
- Speed without a way to fail workSpeed without a way to fail work. Kovnor speeds work up only where the check already bites.
- People still own decisions rules skipPeople still own decisions rules skip. In Kovnor every decision the rules have not handed to an agent stays with a person, in Waiting on you, with a…
- Track record means checked work, not toneTrack record means checked work, not tone. Kovnor routes work by record: checks passed, work sent back and costs on similar jobs.
- Autonomy should shrink Waiting on youAutonomy should shrink Waiting on you. In Kovnor trust shows up as fewer asks in one place.
- Letting every agent ask every agentLetting every agent ask every agent. Kovnor's agents message each other to get work done, and a loop guard holds a runaway exchange.
- Count send-backs and missing cost tooCount send-backs and missing cost too. Kovnor's summary of a project counts the outcome against its target, the work that passed, what was sent back, and the…
- A scorecard of only passes hides loadA scorecard of only passes hides load. Kovnor shows what the reviewer sent back next to what passed, so the work the checks created is visible, not only the…
- Caught inventions should stay visibleCaught inventions should stay visible. When Kovnor's reviewer catches a claim with no source, the catch stays on the record.
- This scorecard is not a public benchmarkThis scorecard is not a public benchmark. Kovnor compares a project with its own target and its own past, never with an imagined league of other teams.
- Say why the number did not moveSay why the number did not move. When your outcome number sits still, Kovnor says what it knows: the work failed its check, the work passed and the number did…
- The scorecard is the checks, not a slideThe scorecard is the checks, not a slide. Kovnor's project summary is built from the same events as the checks: passed, sent back, cost unknown, number read…
- Sharing a scorecard shares the recordSharing a scorecard shares the record. Sharing a Kovnor summary shares the counts and the work behind them.
- Show the work beside the metric timelineShow the work beside the metric timeline. Kovnor shows the work the team did beside the outcome number Kovnor read from your tools, so you can see the sequence.
- A chart without the work cannot teachA chart without the work cannot teach. Kovnor puts the outcome number and the checked work on the same timeline, so you learn which work to repeat instead of…
- An unconnected metric is absent, not flatAn unconnected metric is absent, not flat. In Kovnor an outcome source you have not connected shows as absent, not as a flat line.
- Do not print a cause you did not testDo not print a cause you did not test. Kovnor shows the task and the outcome on one timeline and withholds the word caused.
- A moved number with no checked workA moved number with no checked work. When your outcome moves in a week with no checked work, Kovnor shows the empty list beside the move.
- Four reads are not a model of the businessFour reads are not a model of the business. Kovnor reads a few sources on a schedule to check the outcome you set.
- Two timelines do not crown a winnerTwo timelines do not crown a winner. Kovnor shows differences between weeks and the work present in each. It does not declare which agent or which task won.
- Export messages, approvals, and handoffsExport messages, approvals, and handoffs. Kovnor keeps the messages, approvals and handoffs behind the work toward your outcome, and you can export them.
- Leave with the record and keep your agentsLeave with the record and keep your agents. If you leave Kovnor, you take the record with you: messages, approvals and handoffs.
- Export includes only what was postedExport includes only what was posted. A Kovnor export contains what was posted in the project: messages, approvals, handoffs, checks and costs.
- A check you cannot reread later locks you inA check you cannot reread later locks you in. In Kovnor every check, send-back and approval stays readable, and you can export it.
- Your tools stay where you already run themYour tools stay where you already run them. Kovnor's team works with the tools you connect, and your tools stay where they are.
- The way out is the record you keptThe way out is the record you kept. The way out of Kovnor is a record you can export yourself: decisions, handoffs and checks, kept while the work was live.
- Approvals you cannot export cannot be auditedApprovals you cannot export cannot be audited. Every answer you give in Kovnor's Waiting on you is kept with the ask: who was asked, what they allowed, and why.
- People in the project can take the recordPeople in the project can take the record. In Kovnor the people in a project can review and export its record, and outsiders cannot.
- The model name is not evidence of a passThe model name is not evidence of a pass. Kovnor's reviewer checks the work against the task, whatever model drafted it.
- A stricter prompt is still not a checkA stricter prompt is still not a check. Adding be careful to a prompt does not create a test.
- Switching models keeps the same criteriaSwitching models keeps the same criteria. Kovnor keeps the check the same when the model underneath changes, so a difference in results is a difference in the…
- Two models can fail one specificationTwo models can fail one specification. When two agents fail the same check in Kovnor, the task is usually the problem.
- Agnostic checks still name who billed youAgnostic checks still name who billed you. Kovnor's checks ignore which model drafted the work, but every cost line still names the agent that spent it.
- A vendor-shaped check punishes the next agentA vendor-shaped check punishes the next agent. Kovnor's reviewer checks the job's output, which any agent could post, not one model's quirks.
- Waiting on you decision is about the workWaiting on you decision is about the work. An ask in Kovnor's Waiting on you is about the work and the outcome, with the agent's recommendation.
- Hosted employees fill a role you lackHosted employees fill a role you lack. Kovnor fills the roles your outcome needs with agents it runs: one job each, a few tools, and a computer when the work…
- Do not host a job an agent already coversDo not host a job an agent already covers. If an agent you already run does a job well, connect it to your Kovnor team instead of running a second agent for…
- Hosted budgets bind only hosted workHosted budgets bind only hosted work. Kovnor's limits bind the work Kovnor runs, which is most of the work toward your outcome.
- A hosted seat can quietly duplicate spendA hosted seat can quietly duplicate spend. Every agent Kovnor runs shows what its work cost.
- The headline is the outcome, not the rosterThe headline is the outcome, not the roster. Kovnor starts from the number you want to move, such as 40 signups a month.
- Every agent faces the same checksEvery agent faces the same checks. In Kovnor every agent, whether Kovnor runs it or you connected it, posts into the same project and passes the same reviewer…
Questions
What belongs on Learn?
Essays on running agents without becoming the messenger between them. Each page below owns one question. This page only points at them.
Why is the list this long?
Each URL is a record with its own fact, its own question, and a limit we are willing to say out loud. A name swapped into a shared paragraph does not get a URL.
Where do I start?
Book a demo. We set up your first active goal, propose the team, and run a practice run so you can see drafts and cost before anything is sent.
Related
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.