exe.dev Blog

In classic soft-launch style, their blog is quite good. I really liked reading how they're doing ssh forwarding similar to http reverse proxies using the 'host' header [0] [0] https://blog.exe.dev/ssh-host-header

Yes that’s certainly a great feature and they don’t have it currently. For what it’s worth, they do have a teaser about “Persistent disks with some really interesting work coming soon.” https://blog.exe.dev/meet-exe.dev

i really hope OpenCode v2 with the Effect internals can ascertain and realize and lock on to being the best extensibility platform, on to having a core that serves not just itself, it's conceits of/as product, but a wider world. a street that wants to "find it's own uses for things". it feels like there's still a strong layer of "for us" vs "for you" within opencode, that i hope, over time can get chewed away at. plugins to rebuild history, to re-title are just impossible, for example. none of these changes, these freedoms are hard to release. the patches i juggle are easy. but whether or not my agentic software serves as a substrate for my desire, or whether it allows me to augment agency: tis the question. Dax (opencode lead) has such humble takes, is so forthwith about trying failing trying again on and on. about iterative improvement. and it feels like the guts are so in line to deliver, to allow such freedom now in OpenCode. but i don't see the product (anti-product) alignment, where opencode understands that it's competition isn't cc or codex, which can't and won't ever really compete, but pi, that the competition is to be the putty, to deliver the agency, to be a substrate. really hoping, because i love opencode, and these internals in v2 are sick. the "devtools must be open sourced" debate comes screaming into the fore on this. it certainly argues similar to the post here: that it is minimalism, it is adaptability, programmability, it is directability that unlocks…

Hi, author here. FWIW, the only people I coordinated with are my colleagues at exe.dev. Philip wrote a blog post a week ago on the topic too: https://blog.exe.dev/customizing-shelley. In retrospect, I should have sent drafts of this to other people I know thinking about new dev tooling to get their feedback! A bit more private discussion could have let me polish this more. We are all busy discovering the shape of new tools and norms as our profession has been overturned by LLMs. It is not too surprising similar ideas are floating about. Though I have not seen anything that captured how I now go about personalizing programs, and how I expect it to change our industry. So I wrote this.

Cool, thanks for sharing. How would you compare Shellbox with exe.dev? [1] https://exe.dev [2] https://blog.exe.dev/series-a

If you look at the actual cost of your Claude Code conversations, you'll see that the cost is overwhelmingly dominated by the cost of input tokens (cached). Because of how we construct persistent conversations, each cached input token incurs cost on each API request, meaning that component of cost scales with O(request count). If you graph the cost curve of a claude code session, it's very obvious that this scaling factor overwhelms the cache discount. Here is a blog post that shows some data - https://blog.exe.dev/expensively-quadratic. And I can confirm this is true for Claude Code - I set up a MITM capture for all Claude Code requests and graphed it. So increasing Request Count that reuses the same prefix (which is what higher compaction thresholds do) really does lead to (substantially) higher API costs.

I’m not sure that it’s O(N) with caching but this illustrates the N^2 part: https://blog.exe.dev/expensively-quadratic

Oh wow, thanks for those numbers! Since mmbleh mentioned Linode I'm guessing they're more concerned with traffic from servers, where CGNAT is uncommon. But even that may be changing - https://blog.exe.dev/ssh-host-header

The blog doesn't work on Firefox on Android for me https://blog.exe.dev/meet-exe.dev Secure Connection Failed The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Please contact the website owners to inform them of this problem.

In https://blog.exe.dev/meet-exe.dev s/cloud computing should like/cloud computing should be like/