The pitch behind Axe is straightforward: AI agents should behave less like giant chatbot sessions and more like Unix programs. In the Show HN thread, the author describes focused agents defined in TOML, invoked from the command line, and connected through pipes such as git diff | axe run reviewer. The point is to let developers plug agents into cron, git hooks, CI, and other existing automation surfaces instead of forcing everything through a long-lived assistant UI.

The README follows the same philosophy. Axe presents itself as an executor rather than a scheduler. It supports Anthropic, OpenAI, and Ollama, and adds sub-agent delegation, persistent memory, reusable skills, JSON output, MCP connectivity, and sandboxed file and shell operations. The design is intentionally slim: a single binary, declarative configs, and composability with the shell rather than a full orchestration framework with its own worldview.

That framing matters because agent tooling is getting heavier very quickly. Many products assume large context windows, always-on sessions, and a central UI. Axe pushes in the opposite direction and says that one-shot commands and composable workflows may be the better abstraction for a lot of real engineering work. The HN post explicitly argues that good software is small, focused, and chainable, and several commenters responded positively because it matches how they already work with local models and shell scripts.

The feedback was also practical. Readers compared the idea to earlier prompt-as-program tools, asked whether the lack of a true session model is a limitation, and pushed for more concrete examples of what teams actually automate with it. That is the real question for a project like Axe: not whether the philosophy sounds good, but whether it reduces operational friction better than larger frameworks. Original source: GitHub. Community discussion: Hacker News.

#go

Show HN: Axe turns AI agents into Unix-style CLI programs instead of chat sessions