AIgency persistence
Runs, tasks, interactions, usage, timeline events, criteria, verification reports, defects, repair iterations, and completion reports each have a dedicated repository.
AgentDock Pro
AIgency is available only in AgentDock Pro.
AIgency doesn't keep its state in memory between restarts — every meaningful record is written through a dedicated repository under src/main/db/repositories, backed by the same local sql.js database everything else in AgentDock uses. See Local database.
What's durable
Run and task definitions and their full status history, every prior task attempt, persisted interactions and their outcomes, per-task and per-run provider usage, a capped, filterable timeline of events, acceptance criteria and their evaluation results, verification reports, tracked defects and their repair iterations, and generated completion reports.
Bounded, not unbounded
Persistence here is deliberately bounded in places that would otherwise grow forever — the run-wide activity feed caps at 200 events, and artifact lists per task are capped rather than accumulating indefinitely across retries.
Restart reconciliation
Because live provider process handles are never persisted (they can't meaningfully survive a restart), AIgency reconciles durable state against reality on every startup — see Restart and crash recovery for what that reconciliation actually does.