@neuvybe/ctx

ctx gives coding agents durable, project-specific context that survives compaction. New scaffolds use layout v2: a small core of evidence-tracked project facts, a hierarchical index, and an ignored local continuation file. The glossary add-on is selected by default; other add-ons stay opt-in.

Team mode is the default. Durable context is available to review and commit, while .ctx/local/CONTINUE.md stays ignored. --mode local keeps the entire scaffold private through the repository's common .git/info/exclude. ctx never stages or commits files.

Install

npm install -g @neuvybe/ctx
ctx --version

The postinstall step fetches the matching binary from the package version's GitHub release. If that download is unavailable, install with:

go install github.com/neuvybe/ctx/cmd/ctx@latest

Initialize

# Team-mode v2 core plus glossary
ctx init /path/to/repo

# Core only
ctx init /path/to/repo --without glossary

# Whole-folder private
ctx init /path/to/repo --mode local

# Add focused context at creation
ctx init /path/to/repo --with operating,contracts

# Inspect or extend an existing v2 scaffold
ctx add --list
ctx add /path/to/repo review

glossary remains an add-on so projects can omit it with --without glossary, but new scaffolds select it by default. --with and --without are repeatable and comma-friendly. The other available add-ons are operating, contracts, extending, and review.

For new initialization, --folder accepts one top-level name containing only letters, digits, ., _, or -. Repeat a custom --folder with later commands. On a fresh clone with committed team context, rerun ctx init to hydrate only the ignored continuation file.

Health and readiness

• ctx doctor checks structure, layout compatibility, managed markers, and Git boundaries.
• ctx status summarizes draft / verified / not-applicable metadata, flags listed sources changed since verification, and gives non-failing size guidance; it cannot verify truth or source sufficiency.
• ctx update refreshes compatible named managed blocks without touching local continuation state.

Existing schema-v1 and config-less legacy scaffolds stay on their frozen v1 layout/update path; ctx does not silently relocate their root CONTINUE.md, change unnamed markers, or expose private context.

See the project README, layout v2 guide, fill workflow, team-mode migration, and layout-v2 migration.