# dctx > dctx turns any folder into the smallest correct context for a task, offline, with byte-stable output that prompt caches can reuse. 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. **About this file** - Publisher: TEJL - tvornica elektroničkih jedinica i logike. TEJL.com: https://tejl.com/; TEJL.hr: https://tejl.hr/. - This is llms.txt: the facts and an index of every public HTML page. The other entry points: https://www.dctx.internet.technology/llms-small.txt, https://www.dctx.internet.technology/llms-full.txt. - Engine: dctx 1.3.1. Document captures are the unedited output of the dctx binary on a copy of the documents, recorded by https://github.com/Eris-Margeta/dctx/blob/main/tools/website/capture.py; the site check re-runs them and fails on any byte of drift. Read the pack at https://www.dctx.internet.technology/llms-full.txt. - Docs commit: 5f0b8b6e4560a9c6e2dc361fd7d2e6c33f9ba3b0 (2026-11-17T15:05:30+01:00), the last commit that changed one of the documents. - Command: `dctx pack . --include /docs/START.md --include /docs/WHY-DCTX.md --include /README.md --include /docs/MODALITIES.md` - Document capture budget: 18,466 of 20,000 estimated tokens (ceil(2 * UTF-8 bytes / 7)), 4 documents. **Facts** **What dctx is** dctx is an open-source (Apache-2.0) Rust context engine for AI-assisted coding: one local binary that packs a project into one structured block, or answers bounded, byte-stable symbol queries (find, read, neighbors, skeleton) as CLI output. What it is not: - No RAG: no embeddings, no vector search, and the engine never calls a model. - No network: pack, map and cache make no network calls; the release check counts socket calls under strace and fails on any. - No telemetry, not even opt-out. - No agent loop: dctx answers one command at a time; the agent or the human decides what to ask next. **Version and download** - Current version: 1.3.1, released 2026-11-09 (tag `v1.3.1`): https://github.com/Eris-Margeta/dctx/releases/tag/v1.3.1 - Each release on GitHub ships prebuilt archives for Linux x64/ARM64, macOS x64/ARM64 and Windows x64 with a SHA256SUMS file. - Verify a download: `sha256sum --check --ignore-missing SHA256SUMS` - Releases from 1.3.0 also ship keyless cosign signatures, CycloneDX SBOMs, build provenance and offline bundles; see [verification](https://github.com/Eris-Margeta/dctx/blob/main/docs/VERIFYING.md). **Modalities** - CLI (available): `dctx pack PATH` for one structured block (clipboard, file or stdout); `dctx map find|read|neighbors|skeleton|...` for bounded symbol answers. https://www.dctx.internet.technology/cli/ - Task context (available): `dctx pack --for TEXT --budget N`: find, neighbors and read of the names in TEXT, cut to an estimated-token budget. https://www.dctx.internet.technology/docs/map-mode/ - CI and prompt cache (available): Deterministic pack and map output; tree lines carry no timestamps by default, so the prefix stays stable across a touch. https://www.dctx.internet.technology/docs/modalities/#ci--prompt-cache-prefix-stability - Rust library (available from Git): The `dctx` facade crate as a tagged Git dependency; crates.io publication pending. https://www.dctx.internet.technology/docs/modalities/#rust-library-embed-the-facade - Desktop app (preview): A Tauri preview you build from source; a GPUI rebuild is planned. https://www.dctx.internet.technology/docs/modalities/#desktop-app-tauri-preview-today - Python, Node and Go wrappers (Node on npm; Python and Go from CI): Thin `dctx rpc` wrappers, built and tested in CI. Install Node with `npm install @tejl/dctx`, which includes pinned `@tejl/dctx-` optional dependencies; use CI artifacts for Python and Go. https://www.dctx.internet.technology/docs/modalities/#python-node-and-go-wrappers Two scopes, one binary: - System binary: the `dctx` on PATH belongs to you and your agents, and you upgrade it. Interactive agents call this one. - Project binary (Node from npm; Python and Go from CI): a binary installed by a project library lives inside that project (virtualenv, node_modules), pinned and managed by that package manager. Application code and CI call this one; a library never silently falls back to PATH. - Same engine, different owner. `dctx doctor` lists every binary in reach; verify each against SHA256SUMS and its cosign signature. **Before you start** > 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. **Benchmarks** Baseline: grep plus reading files. - Measured: 11 November 2026: 20 questions, a private 13-crate Rust workspace, claude-sonnet-5-5, dctx 1.3.0, three repeats per arm. Median total tokens [min, max]: grep plus reads 14,904,014 [14,604,149, 15,622,381]; dctx CLI (warm index) 14,157,974 [11,221,908, 15,613,375]. CLI median tokens were -5.01 % versus grep. On this corpus and model dctx did not save 25 % tokens; the pre-registered rule was not met. Official strict citation recall medians [min, max]: grep 10.10 % [10.10, 20.73]; CLI 14.46 % [8.36, 22.65]. Diagnostic file-level recall medians: 53.77 % and 71.70 %, respectively; diagnostic, not a replacement metric. The claim is accuracy and bounded context, not token savings. dctx on its own does not save tokens by default. Savings depend on a harness or agent system reusing byte-identical, prefix-stable context across long sessions; there is no measured, citable savings figure for such a system yet. One corpus, one model, no significance claim; corpus and raw answers private and cannot be published; dctx 1.3.0 is not current HEAD. Under ~200 files, use grep. https://www.dctx.internet.technology/benchmarks/#grep-read - Measured: Byte stability: the same query on unchanged code returns the same bytes; 33 of 33 text and JSON answers were byte-identical after unrelated edits (Linux only). https://www.dctx.internet.technology/docs/stability/ - Historical: The October and November in-house numbers (run 7: 140 of 140 task questions, cold index and warm latency) measure tool output only, as estimated stdout tokens and raw fact coverage without a model; they are not agent completion rates or session costs. https://www.dctx.internet.technology/benchmarks/ - Hypothesis: That a pack template changes model answer quality or cost is a hypothesis pending an A/B test; nothing on this site measures it. https://www.dctx.internet.technology/templates/ **Removed in 1.2.0** These existed before 1.2.0 and no longer work. A transcript that uses them describes an old version. - `dctx PATH` (the implicit snapshot command, for example `dctx .`): use `dctx pack PATH`. - the top-level snapshot flags `-d`/`--diff`, `-t`/`--tree` and `-r`/`--reset`: use `dctx pack PATH` with its filters. - the project rule files `.legacyignore` and `.dctxomitcontent`: use `.gitignore` and `.dctxignore`. - `dctx cache gc --legacy` and its export-selection flags: use `dctx cache gc`. **How to verify a claim** - Test suite: `cargo test --workspace --locked --exclude dctx-desktop --exclude dctx-desktop-api` https://github.com/Eris-Margeta/dctx/blob/main/docs/TESTING.md - CI: Every push and pull request runs the suite on Linux, macOS (ARM64 and x64) and Windows, on stable Rust and the minimum supported version 1.91. https://github.com/Eris-Margeta/dctx/actions - No network calls: `scripts/release-check.sh --quick target/release/dctx-cli` https://github.com/Eris-Margeta/dctx/blob/main/scripts/release-check.sh - Byte stability: `python3 docs/research/stability-20261105/verify.py` https://www.dctx.internet.technology/docs/stability/ - Historical benchmark: `docs/research/bench-3way-20261030/run-3way.sh target/release/dctx-cli` https://github.com/Eris-Margeta/dctx/tree/main/docs/research/bench-3way-20261030 - Every output on this site: Recorded from the real binary by tools/website/capture.py; tools/website/check.py re-records and fails on drift. https://github.com/Eris-Margeta/dctx/tree/main/tools/website ## Overview - [dctx](https://www.dctx.internet.technology/): dctx is the open-source context engine for AI-assisted development: deterministic, bounded code context for agents and chat, offline, with no telemetry. Apache-2.0. - [Search](https://www.dctx.internet.technology/search/): Search the dctx website. - [Playground offline](https://www.dctx.internet.technology/playground/offline/): The playground service is not reachable right now. - [Page not found](https://www.dctx.internet.technology/404.html): This page does not exist on the dctx website. ## Docs - [Documentation](https://www.dctx.internet.technology/docs/): Specification, guides, benchmark reports and project policies for dctx, rendered from the repository. - [Choose your path](https://www.dctx.internet.technology/start/): dctx is an advanced tool with several ways to use it. Pick the path that matches your work: one giant folder, many small projects, a library in your own tool, or a team rollout. - [One giant folder](https://www.dctx.internet.technology/start/giant-folder/): You work inside one very large tree, for example a 200 GB monorepo, data or document folder. Setup, first command, what to expect and the pitfall to avoid. - [Many smaller projects](https://www.dctx.internet.technology/start/many-projects/): You move between many small and medium repositories during the day. Setup, first command, what to expect and the pitfall to avoid. - [Agent builder embedding a library](https://www.dctx.internet.technology/start/library/): You build an agent, editor or tool and want dctx inside it. Setup, first command, what to expect and the pitfall to avoid. - [Team or organisation admin](https://www.dctx.internet.technology/start/team/): You roll dctx out to a team or a fleet of machines. Setup, first command, what to expect and the pitfall to avoid. - [For AI evaluators](https://www.dctx.internet.technology/for-ai-evaluators/): What dctx is and is not, its version, modalities, benchmark status, removed commands and how to verify every claim. - [Why dctx](https://www.dctx.internet.technology/why/): Why dctx exists, its philosophy, and why byte-identical output keeps the prompt cache hitting. - [README](https://www.dctx.internet.technology/docs/readme/): Installation, quick start, map mode, language tiers and the CLI reference. - [What dctx is](https://www.dctx.internet.technology/docs/start/): The claim and its limits, the advanced-user notice, choose your path, the safe path in ten minutes, responsibilities and the two scopes. - [Choosing how to use dctx](https://www.dctx.internet.technology/docs/modalities/): Clipboard, grep plus reads, long sessions, huge trees, CLI usage and CI. - [Map mode guide](https://www.dctx.internet.technology/docs/map-mode/): Every map verb with examples, budgets, ids and precision labels. - [Agent snippet](https://www.dctx.internet.technology/docs/agents/): The AGENTS.md section that tells coding agents to ask dctx first. - [Plugins guide](https://www.dctx.internet.technology/docs/plugins/): The plugin boundary, capabilities, consent and current limits. - [Specification](https://www.dctx.internet.technology/docs/spec/): The core belief, the five constraints, the ten RAG defect classes, policy and roadmap. - [Privacy guarantees](https://www.dctx.internet.technology/docs/privacy/): Ignore semantics and the full sensitive-file deny list. - [Language coverage (ADR-018)](https://www.dctx.internet.technology/docs/language-coverage/): The three tiers and how a language enters one. - [Template contract (DTS v2)](https://www.dctx.internet.technology/docs/templates-contract/): DTS source v2 and the compiled plan IR v1. - [Templating engine (ADR-003)](https://www.dctx.internet.technology/docs/templating/): Markers, ahead-of-time compilation, the two rendering passes and the data variables. - [CLI exit codes](https://www.dctx.internet.technology/docs/exit-codes/): The exit-code contract for map, pack and languages. - [How dctx works](https://www.dctx.internet.technology/how-it-works/): Five short animations: two scopes of one binary, calls times context, prefix stability, the giant folder and the safe path for new users. ## CLI - [CLI reference](https://www.dctx.internet.technology/cli/): Every dctx command, flag, environment variable, and exit code, captured from the dctx binary. - [Languages](https://www.dctx.internet.technology/languages/): The 50 language families dctx indexes, by tier: full, outline and docs. ## Examples - [Examples](https://www.dctx.internet.technology/examples/): Every dctx command on one sample project, with its exact output, exit code, bytes and estimated tokens. - [Templates](https://www.dctx.internet.technology/templates/): The two built-in dctx templates, their source, their output on the same project and what changes between them. - [Playground](https://www.dctx.internet.technology/playground/): Run the real dctx binary on a sample project or on your own text files, in the browser. ## Evidence - [Measurement evidence](https://www.dctx.internet.technology/docs/benchmark/): Grep plus file reads first; whole-session scope and secondary historical protocols. - [Byte-stability report](https://www.dctx.internet.technology/docs/stability/): Protocol, raw answers and limits of the 33/33 measurement. - [Earlier two-way study](https://www.dctx.internet.technology/docs/benchmark-oct/): October 2026, before call edges: the benchmark that set the roadmap. - [Benchmarks](https://www.dctx.internet.technology/benchmarks/): Grep plus file reads, whole-session accounting, byte stability and secondary historical measurements. ## Project - [Crate map](https://www.dctx.internet.technology/docs/crate-map/): How the Rust workspace is organised. - [Releasing](https://www.dctx.internet.technology/docs/releasing/): How a release is cut and checked. - [Contributing](https://www.dctx.internet.technology/docs/contributing/): How to propose changes, with a DCO sign-off. - [Security policy](https://www.dctx.internet.technology/security/): How to report a vulnerability privately, and what happens next. - [Trademark policy](https://www.dctx.internet.technology/trademark/): What the dctx name and logo may be used for, and what forks may call themselves. - [Maintenance](https://www.dctx.internet.technology/maintenance/): dctx is free under Apache-2.0. Maintenance agreements fund security response, long-term support and priority work. ## Optional - [Changelog](https://www.dctx.internet.technology/changelog/): Every dctx release, from dircontxt 1.0.0 in C to dctx in Rust, with known issues. - [News](https://www.dctx.internet.technology/news/): Releases, measurements and product decisions from the dctx project. - [dctx 1.1: three more languages, a prefix-stable pack, and a measured lead.](https://www.dctx.internet.technology/news/dctx-1-1/): Perl, Fortran and Verilog join map mode; dctx pack drops timestamps so prompt caches hit; the three-way benchmark and the byte-stability measurement are public. - [dctx Desktop is now free. Forever.](https://www.dctx.internet.technology/news/desktop-free-forever/): For individuals, teams and companies. No trial, no seat count, no expiry. - [Our specification, and a benchmark that does not flatter us.](https://www.dctx.internet.technology/news/specification-and-benchmark/): The dctx Context Management Specification, and an isolated comparison with Trail-Code: wins, losses and what comes next.