| ▲ | jauntywundrkind a day ago | |
I've only done a little of the new opencode v2 "mini" but it too offers a nice preserve-scroll by default. OpenCode is the best behaved TUI i've seen by far (they invented OpenTUI to make it so good, also in Zig), so it feels less crucial. But it's nice to have there! The "small core" model is very popular all of a sudden. DeepSeek's new harness is famously like that. https://news.ycombinator.com/item?id=49285244 OpenCode isn't quite as small, but there's very much been a deliberate attempt to drive much more into a plugin-based system. I enjoyed Dax talking about the new constitution of opencode, and the results of his agent comparing OpenCode & the new DeepSeek. https://bsky.app/profile/thdxr.com/post/3msy4gjttoc2f https://bsky.app/profile/thdxr.com/post/3msygiqyg6v2y > an architectural change we made in opencode2 is nearly everything is an internal plugin / there's 68 of them that cover our built in agents, integrations, config loading, etc i also think this is such a brilliant fun architectural twist too: > OpenCode is the first time i could justify event sourcing in a real system / everything that happens is an event which gets projected into the sqlite db https://bsky.app/profile/thdxr.com/post/3mt2qx3ktib2c it's so fun seeing new malleable software cores emerge, try to figure out how to augment agency. agentic software striving itself to extend the agency it itself offers. it's been way too long since we've had ambitions to build general system, architectures that serve more than the user. this has held computing back for far too long. this is such an excellent interesting field, of such a more ambitious computing, opening up. | ||
| ▲ | solarkraft a day ago | parent [-] | |
Thanks for the links on opencode 2! I’ve been meaning to get into this as I’ve been frustrated about some opencode 1’s behavior and design. Many of the encounters made me come up with ideas I’m happy to see they also had! As much fun as it may have been to build my own harness, I feel like the core primitives should be pretty well understood by now (in fact I envision a standard core library / API design taking shape). | ||