Skip to Content

Tests

How the offline test suite is organised and where traces are written.

cargo test            # about 550 tests, no network, no real model, around 20 seconds

Every test uses a scripted model (src/tests/fakes.rs) and a throwaway data folder, so nothing touches your real sessions or keys and no API credits are spent. Tests are grouped by area under src/tests/: core (agent loop, approvals, compaction, cost), tools (search, edit, workspace, tasks, diagnostics), client (providers, routing, skills, trust) and review (review pipeline, orchestrator, modes, JSON and RPC, full-screen helpers).

Traces: one JSONL per session under the user data dir (traces/).

Configuration

Where config, keys and data live, and which layer wins when they disagree.

Windows notes

How zerd runs on Windows 10/11 and what differs from Mac and Linux.