Sculptor: the missing UI for Claude Code 🎨 Imagine running 5 Claudes in parallel, safely in containers, while you stay in flow. Then bring their work straight into your IDE to test/edit together. This is how one developer ships like a team. Try it with Sonnet 4.5!

Sculptor works with your existing Claude Code subscription. Thanks to all our alpha testers for helping us get this far ❤️‍🔥 Hop into our Discord to share feedback and shape where Sculptor goes next! Download now:

Follow @imbue_ai to get product updates! Join Discord to chat directly with our team:

I've been using for the past few days: - Works well, pairs with your existing claude code subscription - Safely code in a docker container in your pc, no mix, you judge, test, merge when you feel like it - abstract of git operations is very useful, can fetch, pull, create branch Overall sick product, 10/10

Thanks Andrew — your feedback has been awesome!! ❤️‍🔥

Excuse my ignorance, how is this different than Conductor, or is it just a different take at the same problem?

Great question! Agents in Sculptor run in containers vs. locally on your machine, so they can all execute code simultaneously (and won't destroy your machine). Containers also unlock a cool agent-switching workflow, Pairing Mode: Ultimately, our roadmaps are pretty different — we're focused ways to help you easily verify agent code, so over time you can trust it more and work at a higher level.

Got it, will try it out today, thanks for the swift explanation!

so excited for you to try it! it's still early, so we'd love your feedback — our whole team's in Discord, feel free to join us:

Just joined!

meme fodder @kanjun

Is the main difference between Sculptor and Conductor (from @charlieholtz ) that Sculptor is using containers? Curious what the reason for going with containers instead of worktrees was, security?

The main diff today is containers and the agent pairing/collaboration model that enables! You can e.g. run multiple instances of a NextJS app in parallel, which isn't possible with worktrees: The main reason for containers is actually our future roadmap — we're focused on ways to let you verify agent code faster so that you can work at a higher level. This requires having parallel agents all running code simultaneously, which you don't want on your local machine! More details: For more details:

@charlieholtz Ah that makes a lot of sense, give each agent access to the entire stack it needs to verify e2e changes. Thanks for sharing! Very cool 👌

@kanjun looks cool! but FYI you *can* run a bunch of NextJS apps in parallel in Conductor via worktrees. in fact for NextJS it's especially easy, because it automatically increases the port number for you. I made a video about our workflow here:

@kanjun in either case it feels like the bottleneck quickly becomes RAM eg I want to run my NextJS app with postgres and a few other services in isolation running >3 instances of the full stack will blow up most machines

Ah, yeah — 1. For now if you use Sculptor, just run one instance of the app locally. Then when you "Pair" with an agent, we just pull the agent's code/git state from its container into your local IDE, and you can reload and see the changes / run tests locally. 2. But then the agent isn't as autonomous — we'll be adding support for remote containers in the future so you/the agent can run full instances of the app.

@grok is it true?

Congratulations!!

thanks Jascha!!

Congrats! We're constantly waiting for Claude code to finish responding. Parallel agents is great

we were constantly waiting too! it's really fun to work in parallel — give it a test drive and let us know how it goes

10/10 editing, love a blooper moment. Congratulations team!

thank you, Kaitlynn! so many bloopers in those takes 😂

It’s so satisfying to have a fleet of Claude Codes at my disposal!

🔥💯

woo, so proud of our team! can’t wait for the world to experience the power of Sculptor 🙌

Congrats on the launch

thank you, Hadi!! that means a lot to me ❤️‍🔥

Amazing. Congrats team!! 🎉❤️

So excited to try this!!

Yes YES THE SCULPTOR IS OUT

This is an amazing product btw, highly recommend.

thank you! ❤️‍🔥

Combining the throughput of async coding agents with the collaboration ability of agent CLIs is such a game changer.

Congrats guys!!

thanks Gary! if you try Sculptor, don't hesitate to ping if you run into any issues :)

i've had a lot of fun working on this--sculptor is much better for making production-quality code than any other ai coding tool i've used

this looks slick af trying it out later

excited for you to try it!! feel free to share any feedback (or bugs) in discord — our whole team's in here:

Congrats! 🥳 It was a blast sculpting the launch with you and the team. Can't wait for devs to experience the joy of parallel coding w/ Sculptor!

we couldn't have done this without you!!

running agents in parallel has been a game changer and will be table stakes going forward -- so excited to share things we're cooking up behind the scenes

Yay! Very excited for sculptor to be out in the world!

Congrats Kanjun and team on the launch! Very excited to see a real UI for Claude Code

thanks Spenser! if you still make side projects, would love for you to try it :)

I’ll ask our Amplitude team

yaaaaas 💪 we use Sculptor to build Sculptor, and it helps a lot :)

Interesting, congrats. So is it geared toward building new things from scratch rather than working on a old big codebase? As you mention every agent works on an isolated container, so I could imagine 5 agents will work on 5 codebases.

@oscarle_x we have a giant monorepo and use it pretty successfully to build itself!

Congrats on the launch! Excited to pair w the Claude hive mind

🧠🧠🧠 come join us!! 😈

Congrats @kanjun @joshalbrecht and team!

@joshalbrecht Thank you, Michael! ❤️‍🔥

This is similar to a tool I built for personal use and while I haven't tried it, I will say that it is conceptually the right approach to agentic development. Focus on parallel execution in containers, organization of sessions and the review/merge workflow. Since it appears to be a web-based client/server app, consider allowing the frontend and backend to be installed separately. I'd love to be able to run this headless on my development Linux server and connect to it from other devices. That would satisfy some security requirements from my employer too where the HTTPS traffic from the container can be inspected from a central location and blocked or redacted. I have gotten Sculptor to start using X11 forwarding but I am fighting with docker/podman compatibility now on RHEL. Native podman support would be useful.

@Kevin70143227 That's great feedback, thank you! Sorry to hear that re: podman — we don't support it natively (yet). There's another person trying to get it to work with podman in our Discord ( — feel free to join if helpful!

Sculptor has quickly become my favorite tool for agentic software development! Love the focus on containerization and safe, local automatic execution of LLM generated code in my own custom environment!

Discord link for Sculptor is here: If you run into any bugs, let us know and we'll happily use Sculptor to fix them :)

Exciting stuff! A big step towards an accelerated AI-assisted SWE approach that avoids the trap of turning engineers into AI slop janitors

ooh looks nice 👀

😊 glad to hear

Super awesome. Does it only work with CauldeCode ? Sometime back, I reviewed ContainerUse from @dagger_io. I think they are also solving the similar problem with their opensource ContainerUse package.

@dagger_io Currently only Claude Code, but we're working on GPT-5 :)

@gauravdhiman_ai @dagger_io When GPT-5 hits please make this a big deal. Cursor Agent would be amazing too.

@gauravdhiman_ai @dagger_io GPT-5 is on our roadmap!

Great vid! I genuinely thought this was an Anthropic vid first 😅

❤️‍🔥 thank you! I *think* that's a compliment 😂

As a conductor user, i need to test this. looks 🔥

would love to hear your feedback! I think we have somewhat different roadmaps and both apps could be useful for different things :)