Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.driftless.icu/llms.txt

Use this file to discover all available pages before exploring further.

Driftless keeps architectural context alive across sessions, repos, and contributors. It is not a PR reviewer, CI gate, or cache. It is the durable context layer your team updates as the codebase changes, then loads before the next edit.

Quickstart

Install the CLI, link a repo, and read your first topic.

The Driftless loop

Scan code, observe changes, maintain topics, and deliver context.

CLI reference

Commands for setup, sync, context, graph, branches, and health checks.

Agent setup

Install AGENTS.md instructions so coding agents use context before editing.

​
The loop

1

Sync

Pull team context changes before starting work.
driftless sync
2

Load

Ask Cloud what applies to the files you are about to touch.
driftless context load --files "src/auth/guard.ts,src/users/service.ts"
3

Persist

Append durable decisions, gotchas, and anchors after you learn something.
driftless context update auth --gotcha "JWT decode happens in guard, not middleware"

​
Boundaries

Driftless informs. It never modifies code, approves PRs, blocks merges, runs tests, or exposes an MCP server in v1.

Topics

The unit of codebase memory.

Coverage

Which files have context and which files are gaps.

API

REST surface used by the CLI and dashboard.