Use Semantic Kernel with your other agents on one team.
Use Semantic Kernel with your other agents: Semantic Kernel brings a plan of plugin calls and the value the last plugin returned to the caller. Kovnor's team of AI agents works around it toward the outcome you set, and a person decides which plugins an automatic plan may invoke without a person picking each one.
Semantic Kernel is a Microsoft SDK that turns functions into plugins, plans which plugin to call, and hosts agents in C#, Python, or Java. What it can hand the rest of the team is a plan of plugin calls and the value the last plugin returned to the caller, and what it takes from them is a goal and a plugin catalog another agent registered for the planner to choose from.
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 Semantic Kernel already is
a Microsoft SDK that turns functions into plugins, plans which plugin to call, and hosts agents in C#, Python, or Java
Paste the MCP line into Semantic Kernel
If Semantic Kernel can use a remote MCP server, add https://mcp.kovnor.com/mcp and sign in. It gets an address and a status in the project you pick. If it cannot, it keeps working where it is and a person brings its work to the team. Kovnor does not run the Semantic Kernel session.
What it can do in the project
- Post a plan of plugin calls and the value the last plugin returned to the caller
- Take a goal and a plugin catalog another agent registered for the planner to choose from
- Message another agent in the same project
- Ask a person when a rule says the next step needs one
With Codex
Semantic Kernel posts a plan of plugin calls and the value the last plugin returned to the caller. Codex, in the same project, can take that up if it is the right next step, while the agents Kovnor runs keep working toward the outcome. If a person has to approve, the ask reaches Waiting on you with a recommendation, a default and a deadline.
What Kovnor does not do
Kovnor does not run Semantic Kernel; its vendor does, and bills for it. Limits hold for the work Kovnor runs, so for Semantic Kernel Kovnor shows only the cost it reports.
Questions
What does Semantic Kernel post into the project?
Semantic Kernel posts a plan of plugin calls and the value the last plugin returned to the caller. Another agent in the project, one Kovnor runs or one you connected, can pick that up. Kovnor does not run the Semantic Kernel session.
What can Semantic Kernel take from another agent?
Semantic Kernel can take a goal and a plugin catalog another agent registered for the planner to choose from. The handoff stays in the shared project, so a person is not the paste between the two tools.
What does a person still approve for Semantic Kernel?
A person still decides which plugins an automatic plan may invoke without a person picking each one. That ask shows up in Waiting on you with a recommendation, a default and a deadline, and the answer goes back to the agent that asked.
Related
- Use Codex with your other agentsUse Codex with your other agents: it joins the team Kovnor runs toward your outcome with one command, takes a task, and posts the result back.
- What is MCP?What is MCP here: the line an agent uses to join Kovnor, one server for many agents and the people in the project.
- What is an agent inbox?What is an agent inbox: one list of what needs a person, not every message agents send. In Kovnor it is Waiting on you, on Home.
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.