$ celesto claude start --name claude-work --mount ~/demo-app:/workspace> delete every file in /workspace/workspace is empty.$ ls ~/demo-appREADME.md index.js notes.md package.json# still here.
For the DevRel role at Celesto
Give your developers aReal
DevRel
You asked for something I've made that did well, not a CV. So that comes first. Then what I've already done for Celesto: installed it, read the source, and scripted a video that breaks it on camera.
Things I've made that did well.
Videos developers watched, docs they used, and rooms they showed up to.
8K+ views on a devtool walkthrough
A short video on X showing Starknet Foundry's new project templates and terminal auto-completion. Exactly the kind of video I'd make for Celesto's CLI.
the post on X ↗A video series at 4K to 8K views an episode
I created and hosted the Starknet Builder Series at StarkWare: hands-on devtool demos at 4K to 8K organic views an episode, alongside 12+ tutorials in the official docs.
4,800+ developers who showed up
Eleven developer events across India and a 5 week bootcamp with 600+ students. Getting developers to care, in person.
Quickstarts I fixed upstream
The Cyberwave quickstart's first example crashed on its first call. I traced it and got the fix merged.
cyberwave-os/docs-mintlify#105 ↗
What I've already done for Celesto.
Installed it on my Mac and read the source before writing a word. Four things I found, each with the file that shows it.
- 01
The Claude preset uses your Keychain login
On a Mac,
presets/claude_code.py ↗celesto claude startcopies your Claude Code login from the Keychain into the computer, so you don't need an API key. Smart. I call this out in the video, so people know what their agent can use. - 02
Shared folders are read-only by default
Changes made inside the computer stay there unless you add
guides/sandboxes.md ↗--writable-mounts. That's the right default, and it's the whole demo in my video. - 03
Mounts run on QEMU
Shared folders use QEMU, not Firecracker. So I timed it on my own Mac instead of quoting the homepage: a fresh computer with my project shared started in about 2.5 seconds. The very first one took 117 seconds while the image downloaded, which is worth a line in the quickstart.
guides/sandboxes.md ↗ - 04
Turning the internet off is SDK-only
Outbound access is open by default and can be switched off, but only from Python. The CLI's
cli/commands/app.py ↗--networkoffersnatorbridge, and the CLI is where most people meet Celesto first.
The video I'm making.
I told Claude Code to delete my project. It's still here.
A short video for X on where coding agents should actually run, using Celesto for the demo. No ad read, no job mention: a video about agent safety that happens to need a computer you can throw away.
- 01
Cold open
Claude Code deletes every file. Then I show the project, untouched.
- 02
Blast radius
On your laptop, an agent runs as you: your files, your SSH keys, your .env.
- 03
Laptop, container, microVM
Three places an agent can run, and why a separate kernel matters for code an AI wrote seconds ago.
- 04
The honest part
A VM is a stronger wall, not a magic one: your login still goes in, writable mounts are a choice, and the internet is on by default.
Let me make Celesto make sense.
The video is out this week. DM me on X and I'll send it the day it's up.