@exedev
Account based inUnited States
About this account
- Account based in
- United States
- Connected via
- Web
Account-level information from X, not a live location or the device used for a specific post.
Computers for developers and agents.
Joined August 2025
- Tweets138
- Following28
- Followers3.3K
- Likes180
exe.dev retweeted
New lower pricing for the base @exedev individual plan: $15/month for 2 vCPUs / 4 GB memory. Instead of included tokens, link your ChatGPT subscription.
We launched pools. Group your VMs, pay for compute: blog.exe.dev/pools-our-newes…
What's going on with the air quality in San Francisco? We built a fire map to find out: blog.exe.dev/what-s-going-on…
Share Shelley skills across all your VMs: blog.exe.dev/shelley-skills-…
"My old mindset was wanting a bot to nag me into doing the thing. The new mindset is to have the bot take the task as close to the finish line as possible." blog.exe.dev/cron-vs-vm
"In this new era of 'I can build anything,' this often means you first have to make a choice, 'do I care enough about what good looks like for this product to own the maintenance and upkeep?'" blog.exe.dev/caring-vs-knowi…
Ever wanted your agents to just talk directly with each other? Now they can: blog.exe.dev/mayfly-chat
exe.dev retweeted
finally had a usecase for @exedev today and holy shit this is amazing
exe.dev retweeted
asked claude if we could easily add a minimal remote desktop on an @exedev vm and a few mins later have this accessible from any browser:
💯 we've set up quite a few bots along these lines: blog.exe.dev/inventory
I have this really brittle Zapier integration that takes a Google Sheets updated by a partner a few times per week, and upon update, invokes my API to add a paid subscriber to my newsletter. So many clicks and onboarding to setup and learn Zapier. Costs $200/yr to run.
But with AI: setup is so much easier, no UI needed (eg with Grok Bot). The cost is higher right now ($200/month for Grok Bot), but as soon as prices for "cron AI jobs" drop, either Zapier will be in trouble, or they will get rid of this point-and-click UI that I now no longer want to touch when I can describe my workflows.
exe.dev retweeted
underrated. Going to be trying out @exedev for agent sandboxes and agentic dev workflows via Hermes (thanks to @IndyDevDan for recent video on topic, will link below)
The sane way to run Hermes on mobile: youtu.be/7IzpuXHgDMw
We taught sqlc to invalidate our caches: blog.exe.dev/we-taught-sqlc-…
ALT Of course, information changes over time. People can change the sharing status of their VMs, VMs can move to different hosts, and in general the routing information that the proxy is using can change. So while using a cache is efficient, it means that we have to handle what is notoriously one of the two hard problems of computer systems: cache invalidation (the other hard problem is naming; also, off-by-one errors).
The sane way to run Hermes on mobile: youtu.be/7IzpuXHgDMw
When working with agents, is it better to plan or iterate? blog.exe.dev/planning