My REST Client Formatter Returned 404 for Every Version
I wanted VS Code's REST Client inside Zed. One piece of the setup was dead upstream, and the part that worked was a five-line task.
Mistakes that became learning — terminal setups, productivity explorations, and the things I'm tinkering with.
I wanted VS Code's REST Client inside Zed. One piece of the setup was dead upstream, and the part that worked was a five-line task.
Porting a VS Code setup to Zed took an afternoon. Listing what had no equivalent was the part that told me something.
Compressing chat messages to save tokens sounded clever until it started blowing up my prompt cache and mangling diffs.
A day after I said the compression proxy wasn't coming back, it came back as a six-line zsh function.
workmux only tracks agents that register themselves. So I wrote a script that goes looking for the rest.
Three tools stood between me and a cheaper model. Now there's one, and the launcher that held them together is gone.
The best feature of my new multiplexer was wired to an agent I stopped using. So I went back to the one I'd left.
After years in fish, I moved my whole shell config to zsh in one afternoon. Everyone warns you the hard part is rewriting every function and abbreviation. The hard part turned out to be one variable n
A terminal multiplexer that knows when the agent in the pane is working, waiting on me, or done. That's the feature no tmux config can give you.