Overview & Result
CasaJev asks Jev for a bounded next step. When no registered tool fits, a coding agent proposes and implements a narrow tool contract; CasaJev checks it in an isolated worker, versions and registers it, then resumes the original task so later tasks can reuse the tool.
How Jev fits in the loop
- The harness presents current state and registered tools to Jev.
- Jev chooses the next bounded step or indicates that a new tool is needed.
- A coding agent builds the narrow tool, an isolated worker checks it, and the registry stores the versioned tool.
- The original task resumes and later tasks can select the registered tool directly.
How to reproduce
- Clone https://github.com/8endit/CasaJev and follow the repository's local setup instructions.
- Run a task where no registered tool fits, then inspect the narrow tool contract, isolated checks, version registration and resumed task.
- Repeat the author's tool-build/reuse example and six-task synthetic pilot without generalizing beyond the local measurements.
Why this build matters
This is a concrete tool-learning loop: Jev decides where the agent should go next while code and sandboxed checks own implementation and verification.
Limitations
- The post explicitly describes the project as a prototype and says the measurements are small local or synthetic tests.
- Linux end-to-end validation remains open; full Windows validation was pending because Docker was unavailable on the test machine.
- The author reports that graph hints showed no measured speed benefit in the six-task pilot.
- Tool-contract or API semantic drift can still escape detection when descriptors and output schemas do not change.