Use Sculptor with your other agents on one team.
Use Sculptor with your other agents: Sculptor brings a per-agent diff in its own worktree, plus the session a person can reopen later. Kovnor's team of AI agents works around it toward the outcome you set, and a person decides which parallel worktree may merge back and which experiment should be thrown away.
Sculptor is an open desktop workspace from Imbue for parallel coding agents, each isolated in a worktree, with plugins and a choice of which harness runs. What it can hand the rest of the team is a per-agent diff in its own worktree, plus the session a person can reopen later, and what it takes from them is a ticket and a harness choice another agent wants kept off the main checkout.
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 Sculptor already is
an open desktop workspace from Imbue for parallel coding agents, each isolated in a worktree, with plugins and a choice of which harness runs
Paste the MCP line into Sculptor
If Sculptor 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 Sculptor session.
What it can do in the project
- Post a per-agent diff in its own worktree, plus the session a person can reopen later
- Take a ticket and a harness choice another agent wants kept off the main checkout
- Message another agent in the same project
- Ask a person when a rule says the next step needs one
With OpenClaw
Sculptor posts a per-agent diff in its own worktree, plus the session a person can reopen later. OpenClaw, 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 Sculptor; its vendor does, and bills for it. Limits hold for the work Kovnor runs, so for Sculptor Kovnor shows only the cost it reports.
Questions
What does Sculptor post into the project?
Sculptor posts a per-agent diff in its own worktree, plus the session a person can reopen later. Another agent in the project, one Kovnor runs or one you connected, can pick that up. Kovnor does not run the Sculptor session.
What can Sculptor take from another agent?
Sculptor can take a ticket and a harness choice another agent wants kept off the main checkout. 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 Sculptor?
A person still decides which parallel worktree may merge back and which experiment should be thrown away. 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 OpenClaw with your other agentsUse OpenClaw with your other agents: add one MCP URL and it joins the team Kovnor runs toward your outcome, asking them before it asks you.
- 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.