[flagged]
Show HN: Axe – A 12MB binary that replaces your AI framework
101–110 of 145 posts
Re: Show HN: Axe – A 12MB binary that replaces your AI framework
#102Cool work! Aside but 12 MB is ... large ... for such a thing. For reference, an entire HTTP (including crypto, TLS) stack with LLM API calls in Zig would net you a binary ~400 KB on ReleaseSmall (statically linked). You can implement an entire language, compiler, and a VM in another 500 KB (or less!) I don't think 12 MB is an impressive badge here?
it's written in golang. 12MB barely gets you "hello world" since everything is statically linked. With that in mind, the size is impressive.
The excessive size of Go binaries is a common complain. I last recall seeing a related discussion on Lobsters [1]. Who knows, maybe the binary could be shrunk a bit? IMHO 12mb binary size is not that big of a deal.
--
1: https://lobste.rs/s/tzyslr/reducing_size_go_binaries_by_up_7...
Re: Show HN: Axe – A 12MB binary that replaces your AI framework
#103Why not just run your typical claude/codex/pi/etc with a prompt as the command line/input?
Re: Show HN: Axe – A 12MB binary that replaces your AI framework
#104[dead]
Re: Show HN: Axe – A 12MB binary that replaces your AI framework
#105This is a great concept. I fully agree with small, focused and composable design. I've been exploring a similar direction at asterai.io but focusing more on the tool layer than agent layer, with portable WASM components you write once in any language and compose together.
I currently use Claude web with an MCP component for my workflows but axe looks like it could be a nicer and quicker way to work with the tools I have.
Re: Show HN: Axe – A 12MB binary that replaces your AI framework
#106> - Path-sandboxed file ops. Keeps agents locked to a working directory
How is it supposed to work, if agent can simply run "cat" command instead of using skill for file read/write/etc?
Re: Show HN: Axe – A 12MB binary that replaces your AI framework
#107I've had good success with something along these lines but perhaps a bit more raw: - claude takes a -p option - i have a bunch of tiny scripts, each script is an agent but it only does one tiny task - scripts can be composed in a unix pipeline For example: $ git diff --staged | ai-commit-msg | git commit -F - Where ai-commit-msg is a tiny agent: #!/usr/bin/env bash # ai-commit-msg: stdin=git diff, stdout=conventional…
I was looking at something similar. What does your agent-lib.sh look like?
Re: Show HN: Axe – A 12MB binary that replaces your AI framework
#108This is what I've been trying to get nanobot to do, so thanks for sharing this. I plan to use this for workflow definitions like filesystems. I have a known workflow to create an RPG character with steps, lets automate some of the boilerplate by having a succession of LLMs read my preferences about each step and apply their particular pieces of data to that step of the workflow, outputting their result to successive…
Where is the nanobot approach not working for you?
Re: Show HN: Axe – A 12MB binary that replaces your AI framework
#109Earlier quoted context omitted.
Clankers are not humans.
This is the second time I've seen somebody use the word "clankers" in the last couple days to refer to AI. Is that a thing now? Where'd that come from? Gonna be honest, it has taken away from the message both times I've seen it. It feels a bit like you're LARPing your favorite humans vs robots tv show.
We have been rewatching Clone Wars as a family, and I, for one, find this terminology hilarious given the use of it in the series towards the separatist droids.
Re: Show HN: Axe – A 12MB binary that replaces your AI framework
#110> - Path-sandboxed file ops. Keeps agents locked to a working directory How is it supposed to work, if agent can simply run "cat" command instead of using skill for file read/write/etc?
chroot