Axe treats LLM agents like Unix programs—small, composable, version-controllable. Are we finally doing AI the Unix way?

How are people sharing reproducible AI coding sessions today? Screenshots and recordings never capture the full interaction.

“Context rot” with AI coding tools is definitely real. After a few sessions the agent forgets earlier decisions, and you end up repeating the same planning conversation again.

Storing the plan and discussion as Markdown in Git is an interesting approach. It basically treats the agent’s reasoning as part of the project history, not just the final code.

Curious if others here are doing something similar to keep context across sessions.

Nice breakdown. I’m curious how often the guard check for a function-local static actually shows up in real profiles. In most codebases Instance() isn’t called in tight loops, so the safety of lazy initialization might matter more than a few extra instructions. Has anyone run into this being a real bottleneck in practice?

At ~5KB gzipped this is impressively small. What were the biggest features you deliberately left out to keep the size that low?

Very cool project. MMO server codebases tend to accumulate a lot of architectural complexity over time, so starting fresh with a cleaner separation between networking and game logic makes a lot of sense.

Curious about the sector-based delta sync — how do you avoid packet bursts when a player enters a busy area with lots of items and mobiles?

Also interesting to see NativeAOT used here. Was that mainly for deployment simplicity or performance?

If an AI agent runs inside the page and can see the DOM and the user’s session, how do you keep it safe without limiting what it can actually do?

which AI features will I get in neo ?