Linking to a github repo for a binary release (no source code related to the agent that I could see) is a bit iffy IMO. You should clarify your intentions or link to something else. Might confuse folks.

if you're interested in an open source agent that uses a minimal amount of CPU and RAM and has source that is easy to audit:

https://github.com/smol-env/smol

here are traces from an agentic task around using duckduckdb

comparing CPU and RAM usage of the whole container over time w/ OpenCode, hermes, pi, codex, smol

https://x.com/__tosh/status/2086882367126286466

https://x.com/__tosh/status/2086882204060160350

smol is very minimal only using stdlib (in this case it is the go version but you can also take a look at implementations in python, clojure, php)

also no need to trust these bench runs, you can just run your own

(any OpenAI Responses API compatible endpoint works, if your endpoint does not support 'custom' tools you can have your agent change the smol implementation to use 'function' tool implementation instead)

that said: be aware that smol does not come with any system prompt and does not load agents.md files by default

some older not so strong models benefit from a system prompt and guidance in agents.md that complements them

that said 2: system prompt and or loading agents.md automatically is easy to add though if you want it

[dead]

I will leave this here: https://usehax.dev/ GitHub repo: https://github.com/OleksandrChekhovskyi/hax

This is a coding agent implementation I am working on, which delivers what this promises (at least on the "lean" part), except it's actually fully open source, and even more lean (few MBs of runtime memory usage).

MIT-licensed, written in C, multi-provider / multi-model, minimalist approach to system prompt and tools (think kinda like pi, but with a bit more "batteries included", like subagents and background tasks out of the box), polished presentation, inspectable (usable transcript view), etc.

nice, good to see more contributor in this space

I was kind of excited for this until the binary blob. You want me to give your agent binary god access to my computer, and I am not even permitted to see the source code or use my own supply chain security hardened rust compiler stack? What a joke. Hard pass.

[deleted]

we put it in the repo README, will add migrate more into public repo as soon as possible.

It has to be 100% open source public code or we will have no way of proving this is not malware, or secretly swapped out for malware later when your CI/CD system or laptop is compromised. Supply chain attacks happen all the time and with closed code no one will be equipped to spot it when it happens.

Also, security aside, engineers want the freedom to modify and experiment with the tools we rely on.

Tools like this are too important to be closed. Do you want to be Internet Explorer or Firefox?

Oh no, definitely not Internet Explorer. Will figure out a way to ship with source first to address the security and concern and then figure out how to do the open source development in agentic era later, I was too carried away by the complexity of the latter and ignorant to the former.

When it is 100% freely licensed open source software I can modify and compile myself, I will be happy to give it a shot.

Open source didn't stop Jia Tan... and most people on Earth still use a closed source, proprietary browser without thinking twice.

>Open source didn't stop Jia Tan

How do you think the backdoor situation would have been resolved if xz hadn't been open-source?

Linking to a binary is iffy from a security perspective. Linking to a GitHub repository is exactly what HN should do.

A GitHub repo with no source code is exactly equivalent to linking the binary directly

there are so much content and valuable stuff in the github repo you can pretty much recreated with your own agent.