Frequently asked questions
The short version of how everything fits together — the guides below go deeper on any part of it.
Every part of DF Code, explained
Grouped by topic, each starting with the basics before working up to the more advanced pieces.
Getting Started
What is DF Code?
The short version: one place for your ideas, repos, and agents to live together.
Picking your context
First launch asks who you are, not for a password — here's why, and what the setup walks you through.
Your first week with DF Code
A rough on-ramp: what to try on day one, and what to reach for once the basics feel automatic.
Workspaces & Threads
Workspaces & Threads
Your project's home base — repos, conversations, and history, all attached to one place.
Diffs, history, and editing files directly
Every change a conversation makes stays visible — as an inline diff, a running history, or a file you can open yourself.
Organizing bigger projects with phases
A big initiative doesn't have to live in one workspace — nest smaller ones underneath it instead.
One-off conversations
Sometimes you just want to ask something — a floating panel skips creating a workspace entirely.
Domains
Domains
Write down what your codebase needs an agent to know, once, and stop repeating yourself.
Keeping Domains and repositories in sync
A Domain's notes only help if its workspace can actually see the code they describe.
Writing a Domain that actually gets used
The difference between a Domain that helps and one nobody reads comes down to a few habits.
Agents & Conductor
Agents & the Conductor
Two different kinds of automation — a one-off nudge, and something that keeps going on its own.
Tuning how often an agent checks in
How often an agent looks, and how long it's allowed to run, are both yours to adjust.
Reading the Audit Trail
When an agent didn't do what you expected, this is the first place to look — not the last.
Strategies
Reusable Strategies
Save a multi-agent pattern that worked, and bring it to life again with one click.
Root roles vs. their own workspace
The one real judgment call when designing a role: does it need a space of its own?
Referencing sibling roles in a prompt
One role's instructions can point at another by name — resolved automatically the moment you instantiate.
Forking the built-in Watcher/Addresser and Engineer/Reviewer strategies
Two proven patterns ship ready to copy — start there before designing one from scratch.
Memories
Connectors
Connectors
DF Code speaks Claude natively — and leaves the door open for other coding agents too.
Choosing a connector per workspace
Most people never touch this — it's there for the rare project that wants something different.
What "scaffolded" means for the newer connectors
A couple of connectors exist as an early sketch, not a tested guarantee — worth knowing before relying on one.
MCP Server
Admin & Identity
Admin & User Profiles
For installs shared by more than one person — who's who, and who can manage what.
Sharing one install with your team
One DF Code install, running on one machine, can genuinely serve more than one person.
Moving a workspace between contexts
Handing off one project to someone else's space, without dragging your whole setup along with it.
Backing up and restoring your setup
Your entire setup — every workspace, every conversation, every setting — can travel with you to a new machine.
Tutorials
Create your first workspace
The smallest complete loop — a repo, a workspace, and one real conversation.
Build a Watcher / Addresser strategy
Wire up two agents that hand work to each other — from a blank page to a running pipeline.
Set up an Engineer / Reviewer pipeline
A second set of eyes on everything you build — wired up once, running from then on.
Recover from a stuck agent
A quick checklist for the moment an agent seems to have gone quiet and you're not sure why.
Still stuck?
Contact us