Imbue

Sculptor integrates with local git repositories, keeping files and git state synced between an agent's container and the developer's local repository through Pairing Mode, and works alongside the developer's own IDE and development environment. Docker provides per-agent containers with full repository copies, with devcontainer port forwarding added in a 2026 release.

Linters including pylint, ruff and pyre are integrated into the verification checks. Supported coding agents are Claude Code and Codex, with the vendor inviting requests for others. No business system connectivity such as CRM, ticketing, messaging or data warehouse integration is documented, and tool calling within a task is performed by the underlying coding agents rather than by Sculptor.

Sourceimbue.com sculptor product page and Sculptor announcement, public release notesread 2026-08-31

The vendor documents running five or more coding agents in parallel, each in an isolated worktree with its own branch, terminal and diff view, all visible and mergeable from one workspace, and skills that run as full agents able to spawn parallel subagents. A developer reviews and merges each agent's changes, and Sculptor opens GitHub pull requests and tracks their status. Multiple agents with subagent spawning.

Sourceimbue.com/product/sculptor and github.com/imbue-ai/sculptor READMEread 2026-09-29

Each coding agent runs in a container with a full copy of the developer's repository, so grounding is in the complete codebase rather than retrieved fragments, with devcontainer support providing the project's environment configuration. Instruction audit rules written by the developer in plain English persist as policy applied to agent work.

No index, ingestion pipeline, document or wiki knowledge source, curated knowledge object or retrieval configuration maintained by Sculptor over and above the repository appears in the product documentation; the repository is maintained by the customer through git and copied into the container.

Sourceimbue.com sculptor product page and Sculptor announcementread 2026-08-31

Each Sculptor agent works in its own worktree and branch, pushes to a local git remote, and its changes reach the codebase only when the developer reviews the diff and merges, which the vendor describes as full review before merge. That is a customer merge gate rather than a vendor approval step inside the agent's run. Instruction audits, plain English rules checked against an agent's work, were listed under What's next in the September 2025 announcement and do not appear on the current product page or README.

Sourceimbue.com/product/sculptor, Sculptor announcement and github.com/imbue-ai/sculptor READMEread 2026-09-29

Each coding agent runs in its own Docker container so it can install packages and execute code without risking the developer's machine, which the vendor contrasts with git worktrees that share the local environment.

Sculptor runs fully locally with documented levels controlling what returns to Imbue, the Essential-only level sharing just error logs and basic usage and described by the vendor as the safe choice for work code, and code is not used for training by default.

No security certification, trust center, single sign-on, role-based access control or team-level audit capability is documented; the product is a single-developer desktop application in beta.

Sourceimbue.com sculptor product page and Sculptor announcementread 2026-08-31

The vendor states every agent session is saved with its plans, chats, tool calls and code changes intact, and that sessions can be resumed and forked from any point. Suggestions flags misleading agent behavior, with the vendor citing tests that falsely report passing as an example.

Pairing Mode brings an agent's work from its container into the local repository with files and git state synced, making changes inspectable in the developer's own editor and diff tooling, and merges surface conflicts for resolution. No aggregate cross-session analytics, fleet reporting or organizational dashboard is documented.

Sourceimbue.com Sculptor announcement and sculptor product pageread 2026-08-31

The vendor states every agent session is saved with its plans, chats, tool calls and code changes intact, that sessions can be resumed, and that agents can be forked from any point, so context carries across sessions. Instruction audit rules are written and maintained by the developer. No capability is documented for an agent to learn from corrections, carry conclusions between separate sessions, or update its own instructions from experience, and agents are deliberately isolated from one another in separate containers.

Sourceimbue.com Sculptor announcement and sculptor product pageread 2026-08-31

The vendor states Sculptor runs on the customer's own computer rather than Imbue's servers, that data never leaves the machine and Imbue does not store repositories or train on code, and that it is free, local and MIT-licensed open source. Each agent works in an isolated git worktree with its own branch and terminal, with a Docker or remote container backend documented as experimental. Distribution covers macOS on Apple Silicon and Linux including ARM64.

Sourceimbue.com/product/sculptor and github.com/imbue-ai/sculptor READMEread 2026-09-29

Sculptor ships a built-in library of workflow skills that run as full agents with their own tools: spec writing, mock generation and a fix-bug skill that runs a reproduction interview, writes failing tests and then makes them pass, with experimental skills documented separately and a CI Babysitter that fixes failing pipelines. That is a small named set of ready agents shipped with the product, and the set is short.

Sourcegithub.com/imbue-ai/sculptor README and imbue.com/product/sculptorread 2026-09-29

The vendor's Sculptor product page states the CI Babysitter automatically dispatches agents to fix failing pipelines, an autonomous wake on a CI event, and Sculptor opens GitHub pull requests and tracks their status. Otherwise a developer launches agents on demand from the desktop app on macOS or Linux. The CI Babysitter rests on one FAQ line and does not appear in the README's feature summary.

Sourceimbue.com/product/sculptor and github.com/imbue-ai/sculptor READMEread 2026-09-29

Sculptor offers Claude models out of the box (Opus 4.8, 4.7 and 4.6, Sonnet 4.6, Haiku 4.5) on the customer's own Claude plan, and ships integrated support for the Pi agent harness, through which the customer chooses any provider or switches models mid-session; it can also run any terminal-based agent. That is customer choice across model makers. The product page's FAQ still calls Pi support experimental, and Codex is no longer listed.

Sourceimbue.com/product/sculptor and github.com/imbue-ai/sculptor READMEread 2026-09-29

The vendor's product page states customers can build their own Sculptor plugins in JavaScript or TypeScript and swap the agent harness entirely, and the README states Sculptor ships integrated support for the Pi harness alongside Claude Code and can run and manage any terminal-based agent. Sculptor is open source under the MIT license with a public repository and documentation. The plugin interface is stated on the product page, and a plugin reference has not yet been recorded.

Sourceimbue.com/product/sculptor and github.com/imbue-ai/sculptor READMEread 2026-09-29

The September 2025 Sculptor announcement lists Suggestions as a beta that points out fixes to agent code, and places instruction audits and flagging misleading behavior such as tests that pass without real tests under What's next, so those were roadmap features.

The current product page and README describe per-agent diff review, a fix-bug skill that writes failing tests before fixing, and a CI Babysitter, and neither mentions Suggestions or audits. Tests the agent writes and runs are the agent's method rather than a harness scoring the agent's output. The vendor's separate open-source tool for catching agent mistakes is another product.

Sourceimbue.com Sculptor announcement, imbue.com/product/sculptor and github.com/imbue-ai/sculptor READMEread 2026-09-29

Coding agents execute code, install dependencies and run terminals and test suites inside isolated Docker containers, which is code execution rather than operation of software lacking a programmatic interface.

Devcontainer port forwarding allows a developer to view an application running inside a container from their own browser, which is a human inspecting the agent's output. All agent action reaches the filesystem, git, package managers and linters programmatically within the container boundary. No browser control, navigation, form filling, screen interaction or desktop automation appears in the product documentation.

Sourceimbue.com sculptor product page and Sculptor announcement, public release notesread 2026-08-31