qudat

We take a slightly different approach for https://pico.sh -- no automatic subscription, but we charge for an entire year. It's great for us because each sub is a year and if someone truly isn't using our services then it'll quietly drift into the background for the end-user.

The entire concept that we need to cater CLIs to agents at all should tell us how far away they are from being “junior devs” or “an intern” and I reject the premise.

A lack of structured output has never been a blocker for agents to work, that’s a traditional coding problem.

“Write good help text and error messages” is just good design which is self evident.

I don't get it, it looks like they are copying data to the sandbox filesystem why would that impact production data? Because the agent can re-upload the file to s3?

Wild example as it has been corrupted by VC money as well. I wouldn’t touch deno either.

Interesting analogy. Through the lens of a data driven design, all we are doing is taking data in shape A, transforming it to shape B, and then sending it somewhere else.

I think if you look purely at the numbers, the real reason TUIs are popular is claude code, everything else is background noise compared to it.

What originally got me excited to build TUIs was the concept of delivering apps over the wire via SSH. SSH apps resemble a browser in that way: no local installs required.

It's a major reason why I enjoy hacking on https://pico.sh -- deploying the TUI requires zero user involvement.

Fundamentally it cannot be much better than how well we can write the spec and then validate the results.

It’s always gonna be a multi shot process. And it can already write code good enough. That’s no longer the bottleneck.

Further, Qwen 27b is such an incredible masterpiece for coding and it can run on consumer hardware today. Anthropic/OpenAI are gonna give up on coding models very soon. There’s not gonna be any money in it when you can run your own local model for significantly cheaper.

Qwen27b is not SOTA but the value is insane. You can basically use it for small tasks and then route harder problems to opus or sonnet and boom you’ve said a lot of money.

Interesting idea. Tangentially related I’ve been using my local agent to interact with remote shells via zmx, described here: https://bower.sh/zmx-ai-portal

The use case is different but this article strikes some vague similarities around an agent API to remotely execute commands.

Thanks for the callout: we’ve been reimagining code forges by making them irrelevant with tools and tiny services like: https://pgit.pico.sh (static site generator for git) and https://pr.pico.sh (pastebin for git collab)

They are still a WIP but it’s on our roadmap to continue to improve.

how do you provide the base url?

Agreed! Over at https://pico.sh we are chugging along and having a blast. Profitable but at a scale that is manageable for us. Cheers

I didn’t think pi supported local models?

I just want sonnet 4.5 but I also want it to be fast which is trickier

I'm guessing part of it is design philosophy: mawww doesn't want splits embedded in the editor, for example.

Totally agree. Nextjs is a vehicle to sell their PaaS, every other feature is a coincidence.

What’s worse is vercel corrupted the react devs and convinced them that RSC was a good idea. It’s not like react was strictly in good hands at Facebook but at least the team there were good shepherds and trying to foster the ecosystem.

I’ve been experimenting with letting a local agent manipulate my remote servers using https://bower.sh/zmx-ai-portal

What’s exciting is how simple cli tools can be so impactful to dev workflows

Hello. I couldn't find a great way to interact with remote terminal sessions, especially ones that required multiple hops through SSH / containers so I adapted zmx to integrate with local code agents.

- https://zmx.sh/

- https://github.com/neurosnap/zmx

- https://youtu.be/CV3skPYHP4Q

Happy to answer questions

This is the key. These frontier model companies are funneling all of their time and resources into scaling, how could they possibly be researching the next phase of AI? Once scaling hits the limit the money is gonna dry up.

AGI is not gonna come from these companies

Check out: https://github.com/neurosnap/zmx

It uses libghostty to restore scrollback history and terminal state.

A similar post with more emphasis on validating changes: https://bower.sh/thinking-slow-writing-fast

Hard agree.

Single monitor workflows — which are more ergonomic — make switching spaces a necessity. It might not impact productivity but it is annoying as hell switching around spaces a lot

It’s insane and the worst part about Mac OS

To be completely fair to JJ: you can still use git commands and any aliases with it. I daily JJ in all of my repos but I created these aliases inside of git. That's one of the great aspects of JJ: it's fully compatible with git.

There is zero reason not to include a picker like helix does. I’m gonna guess 90% of everyone running neovim has a picker

Their primary goal in the last year was to move to Azure. Any massive infra migration is going to cause issues.

Because we are constantly writing variables that are lowercase. Coming up with a name that is both short but immediately understandable is what we live for. Variables are our shrine, we stare at them everyday and are used to their beauty and simplicity.

Waiting for the zig port

If you want VC money you need to put an AI spin on it.

Interesting you mention tmux because it itself resembles a terminal emulator. It has its own terminal feature matrix that controls what your parent emulator can render. It sounds like you aren’t using tabs and splits in tmux but it does include them.

It sounds like you could get away with using a tool like https://zmx.sh which only handles session persistence (attach/detach). It also uses libghostty but only for state restoration on reattach.