Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

  • Hacker News
  • Wow. Great concept!
  • so it is just llamafile with few additional application in bundle?
  • it is more like an actual harness with a managed and pinned llama the control is inverse.

    Harness is compute and Model is data

  • Considering that ripgrep, git, and, you know, other dev tools are part of the toolbox, then why ship them inside this executable? And, furthermore, if you ship them, then why stop there?
  • so it is more for being self contained and works out of box if being deployed in a bare linux environment. we tried shell out to `rg` it didn't work very well and instead spending time handling the args parsing and jugging string output, we decided to spend time on building Grep natively for agent. It is just a start~

    as for why stop here yep, the goal is to be able to find the best sweet spot in being self contained v.s. all-in-one bloat ware. for example, we still use a bundled `tmux` skill for the orchestration.

  • called out the most asked questions - where is the source - telemetry opt-in/opt-out in README of https://github.com/AntigmaLabs/ante
  • "Is there telemetry? Yes, and it is opt-out: set ANTE_TELEMETRY=off"

    Opt-out every time is unacceptable. If you opt out once it should be enough. One accidental execution path without the right environment and you're spewing telemetry to spaghetti knows where.

  • > One accidental execution path without the right environment and you're spewing telemetry to spaghetti knows where.

    That would also be true with opt-in by environment variable, though.

  • How good is it to work on building games, compared to existing agents? I am building my own game?
  • we have a detailed launch thread explaining and show case exactly this! https://x.com/NoCommas/status/2086835536598351955
  • You aren't building your own game if you have a chatbot do it for you.
    by 1bpp
  • They are a bit weird with game development at the moment.

    They can one shot entire games, with relatively minor issues.

    And obviously asking for small code snippets and integrating them yourself has been well supported for five years.

    But in Agent mode... not so much. I was asking frontier models to make simple changes to my Pong game (you know like the one from 1972) and it constantly failed to make simple changes or would break something else in the process.

    The main issue is that they can't see what they're doing. Actually one of the agents tried playing the pong game by screenshotting every frame, and it ran for about 20 minutes before I realized what it was doing, and told it to calm down.

    It takes about 10 seconds to process an image, so it was running the game at 0.1 frames per second... 600x slower than realtime. The technology is not quite there yet.

    If your game is something turn-based though, with discrete States and well-defined transitions between them, they can help out a lot more with that.

  • > We care about the harness, not the model or the prompts.

    I wonder if this is a viable approach; after all frontier model providers are betting on the opposite.

    Then again, they bundle their harness and offer subsidiary pricing - so maybe they themselves aren’t sure if models are as important.

  • my view on harness is that it is to capturing the structural mechanism with llm interacting the world. They are a dynamic duo evolving together. The technical depth will continue to grow (e.g. /goal being the new primitive, multi-agent collaboration is basic need) So it is here to stay. And it is just our focus as we don't have enough resource (yet) to improve the model and I think prompts belong to the user.

    Had a discussion recently: https://x.com/NoCommas/status/2086568454434537710?s=20

  • no source code
  • I understand that claude-code takes a lot of memory and that's bad. However, harneses are simple loops, in theory should take very little memory even if written in python or typescript. See for e.g. pi agent
  • I love pi and share many vision and value with it. But my view on harness is that it is to capturing the structural mechanism with llm interacting the world. They are a dynamic duo evolving together. The technical depth will continue to grow (e.g. /goal being the new primitive, multi-agent collaboration is basic need)

    Yes the core part is a simple loop, but we have all built toy compilers, inference engine, browsers (it is just a curl command eth) etc. The core algorithm is supposed to be simple.

    Had a discussion recently: https://x.com/NoCommas/status/2086568454434537710?s=20

  • > “while taking the time to figure out how open source should work in the agentic era”

    I can’t even guess what this means

  • generally the challenge now is that 1. how to deal with PR spams by AI bots 2. how to make the project sustainable especially when one has no distribution. when anyone can insta remix and re-package and re-sell your hard work. For knowledge sharing open source it is ok, but if you are serious about what you built, this is question needs to be answered first before make it a true community effort.
  • 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.
  • Linking to a binary is iffy from a security perspective. Linking to a GitHub repository is exactly what HN should do.
  • we put it in the repo README, will add migrate more into public repo as soon as possible.
  • 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.
  • 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.

  • 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)

    by tosh