dctx1.3.1
Choose your path

Many smaller projects

You move between many small and medium repositories during the day.

you get
Install once, then run find and read from each project directory.
modality
System binary, called directly from a shell or an agent's shell tool.
version
dctx 1.3.1

Setup

  1. Install the system binary once and put it on PATH.
  2. Run the dctx CLI directly from your agent's shell tool.
  3. Start in the project directory, or use --place to name the project root.
  4. Nothing else per project: dctx reads .gitignore and .dctxignore where they already are.

First command

shell
$ dctx map find NAME

What to expect

find returns stable ids; read returns the verified source bytes of one id. The captured run below shows find on the sample project.

A real run on the kiosk sample project, recorded from the release binary by capture.py:

~/kiosk · dctx 1.3.1
$ dctx map find greet# kiosk finds:src/util.rs#greet	fn	L2-4s:web/app.ts#renderGreeting	fn	L10-12# exit 0 · 79 bytes · ~23 est. tokens

The pitfall

Stale caches of projects you deleted or no longer use. Auto-clean runs once a day and drops unpinned roots after 30 idle days; to clean by hand, run dctx cache status, then dctx cache gc --dry-run or dctx cache purge --root PATH --dry-run.

Read next

Choosing how to use dctx · Who is responsible for what

Other paths:

dctx is an advanced tool with several ways to use it. Used well, it cuts irrelevant text from selected tool answers. It does not save tokens by default; savings depend on a system reusing byte-identical, prefix-stable context. Extra calls can add tokens. If you are new, follow the safe path: one project, the system binary, direct CLI commands. Measure before you change anything.

Status: Receipts are planned. The safe path uses CLI commands from a shell or an agent's shell tool.