1,491 karma · joined February 21, 2026
It does involve letting go and not micromanaging every code convention and implementation detail, but that is the same skill you need when leading engineering teams.
For a concrete example, check out this random plan [0]. A detailed spec followed by the exact implementation tasks that will be executed by the subagents.
[0]: https://github.com/bensyverson/woodcase/blob/main/project/20...
I think if I was doing evals on the way an agent interacts with a service (e.g. Slack) the digital twin could make sense, but for rapid iteration or testing, it might not be what you want.
So here goes: you should not use an AI model to validate a claim which is trivial to calculate deterministically. That is (obviously?) not what a model like Jev is for, thus it is not a good test of Jev.
Base62 (or 64, with -_) is totally sufficient.
Whatever side you come down on, privacy doesn't stand a chance against a small amount of convenience.
GLM 5.3 Flash Max had an interesting showing. Its Codex version was bad [0], and it completed in 9 minutes. The OpenCode version was much richer [1] and more detailed, completed in 20 minutes. And the OMP version was arguably the most complete [2], completing in 30 minutes.
This is probably the strongest argument for the effect of a harness, and I'd be interested to learn the differences in the prompts and tools between these three.
[0]: https://alvins82.github.io/hangar-harness-model-tests/hangar...
[1]: https://alvins82.github.io/hangar-harness-model-tests/hangar...
[2]: https://alvins82.github.io/hangar-harness-model-tests/hangar...