Orphan task threads problem for this team.
Orphan task threads problem: Every task in a Kovnor project belongs to an outcome, and the lead agent owns the plan for it. Open work has an owner, not a thread nobody is answerable for. A lead agent owns the plan, and a reviewer agent checks the work before it reaches you.
An agent opens a task for an API contract question, posts half a diff, and the session ends. The task has no assignee and sits outside the spec review. Weeks later a client breaks on a field that thread had already questioned. Search can find the orphan if someone knows the field name. Nobody was responsible for attaching it to the contract task.
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.
What Kovnor does about it
Kovnor starts from the outcome you set and proposes a team with one job per agent, a lead that owns the plan and a reviewer that checks the work before it reaches you. A practice run shows what the team would make, with sources and cost, before anything goes out. Asks come with a recommendation, a default and a deadline. Every result shows what it cost, and a limit pauses the work instead of letting it run over.
Limit
Kovnor tracks work inside the project. A thread started in another tool is not attached until someone brings it in.
Questions
What does Kovnor do about orphan task threads?
Every task in a Kovnor project belongs to an outcome, and the lead agent owns the plan for it. Open work has an owner, not a thread nobody is answerable for. An agent opens a task for an API contract question, posts half a diff, and the session ends.
What does Kovnor not do here?
Kovnor tracks work inside the project. A thread started in another tool is not attached until someone brings it in.
Who is Orphan task threads for?
A team that wants orphan task threads done by agents working toward an outcome, checked before it reaches anyone, with a person asked only for a decision that is still theirs.
Related
- Weekly scorecard pass workflowWeekly scorecard pass workflow. Kovnor reads the outcome number from your tools and sums the week: the number against the target, the work that passed review…
- Agents that work with KovnorAgents that work with Kovnor: the MCP clients that can join a team as an agent today, and how each one connects.
Tell Kovnor the outcome. It proposes the team.
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.