AICTX
Repo-local execution state for coding agents

Operational continuity for AI coding agents.

AICTX helps Codex, Claude, GitHub Copilot and other coding agents continue work across sessions by preserving the last useful execution state: active work, next actions, decisions, failures, validation evidence and repo context.

Start in 2 minutes Open user manual View on GitHub
resume → work → finalize 
pip install aictx
aictx install
aictx init

# Then just keep using your coding agent.
# Agents handle the lifecycle themselves:
# resume context → work → finalize continuity

Start from what actually happened.

New agent sessions often rediscover the same files, decisions, failed commands and validation steps. AICTX keeps that operational state inside the repository so the next session can continue from evidence instead of guessing from README plus chat history.

Work State

Active task, hypothesis, relevant files, risks, next action and verification state.

Decisions and handoffs

Project decisions and what the previous session left for the next one.

Failures and validation

Known failed commands, resolved patterns, canonical checks and evidence.

Disconnected sessions are the problem.

Coding agents can reason through code, but every new session often starts operationally cold: it has to rediscover the repo, infer the task state, avoid old mistakes and guess which validation matters.

Without AICTX

A new agent session starts cold.
It scans README, docs and Makefile.
It rediscovers decisions.
It may repeat failed commands.
It guesses what should happen next.

With AICTX

The agent loads a resume capsule.
It sees active work and next action.
It sees known failures and validation path.
It finalizes factual evidence for the next session.

Inspectable, local, not hidden.

AICTX stores continuity under .aictx/. It is not cloud memory, not a vector database and not locked inside one chat. You can inspect it, clean it up, and optionally make a safe subset portable through Git.

Continuity View

Generate a local Markdown and Mermaid view of current operational continuity. 

aictx view --repo .

# writes:
.aictx/reports/continuity-view.md
.aictx/reports/continuity-map.mmd

Local MCP server

Expose continuity as local MCP tools/resources/prompts. Compatible clients can launch it over stdio; CLI fallback remains available.

aictx mcp-server --repo . --profile full

Simple start. Deep runtime when needed.

Quickstart

The shortest path from install to first continuity check.

Read Quickstart →

User Manual

Practical “I want to…” commands: portability, reports, MCP, cleanup, messages and diagnostics.

Open User Manual →

Technical Docs

Full technical reference for Work State, contracts, RepoMap, MCP, plugins, portability and internals.

Browse Technical Docs →

Works around the agents you already use.

Codex

CLI/runtime JSON contract, MCP support and Codex plugin artifacts.

Codex continuity →

Claude Code

Project instructions, hooks, MCP support and Claude Code plugin artifacts.

Claude Code continuity →

GitHub Copilot

Best-effort repo instructions, prompt files and VS Code MCP config where supported.

Copilot continuity →

What AICTX is not

AICTX is not an autonomous coding agent, a cloud memory service, a dashboard, a vector database or a replacement for human review.

AICTX does not guarantee correctness, productivity gains, token savings or that every agent will follow the lifecycle perfectly.