exe.dev - ssh exe.dev

When I was actively contributing to the Go project, my primary feed was the code review email firehose.
Issues, mailing lists, and Slack had low SNR. The finished commit history was better: it was finely polished work with some of the best written commit messages I have ever encountered. But it didn't hold a candle to code reviews for operational learning...

"Edit with Shelley"
⇄
"slinky.exe.xyz"

It has been a busy month for exe.dev! We launched in late December and have been hard at work keeping the service online.
Along the way we found some time to ship some features. Of note:
The new cp command to make a fast copy of a VM to another VM. Under the hood this is implemented as copy-on-write, so no matter how complex your configuration gets, expect your new VM in a couple of seconds....

Pop quiz: at what point in the context length of a coding agent are cachedreads costing you half of the next API call? By 50,000 tokens, yourconversation’s costs are probably being dominated by cache reads.
Let’s take a step back. We’ve previouslywritten about how coding agents work:they post the conversation thus far to the LLM, and continue doing that ina loop as long as the LLM is requesting tool calls. When there are nomore tools to run, the loop waits...