Also worth noting that this text is not only entirely AI generated, but meant for other agents to read, not us humans.
Something feels off, and claims on the site do not seem credible. Def not manually verified. If it was verified, the author did not go deep enough to give credits where it's due.
The only thing I got out of the site was to see terms I never heard of.
and if you want to see what a simple harness implementation looks like you can just dive into the code and ask your favorite agent about it
And here is the original author on a podcast talking about it: https://open.spotify.com/episode/4FxEdjXldNhoh67KYVmbDu
I also have a self-evolving architecture on it, but you have to be careful, especially if you're using multiple models (still WIP).
I personally think that a lot of the words used around AI, harness, SKILLS, agents, RAG.. are make up words or close to it, words that do not have profound semantics, even though people are trying to, often after the fact, make sense of them.
It’s just popular words that are different enough that people like to use them to claim a new knowledge, or to market a product.
But we could use AI tooling instead of harness in the abstract, and it would be better to use more precise terms for more concrete use cases, agent loop, CLI, IDE..
It was a fun game at a time where papers were competing for attention, but now that it has become a proven technology, I hope we can find more precise and meaningful words.
Broadly speaking,
- Copilot only reads AGENTS.md
- Codex reads AGENTS and CONTEXT
- Claude reads CLAUDE
This ai-literacy is noise, muddling the definitions and suggesting yet-another-md-file.
I don't know any harness that solves 'Garbage Collection' in the way described here
(most harnesses accelerate context pollution and code base drift via instructions they embed into system prompts, tool descriptions and skills)
https://docs.wingman.actor/concepts/sessions/
I think there is still plenty of innovation to be had in the space. Right now everything is still pretty bundled to the file system where getting skills and things to work inside of like a virtual worker requires simulating a virtual file system (usually). I believe even in the latest opencode v2 versions it still requires that a session be bundled to a working directory, I try to avoid (some of) that in Wingman.
Then, if someone opens a PR who isn't one of those people listed, it requires them to be a reviewer.
We use it for .editorconfig; specifically, we don't want a newcomer to come in, not like a style rule, and slip in a change.
As someone who does loads of AI-driven dev and governance, I'm finding there are a lot of great nuggets here. Between him (chaos engineering) and Kent Beck (extreme programming) I'n a kid in the candy store and wanted to share.