ubermon

both points to the same outcome: plan mode within harness is dead.

not yet, but will be included in the distributed version

the point is you can redirect all the telemetry to your own exporter with nothing leaves your machine and all the benefits.

it can be opt-out, opt-in, but the telemetry needs to be there to actually improve the agent.

it is more like an actual harness with a managed and pinned llama the control is inverse.

Harness is compute and Model is data

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

yes. Offline mode is choice, should be able to run frontier one first and then figure out how do incorporate local models as real workhorse

there are still many bad players in the industry, i wouldn't mind sharing it with trusted group. But I am not yet strong enough with deal and handle all those yet.

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.

called out the most asked questions - where is the source - telemetry opt-in/opt-out in README of https://github.com/AntigmaLabs/ante

I wonder my self, was notified by a friend, but I am grateful.. Probably because of the Meta's open model release?

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

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

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.

we are migrating to public repo. will first see how to ship a binary with source code attached. the release pipeline seem to use the preview repo for attaching source.

the public repo README is updated.

there is one toy version https://github.com/AntigmaLabs/nanochat-rs README updated.

even with power of AI, we are mere human and still slow. Adding this to backlog.

feedback received, it was carry over from the preview dev build.

for now only some of core crates is migrated, will do so progressively

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.

nice, good to see more contributor in this space

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

partially, we indent to progressively add source code component to it. the crates/ is sync from the active repo in realtime.

yes, the goal is to perfect the `ante serve` so it is easy to build gui. We are building one internally to test the protocol version

will add those soon!

we have a detailed launch thread explaining and show case exactly this! https://x.com/NoCommas/status/2086835536598351955