Show HN: MicroCodex Coding Agent – OpenAI/codex reimplemented in C++ <1MB binary

Posted by paoloanzn 18 hours ago

1916Original

Comments

Comment by kamikazechaser 5 hours ago

How does it compare to nanocodex (https://github.com/gakonst/nanocodex)?

Comment by orliesaurus 15 hours ago

i love the idea, but you also need to maintain it long term: in today's world what is the best practice to do that... do you spin up an agent anytime codex-cli updates and mirror the updates in c++ and push a new release? or idk... set up an automated process that does this on a worker on CF in a sandbox when npm updates @openai/codex?

Comment by paoloanzn 9 hours ago

there is already a wrapping script when you install it, every time i publish a new release it will detect it a prompt it to update (if you want to).

Comment by fractorial 17 hours ago

I’m not quite sure why the harness itself needs to be small. Isn’t the system prompt and management of system prompt the bit you want lightweight?

Comment by userbinator 17 hours ago

"Why does it need to be large?" should be the question instead.

Comment by selcuka 15 hours ago

A harness needs to be good. Being large is annoying, sure, but it's generally not an issue. Unless this one has feature parity with the "large" ones (hint: it doesn't), I don't see any reason to use it only because it's small.

Comment by paoloanzn 9 hours ago

I ported almost every key feature already tbh. Of course there will always be a compromise, but there is even still margin to add more. Tools, skills, context compaction, it’s all already implemented.

Comment by selcuka 8 hours ago

I haven't actually tried it, my comment was based on the "Known bugs and issues" section in the readme (e.g. no MCP support yet). Apologies if that section is out of date. If the functionality is on par with the mainstream ones, then sure, small and lightweight is preferable.

Comment by paoloanzn 45 minutes ago

Actually the MCP support is really one of the only "key" things we had not brought over yet, but please feel free to open an issue or a PR!

Comment by cyanydeez 15 hours ago

ultimately, the harness is just going to be another model specifically engineered to be deterministic, like ballbearings in a wheel minimizing friction.

Comment by K0IN 16 hours ago

I think it's nice to have options, but I also don't see the appeal in "sub x mb" (except as codegolf or just for the hacky part, for day to day this does not matter) especially if features are missing or other compromises have been made just for the sake of remaining small.

Comment by paoloanzn 9 hours ago

I’m mainly looking also at running a cli agent inside a small device, with few resources.

Comment by embedding-shape 13 hours ago

Probably you want all of them to be as simple and small as possible, especially if you want to use it to work on itself. Smaller codebases are (generally) easier to work with.

Comment by adithyassekhar 11 hours ago

Sometimes smaller software has the harder codebase.

Comment by embedding-shape 5 hours ago

Damn, you really got me there, nothing in my comment could have possibly have guarded against that not every smaller codebase is easier to work with. If only there was a way in English language to indicate side-thoughts, optionals and asides, but oh well.

Comment by paoloanzn 9 hours ago

What about running agents on embedded devices with small resources? maybe even multi agents flows? good luck trying to do that with codex, let alone claude code