View on GitHub

AICTX

Repo-local continuity runtime for coding agents

Work State

Work State is AICTX’s repo-local artifact for suspended active-task continuity.

It answers:

Where was the active work left?

What it preserves

A Work State thread can preserve:


What it is not

Work State is not a task manager, kanban board, issue tracker, planner, or hidden semantic memory.

It is deterministic operational continuity.


Artifacts

.aictx/tasks/active.json
.aictx/tasks/threads/<task-id>.json
.aictx/tasks/threads/<task-id>.events.jsonl

Only one active pointer exists per repo. Old threads remain stored.


Public CLI

aictx task start "Fix login token refresh" --json
aictx task status --json
aictx task update --json-patch '{"next_action":"run targeted auth tests"}' --json
aictx task list --json
aictx task show fix-login-token-refresh --json
aictx task resume fix-login-token-refresh --json
aictx task close --status resolved --json

These commands are available for inspection and advanced control. In normal supported-agent workflows, the agent may update Work State through runtime integration.


Runtime integration

prepare_execution() loads active Work State when safe and exposes compact active_work_state.

finalize_execution() can update Work State from factual evidence or explicit payloads.

Automatic updates stay conservative.


Branch-safe loading

AICTX stores:

Rules:

Situation Behavior
same branch load
same branch, changed HEAD load with warning
different branch, saved commit reachable from current HEAD load with warning
different branch, saved commit not reachable skip
saved state dirty and branch changed skip
old Work State/no git load conservatively

Skipped Work State is not deleted.


Relationship to other layers

Work State = current suspended task state.
Handoff = latest operational summary.
Strategy Memory = what worked.
Failure Memory = what failed.
RepoMap = where to look.