
Matt Evans
160 posts

Matt Evans
@EvansBuildsIt
Award-winning website and product engineer, with a background is saas marketing.














The faster people can get to something 80% done and unstable, the more they are going to crave stuff that's already 100% done and reliable.




I encourage everyone to check out @aarondfrancis 's soloterm. You can feel the craftsmanship when you use it, not just another vibe coded "mux" gui wrapped around libghostty (also awesome, btw). 5.5 controlling soloterm is OP. I have never been happy with Codex's subagent implementation -- tbf, it is clearly unfinished and in dev, but still it's lacking. Even if it were perfect, I have never been a fan of inline subagents, or actually traditional subagents in general. I prefer full codex instances each having their own full top-level operating environment. This is what soloterm fully unlocks. You can send slash commands, or anything else you could do interactively that you can't do with subagents. I have been using tmux for this but it feels heavy, is annoying the UI sucks. If I never had to ctrl+b again in my life I'd be just fine. But for a top level operator, giving codex a full interactive shell instead of its built-in one also allows it to solve a whole class of problems that were previously annoying like debugging tmux itself or other interactive shells - "why is my script failing inside of a devbox shell?" type ish. We got a real one here you guys. All 6 people who will see this post, pls support this man. OUT.

























