TENET agents are autonomous workers that make focused code changes, measure the results, and learn from the outcomes. They run on a reinforcement learning loop — keep what improves, revert what doesn’t.Documentation Index
Fetch the complete documentation index at: https://docs.10et.ai/llms.txt
Use this file to discover all available pages before exploring further.
How Agents Work
Each agent has:- A metric — what it’s trying to improve (test coverage, startup speed, code quality)
- An eval script — how to measure the metric (bash or TypeScript)
- A scope — which files it can modify
- A time budget — how long each round gets
Built-in Agents
TENET ships with 5 focused agents out of the box:| Agent | Metric | Direction | What it does |
|---|---|---|---|
test-coverage | coverage_percent | maximize | Adds tests for uncovered files. Uses jest --coverage. |
code-quality | quality_score | maximize | Reduces console.logs, any types, TODOs. Adds @purpose headers. |
cli-speed | p90_ms | minimize | Optimizes CLI startup latency. Lazy-loads, caches, reduces imports. |
telemetry-rl | product_health | maximize | Improves real user experience: startup speed, session reliability. |
onboarding-success | success_rate | maximize | Fixes onboarding edge cases in tenet init. |
Running an Agent
Agent Output
The Key Insight
Good eval = real gradient (12.8% coverage → 87% room to improve). Bad eval = ceiling (100% test pass rate → nowhere to go).What’s Next
Agent Configuration
TOML config reference — metrics, scope, time budgets.
Eval Scripts
Write eval scripts that produce real gradient.
Peter Parker
The meta-orchestrator that runs the nightly loop.
Creating Agents
Build custom agents for your own metrics.

