AICTX
Stop onboarding your coding agents from scratch every session.
AICTX is a lightweight repo-local continuity runtime for Codex, Claude Code, GitHub Copilot, and other coding agents. It gives each new session the useful facts from the repository — what happened, what failed, what changed, what was decided, and what should happen next — without turning AICTX into an agent framework, task manager, vector database, or cloud memory product.
pip install aictx
aictx install
aictx init
After that, keep working normally. Compatible agents run the lifecycle themselves:
resume -> work -> finalize -> next session resumes
Quickstart · What AICTX writes · Continuity View · Website
Why AICTX exists
Coding agents are strong, but new sessions still start cold:
- they rescan the same files and docs;
- they rediscover decisions already made;
- they repeat failed commands and stale assumptions;
- useful context gets trapped in one vendor's chat history.
AICTX turns that fragile chat-local memory into repo-local operational continuity. The next agent starts with a compact brief instead of guessing from scratch.
The product loop
The user path is intentionally small:
aictx install
aictx init
then let the coding agent work
The agent path is equally small:
aictx resume --repo . --task "fix the parser bug" --json
# agent edits, tests, debugs, and reviews normally
aictx finalize --repo . --status success --summary "Fixed parser recovery and ran focused parser tests" --json
A later session resumes from local repository state instead of hidden chat history.
You: fix the parser bug
Agent: resumes repo-local continuity
Agent: works normally
Agent: finalizes factual evidence for the next session
What the next agent gets
AICTX records operational facts that make the next session useful faster:
| Continuity | Why it helps |
|---|---|
| Active work | Current task, files, risks, and next action. |
| Handoffs | What the previous session actually left behind. |
| Decisions | Project facts the next agent should not re-litigate. |
| Failures | Known broken commands, errors, and resolved patterns. |
| Validation evidence | Commands, tests, files opened/edited, and final summary. |
| Quality signals | Fresh, stale, missing, obsolete, or unverified context warnings. |
Everything is local and inspectable. The default runtime writes under .aictx/ and generated agent-instruction files; no account, daemon, dashboard, or cloud sync service is required.
See it working
Generate an inspectable continuity report at any time:
aictx view --repo .
Default output:
.aictx/reports/continuity-view.md
.aictx/reports/continuity-map.mmd
Check health and repair guidance:
aictx doctor --repo . --json
AICTX is not hidden memory. It is reviewable repo-local continuity with explicit quality signals.
Why it feels different
- Local-first: continuity belongs to the repository, not a private chat thread.
- Agent-neutral: Codex can leave context that Claude Code, Copilot, or another compatible agent can resume.
- Tiny default path: install, init, then work; manual resume/finalize commands are mostly for inspection and unsupported runners.
- Evidence-oriented: AICTX records what was observed, validated, skipped, or left unfinished.
- Honest by design: stale context is marked stale; missing validation stays visible; AICTX never claims automatic correctness.
Supported agents
AICTX is runner-aware, not runner-locked.
- Codex:
AGENTS.md, optional global Codex setup, CLI/MCP lifecycle guidance. - Claude Code:
CLAUDE.md, Claude settings/hooks, CLI/MCP lifecycle guidance. - GitHub Copilot: repository instructions and optional prompt files where supported.
- Generic agents: any runner that can read instructions and call CLI or MCP tools.
Compatible agents prefer AICTX MCP tools when available and fall back to the CLI:
aictx_resume / aictx_finalize
# or
aictx resume --repo . --task "<goal>" --json
aictx finalize --repo . --status success|failure --summary "<what happened>" --json
What AICTX is not
AICTX is not an autonomous coding agent, RAG system, vector database, task manager, dashboard, cloud memory service, replacement for tests/review, or guarantee of correctness, productivity gains, or token savings.
It is a lightweight continuity runtime that helps cooperating coding agents start from useful repository state.
Documentation
Start here:
Core concepts:
- Technical overview
- Work State
- Handoffs and Decisions
- Failure Memory
- Execution Summary
- Execution Contracts
Advanced:
Legacy/internal compatibility surfaces are intentionally kept out of the first-run path; see Usage for the split between supported advanced commands and compatibility-only commands.
For the full command reference, see Usage.
Project links
- Website: https://aictx.org
- PyPI: https://pypi.org/project/aictx/
- CLI:
aictx - Official identity: docs/OFFICIAL_PROJECT.md
1 maintainer
Metadata
1 maintainer
Release files for aictx 7.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| aictx-7.0.1.tar.gz | 409.8 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aictx-7.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 695.6 kB
Release files / aictx-7.0.1.tar.gz
| Download URL | aictx-7.0.1.tar.gz |
|---|---|
| Size | 409.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
703c834e9467793f17401a6fed8a17421c4e92a1541eac575d72b5af294dbb74
|
|
BLAKE2b-256 checksum How to use checksums |
b67091bfd67dc21b584d056b0ecec711b4e071f441a3b790c058d0d53ae9e9f0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 17, 2026.
Transparency logRelease files / aictx-7.0.1-py3-none-any.whl
| Download URL | aictx-7.0.1-py3-none-any.whl |
|---|---|
| Size | 285.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b5e3130d25248c7deedf64e964361c005c7d187f1602d9027074bcf4db2f2238
|
|
BLAKE2b-256 checksum How to use checksums |
a0f8779cce917a455a91a975c9f653c0855dedeccdf1b12f51bf0babae7f82dd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 17, 2026.
Transparency logSecurity for aictx 7.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for aictx-7.0.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 17, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
