Skip to main content
Brein is one workspace where a team and its agents share durable state: the Knowledge you keep, the Operations you run, and the Work in flight. The installed CLI and agent commands retain the driftless name for compatibility. This quickstart starts where builders feel it first: your agent reads the relevant context before it touches an area and writes back what it learns. You don’t learn a system. Your agent does. Here’s the whole setup.
1

Install and log in

For CI or non-interactive setup, pass a key instead: driftless login --key drift_your_api_key_here (create one at driftless.icu → Settings → API Keys).
2

Teach your agent

This writes AGENTS.md and CLAUDE.md into your repo. From now on, any coding agent that opens the repo knows the loop: pull team context before editing, persist what it learns after.
3

Go code

Work as you normally would. Your agent pulls context before it touches an area, and saves new gotchas and decisions as it learns them. Come back to your dashboard and watch your first memory show up.
That’s it. Pull before, persist after. That’s Brein.

​
The whole loop, in one prompt

Prefer not to install the skill, or want to drop the behavior into any agent directly? This is all it needs:

​
Going deeper

You don’t need any of this to start. Reach for it once you have a few topics and want more out of them:
  • The Driftless loop: the whole model, Knowledge, Operations, and Work, and the loop between them.
  • Topics: the content, anchors, and fields each one carries.
  • Drift & freshness: how a topic flags itself when its code moves underneath it.
  • The CLI: anchoring topics to files, file-matched retrieval, relations.
  • Agent setup in depth: wiring Driftless into specific coding agents.