ivanbelenky

humble sliced public repo harness configs research, codex shows interesting traits

- overrepresentation in high starred buckets - overrepresentation in rust - if we trust proxy signal, ~50% of CC repos and growing equally as fast

it is also a harness that gets configured mainly with a toml file, single manifest is not the case but a great chunk of the configuration surfaces is sitting in `config.toml`

theta-spec is a declarative, harness-agnostic configuration standard for AI coding agents. `theta` is its canonical implementation.

We use it internally at `tamarillo.ai` and we are fully aware of its limitations, but we also feel it’s mature enough to share. This is our interpretation of what it would take to allow individuals working across different harnesses (or teams with more complex configurations) to be able to keep things consistent, or share their configurations with others.

Any feedback and contribution to the spec and reference implementation is extremely welcomed. We already support a few of the most common harnesses today.

Also when putting this together there were a lot of assumptions made, and many of those could prove to be wrong, so contributions are welcomed all the way through to the fundamentals.

At tamarillo.ai, we are building, among many other things, tooling to standardize coding harnesses. This is our humble attempt to understand one slice of their usage.