Skip to content
Documentation
Browse documentation

Getting started

LangDrift setup requires Node.js 24 or later and an existing project directory. From inside a Git repository, the command can discover the nearest repository root, so no --root flag is needed.

npx @langdrift/core setup \
  --project-id proj_example \
  --account-id acc_example \
  --name 'Example Product'

Outside a Git repository, pass an explicit existing directory with --root /path/to/product. Project and account IDs are routing metadata; setup does not create an account or authenticate either ID.

Generated files

A new setup creates exactly these protocol files:

.drifts/project.json
.drifts/vision/schema.json
.drifts/loop/schema.json
.drifts/evidence/schema.json

Artifact directories are created later as documents are added. Setup does not generate placeholder artifacts, integration code, or agent configuration.

Safe, local setup

Preview the complete file plan before writing:

npx @langdrift/core setup \
  --project-id proj_example \
  --account-id acc_example \
  --name 'Example Product' \
  --dry-run

Setup classifies every managed destination as create, preserve, or conflict. It creates missing files, preserves matching files byte-for-byte, and never overwrites conflicting content. A preflight conflict prevents all writes. The command makes no network requests and does not connect GitHub, Linear, Obsidian, MCP, or a LangDrift backend.

Continue

Edit this page on GitHub