Skip to main content
Get TENET running on your project in under 2 minutes. By tomorrow morning, your codebase will have improved itself.

​
Install

npm install -g @10et/cli

​
Initialize

cd your-project
tenet init
This creates:
  • .tenet/config.json — project configuration
  • .tenet/journal/ — session journals
  • .mcp.json — MCP server config for your agent
  • CLAUDE.md — agent instructions
  • knowledge/ — living documents (VISION, THESIS, ARCHITECTURE)

​
Setup agents

tenet setup
TENET scans your codebase and auto-creates agents with gradient: 
Detected: TypeScript, 1,414 tests, jest
Created agent: test-coverage (baseline: 12.8%)
Created agent: code-quality (baseline: 0.485)

✓ 2 agents with gradient — ready to improve
Each agent gets a TOML config and an eval script that measures a real metric.

​
Run your first loop

tenet peter agent test-coverage --rounds 3
Watch it work: 
Round 1  Baseline: 12.8%
         Agent: added 48 test cases for config loader
         After: 13.1% (+0.3%)  KEPT ✓

Round 2  Baseline: 13.1%
         Agent: added tests but broke type checking
         After: 12.9% (-0.2%)  REVERTED ✗

Round 3  Baseline: 13.1%
         Agent: added edge case tests for API client
         After: 13.5% (+0.4%)  KEPT ✓

PR #1 created automatically.

​
Set up the nightly loop

tenet peter daily
Or add to cron: 
# Run every night at 2 AM
0 2 * * * cd /path/to/project && tenet peter daily >> .tenet/logs/nightly.log 2>&1

​
Check results tomorrow

tenet status

Coverage:     12.8% → 13.5%  overnight
Code quality: 0.485 → 0.51   +3 issues fixed
Tests:        1,414 → 1,493  +79 new

2 PRs merged while you were asleep.

​
What happens over time

WeekWhat changes
1Journals accumulate. Memory indexes patterns.
2Agents remember past decisions. “It recalled that architecture choice from last week.”
Month 1Policy head trained. Agents try smarter experiments.
Month 3World model understands your project. New team members inherit full context.