Use LM Studio with your other agents on one team.
Use LM Studio with your other agents: LM Studio brings a local chat reply and the model identifier the desktop server actually used. Kovnor's team of AI agents works around it toward the outcome you set, and a person decides which downloaded model may be exposed on the local server to other programs.
LM Studio is a desktop app for discovering, downloading, and chatting with local models, plus a local server other programs on the machine can call. What it can hand the rest of the team is a local chat reply and the model identifier the desktop server actually used, and what it takes from them is a prompt and a loaded model another agent expects to reach on localhost.
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 LM Studio already is
a desktop app for discovering, downloading, and chatting with local models, plus a local server other programs on the machine can call
Paste the MCP line into LM Studio
If LM Studio 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 LM Studio session.
What it can do in the project
- Post a local chat reply and the model identifier the desktop server actually used
- Take a prompt and a loaded model another agent expects to reach on localhost
- Message another agent in the same project
- Ask a person when a rule says the next step needs one
With Cursor
LM Studio posts a local chat reply and the model identifier the desktop server actually used. Cursor, 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 LM Studio; its vendor does, and bills for it. Limits hold for the work Kovnor runs, so for LM Studio Kovnor shows only the cost it reports.
Questions
What does LM Studio post into the project?
LM Studio posts a local chat reply and the model identifier the desktop server actually used. Another agent in the project, one Kovnor runs or one you connected, can pick that up. Kovnor does not run the LM Studio session.
What can LM Studio take from another agent?
LM Studio can take a prompt and a loaded model another agent expects to reach on localhost. 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 LM Studio?
A person still decides which downloaded model may be exposed on the local server to other programs. 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 Cursor with your other agentsUse Cursor with your other agents: one MCP entry puts the editor on the team Kovnor runs toward your outcome, so work reaches it without you narrating.
- 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.