This is for monitoring/poking agentic coding sessions while I'm not at my computer. So, typically Claude, Emacs, and an overmind process running my app locally in different panes of a tmux window.
Call me old fashioned, but instead of adopting one of the "agentic coding orchestration frameworks" that seem to basically be reinventions of tmux, I've been tweaking my tried-and-true tmux-oriented workflow to incorporate agentic coding harnesses in an ergonomic way. I'm currently still using Claude Code, but getting Pi-curious as local models advance.
@fastidiousprofilefollow
"Beware those that would deny you access to information, for in their heart they dream themselves your master." — Sid Meyersreplied to:
"Beware those that would deny you access to information, for in their heart they dream themselves your master." — Sid Meyersreplied to:I will be dead, and many years will pass after that, before local models are capable to match those of the big companies, unless their intended use is banal.
replied to@fastidiousprofilefollow"Beware those that would deny you access to information, for in their heart they dream themselves your master." — Sid Meyers:
"Beware those that would deny you access to information, for in their heart they dream themselves your master." — Sid Meyers:It seems like we've reached a point where mid-grade frontier models like Sonnet are good enough for most day-to-day tasks. And Sonnet-grade models are already runnable on the higher end of consumer hardware.
In which case, I can imagine a workflow where local models serve as workhorses for implementing plans that you may bump up to e.g. Opus or Sol to produce.