Welcome. This guide is the friendly, hand-written companion to DreamGraph. It is intended for humans who want to use the system, not for the system documenting itself.
This same guide is also published on the website: dreamgraph.nofs.ai — same content, nicer reading experience.
If you are looking for the auto-generated reference (every tool, every parameter, every schema), that lives in docs/. This guide is the part you read first.
- First-time users who installed DreamGraph and are now staring at a CLI prompt
- Developers who want to understand the mental model before writing code against it
- Architects who want to know what DreamGraph actually does with your repository
- People who tried it once, got confused, and bounced — we want you back
You do not need to read the guide top-to-bottom. Jump to whichever page matches your current question.
| # | Page | What you'll learn |
|---|---|---|
| 1 | What is DreamGraph? | The mental model. Graph + dreams + cognitive engine, in plain language. |
| 2 | Installation | One-command install, prerequisites, common install gotchas. |
| 3 | Your first instance | dg init, attaching a repo, starting the daemon. |
| 4 | LLM setup | Connecting Ollama, LM Studio, OpenAI, or Anthropic. Choosing a model. |
| 5 | Bootstrapping the graph | What dg scan actually does. Where your data lives. |
| 6 | The VS Code extension | A tour of the sidebar: Architect chat, dashboard, Explorer, changed files. |
| 7 | The Explorer | Browsing the graph, inspector, tensions, candidates, search. |
| 8 | Dreams and cycles | What dreaming means, when to do it, what to expect. |
| 9 | Curating the graph | Reviewing tensions, promoting/rejecting candidates, recording ADRs. |
| 10 | A typical daily workflow | A sustainable loop. What to do in the morning, what to leave running. |
| Page | When to read it |
|---|---|
| Multi-repo and monorepo setups | You have more than one repository, or one big monorepo. |
| Troubleshooting & FAQ | Something is wrong and you want a quick checklist. |
| Glossary | "Wait, what's a latent candidate again?" |
You install DreamGraph once. Then it runs as a background daemon you barely think about. You interact with it through three surfaces:
- The
dgCLI — for setup, daemon control, and one-off maintenance. - The VS Code extension — for chat (Architect), the dashboard, and the Explorer.
- MCP tools — automatically available to any MCP-aware AI agent (Claude Desktop, Copilot, etc.) once the daemon is running.
Most days you will never type dg after starting the daemon. You'll talk to your AI agent and browse the Explorer.
- No surprise jargon. Every cognitive-engine term is defined the first time it appears, and again in the glossary.
- Concrete commands. Every page that tells you to do something shows you the exact command.
- Honest about rough edges. If something is finicky or experimental, this guide says so.
- No marketing. This guide does not try to sell you DreamGraph. You already installed it.
- Check the Troubleshooting & FAQ page first.
- Run
dg status <instance>— most problems show up there. - Check the daemon logs at
~/.dreamgraph/<instance-uuid>/logs/. - File an issue at https://github.com/mmethodz/dreamgraph/issues with the output of
dg statusand the relevant log snippet.
Ready? Start with What is DreamGraph?