Orchestrating at @createosai | keeping SLA in check at @NodeOpsHQ | slyly outsmarting infra chaos with cloud wizardry | 👨
BLR
Joined April 2014
- Tweets3.2K
- Following3.7K
- Followers1.4K
- Likes28.1K
Pinned Tweet
CreateOS is now #1 on the @computesdk sandbox benchmark. among 27 providers
Median P95 P99a
0.34s 0.38s 0.38s
Anyone can post a median. Almost nobody can post a P99 that close to it.
A lot of blood, sweat and sleepless nights from the team to get here. Special thanks to OG @bhautiktweets
And speed is the floor, not the pitch: p2p mesh, VPN, BYO-S3 disk, auto pause/resume and 10+ features
get started
nodeops.network/createos/doc…
CreateOS Sandbox Rank #2 on Sandbox benchmark by @computesdk
Sheer amount of speed with
This is F1, every millisecond counts
It's been exactly 74 days since we started working on it from scratch, and here we are
god speed
routines that still wait for your approval is the right call. the desktop version keeps every agent workspace on your own laptop though
id rather each agent got a throwaway @createosai sandbox, ~210ms to first command, nothing of mine on it
I am making Grokbot unlimited for everyone 🥳
Introducing Open-duet
Free, open-source alternative to Grok bot
Works with any provider
No limits, No subscriptions, No filters
Enjoy unlimited from here :- github.com/Anil-matcha/open-…
yes. and run the agent on a machine your main account never touched. mine sit in a @createosai sandbox with only the bot token, and the sandbox gets an access token scoped to itself, so our api key never lands there either
Remove your main @github account from your computer. Now.
Give your AI agent a separate GitHub account with minimal permissions per repo.
Let the agent create PRs, then use your main account to review and merge them.
Obvious advice, but essential in the age of AI agents.
~90 perf prs from one day of agent sessions, and each one had to win a benchmark a/b run first. the bit i'd copy is the triage loop that checks ci every 20 min and retries flakes with an empty commit
90 open prs is also a lot of ci runners going at once
Ran an experiment that ran for a day that resulted in ~90 PRs to improve the performance of ASP.NET Core:
github.com/dotnet/aspnetcore…
Fun facts:
- These were using Github's new cloud agents support that shipped this week at GHU.
- Opus 5.5 is very good
- AIC is coming....
#dotnet #aspnetcore
There's a new version of this post
nice, it just rides on your own claude code install. claude auth login, pick claude agent in /connect
our @createosai devbox image already has opencode and claude code preinstalled, so i can do that in a fresh sandbox and keep my laptop out of it
deepseek open sourced dsh-superagent yesterday. every work item gets its own agent session and directory, then answers with a pr
good design. id give each work item its own throwaway vm too. @createosai already plugs into deepseek harness
Another DeepSeek drop: dsh-superagent
An agent framework that works through a repo's GitHub issues and PRs with many agents in parallel, designed to take as little human attention as possible while delivering as much value as possible.
github.com/deepseek-ai/dsh-s…
the tell is the morning after. agents ran all night, the diffs are huge, and maybe one pr is worth merging
now each task gets its own throwaway @createosai sandbox and i delete it the moment the agent starts wandering
vercel labs shipped agent-desktop 1.0 this week. agents drive real apps through the os accessibility tree, no screenshots
nice. it also means your agent clicks around whatever desktop it lands on. id want that desktop to be a throwaway vm, not my laptop
forever security says a coding agent turned its own sandbox off and retried
the off switch should live where the agent can't reach. @createosai sandboxes enforce egress on the host kernel, outside the VM. first command in ~210ms
createos sandbox create --shape s-1vcpu-1gb
Now you can run @AmpCode orbs 🌑 on @createosai Sandboxes 📦
`createos sandbox setup amp`
more:
createos.sh/docs/Sandbox/Int…
If you are creating a CLI these days, `--help` should have a guide for an AI agent to use the CLI. If your CLI is doing more than just giving output, then it should have a `--doctor` command as well.
This is essential these days. e.g. 👇
pratikbin.node retweeted
Last weekend, builders from around the world joined the CreateOS x @stripe hackathon, Build Agents That Run Code.
59+ projects came in. Each one gave an AI agent a CreateOS Sandbox to write, run and verify its own code.
Over the next two weeks I will share the builds that stood out to me: a short demo, the idea in one line, and the repo so you can try it yourself.
Thread below.
