Getting Started

Prerequisites¶
ctx does not require git, but using version control with your .context/
directory is strongly recommended.
AI sessions occasionally modify or overwrite context files inadvertently.
With git, the AI can check history and restore lost content:
Without it, the data is gone.
Also, several ctx features (journal changelog, blog generation) also use
git history directly.
Installation¶
A full ctx installation has two parts:
- The
ctxbinary — the CLI tool itself - The Claude Code plugin — hooks and skills that make Claude Code context-aware
You need both. The binary alone gives you the CLI but Claude Code
won't autoload context, nudge you to persist decisions, or provide
the /ctx-* skills.
Pick one of the options below — each is a complete path from zero to a working setup.
Option 1: Build from Source (Recommended)¶
Requires Go 1.25+ and Claude Code.
Install the Claude Code plugin from your local clone:
- Launch
claude - Type
/pluginand press Enter - Select Marketplaces → Add Marketplace
- Enter the path to the root of your clone,
e.g.
~/WORKSPACE/ctx(this is where.claude-plugin/marketplace.jsonlives — it points Claude Code to the actual plugin ininternal/assets/claude) - Back in
/plugin, select Install and choosectx
This points Claude Code at the plugin source on disk. Changes you make to hooks or skills take effect immediately — no reinstall needed.
Verify:
Building from source gives you the latest features and bug fixes.
Since ctx is predominantly a developer tool, this is the
recommended approach: you get the freshest code, can inspect what
you are installing, and the plugin stays in sync with the binary.
Option 2: Binary Download + Marketplace¶
Pre-built binaries are available from the releases page.
Download ctx-0.6.0-windows-amd64.exe from the releases page and add it to your PATH.
Install the Claude Code plugin from the marketplace:
- Launch
claude - Type
/pluginand press Enter - Select Marketplaces → Add Marketplace
- Enter
ActiveMemory/ctx - Back in
/plugin, select Install and choosectx
Verify:
Verifying Checksums¶
Each binary has a corresponding .sha256 checksum file. To verify your download:
# Download the checksum file
curl -LO https://github.com/ActiveMemory/ctx/releases/download/v0.6.0/ctx-0.6.0-linux-amd64.sha256
# Verify the binary
sha256sum -c ctx-0.6.0-linux-amd64.sha256
On macOS, use shasum -a 256 -c instead of sha256sum -c.
What the Plugin Provides
After installation (either option) you get:
- Context autoloading —
ctx agentruns on every tool use (with cooldown) - Persistence nudges — reminders to capture learnings and decisions
- Post-commit hooks — nudge context capture after
git commit - Context size monitoring — alerts as sessions grow large
- 25+ skills —
/ctx-status,/ctx-add-task,/ctx-recall, and more
See Integrations for the full hook and skill reference.
Quick Start¶
1. Initialize Context¶
This creates a .context/ directory with template files and a
.scratchpad.key for the encrypted scratchpad.
For Claude Code, install the ctx plugin
for automatic hooks and skills.
2. Check Status¶
Shows context summary: files present, token estimate, and recent activity.
3. Start Using with AI¶
With Claude Code (and the ctx plugin installed), context loads automatically via hooks.
With VS Code Copilot Chat, install the
ctx extension and use
@ctx /status, @ctx /agent, and other slash commands directly in chat.
Run ctx hook copilot --write to generate .github/copilot-instructions.md
for automatic context loading.
For other tools, paste the output of:
4. Verify It Works¶
Ask your AI: "Do you remember?"
It should cite specific context: current tasks, recent decisions, or previous session topics.
Next Up:
- Your First Session → — a step-by-step walkthrough from
ctx initto verified recall - Common Workflows → — day-to-day commands for tracking context, checking health, and browsing history