Team or organisation admin
You roll dctx out to a team or a fleet of machines.
- you get
- One verified, pinned version on every machine, with the same safety rules everywhere.
- modality
- System binary distributed through your own package channel, one pinned version everywhere.
- version
- dctx 1.3.1
Setup
- Download the release archives from GitHub Releases and verify them against SHA256SUMS and their cosign signatures; each release also ships an SBOM.
- Ship one pinned version through your own package manager, image or configuration tool.
- Ship shared ignore rules (
.dctxignoreand a global ignore); the built-in deny for secrets,.gitand symlinks always applies. - Tighten the cache cap per machine if you need to:
dctx cache config --max-bytes Ncan only lower it.
First command
$ dctx --versionWhat to expect
One line with the version on every machine; dctx --version --verbose adds the feature list and precision and cache limits. Every machine should print the same line.
A real run on the kiosk sample project, recorded from the release binary by capture.py:
$ dctx --versiondctx 1.3.1 (<git sha>)
The pitfall
Mixing project and system versions without checking. Run dctx doctor to list every binary in reach, and check dctx --version on PATH and the version each project pins, as part of onboarding.
Read next
Privacy guarantees · Security policy · 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.