Kairos and auto-dream are more interesting than anything in the agent loop section. Memory consolidation between sessions is the actual unsolved problem. The rest is just plumbing tbh
good tip, just offload the heavy stuff to a vps and keep the neo for light tasks. thermal pad helps but why fight the hardware when you can throw compute elsewhere
Faced this too. Tried https://github.com/rtk-ai/rtk to compress cli output but some commands started failing and the savings were minimal. Ended up just being more deliberate about context size instead of adding more tooling on top
claude.md rules that cut "great question! here's what i'll do..." are fine. Rules that cut the actual thinking steps break the output. Don't confuse the two.
Good read. I get the point about real world usage, but I still feel like Neo might fall short with how fast things are getting heavier, especially with Node and modern dev workflows.
Feels fine today, but not sure how well it holds up a couple years down the line.
The PLAN.md question is the one worth pulling on. Once the plan lives in git or the PR it's already downstream of intent and whoever defined what to build has already handed off. The harder problem is giving agents access to the original intent, not just the implementation plan derived from it. When there's drift between what was planned and what got built, a git-resident PLAN.md makes it hard to trace back to why the decision was made in the first place.