Register Content

What to register

Any documentation that agents would benefit from but that isn't derivable from source code alone is a good candidate. Common examples:

• Coding standards and style guides — Org-wide conventions for naming, error handling, security, and patterns. Register at the org level so every agent working in any codebase receives them.
• Architecture Decision Records (ADRs) — Architectural rationale that agents can reference before proposing changes. Keeps past decisions in context during implementation.
• Legacy code guidance — Explain relationships between old and new APIs, or direct agents to prefer a v2 path while allowing maintenance work on v1.
• Migration guides — Step-by-step guidance during major version upgrades or breaking changes. Register for the duration of the migration, then remove when complete.
• Cross-codebase architecture docs — System-level context for services that span multiple repos. Register at the org level so agents working on any service understand how the pieces fit together.
• Shared glossaries and domain terminology — The language of your domain, defined once. Reduces the gap between how your team talks about the product and how agents interpret it.
• Onboarding guides — Team- or subsystem-specific orientation guides so new developers and their agents start with the same baseline.
• SDLC documents — Requirements specs, design documents, and test plans registered alongside the code they describe. Gives agents traceability between what was intended and what was built.

Step 1: Prepare your content

Content must be in Markdown. If your document is in another format (Google Docs, Confluence, Word), export or paste it as Markdown before registering.

Write a clear, descriptive title and make sure the content is self-contained — agents will read it without additional context about where it came from.

Step 2: Choose scope

Registered content can be scoped to a specific codebase or to your entire organization:

• Codebase-scoped — Available only when an agent is working in that codebase. Use for content specific to one repo: ADRs, migration guides, API contracts, onboarding guides for that service.
• Org-scoped — Available across all codebases in your organization. Use for content that applies everywhere: coding standards, shared glossaries, cross-codebase architecture docs. Requires org admin access to register.

Registered content inherits your organization's RBAC-based access controls — agents only receive content they have permission to access.

Step 3: Choose update behavior

Each registered document is either static or auto-updating:

• Static — The content stays exactly as registered. Use for authoritative documents that should remain unchanged regardless of code changes: coding standards, ADRs, onboarding guides, migration guides.
• Auto-update — Driver revises the content whenever the associated codebase changes in a way that affects it. Use for documents that describe the current state of the code and should stay accurate over time: API references, architecture summaries, data flow documentation.

For auto-updating content, provide a goal that describes what the document should cover. Driver uses this goal to determine when and how to update it. See Auto-Update Content for guidance on writing the seed content and goal.

Step 4: Register with your agent

Ask your coding agent or MCP-connected AI agent to register the document. In your prompt, specify:

1. Whether it applies to your entire organization or a specific codebase (and optional branch)
2. Whether it should auto-update or remain static
3. Optionally, a goal describing what the content should cover

Example prompts

• "Register the content in coding-standards.md with Driver as a static org-wide document."
• "Add the content in data_flow.md to Driver so it automatically stays updated whenever the data model or processing pipeline logic is modified. Attach this to the backend codebase."
• "Register this ADR as a static document scoped to the payments codebase."

The agent calls the register_content MCP tool. Once registered, the content is returned in future MCP context calls for agents working in the relevant codebase or organization.

Managing registered content

Three additional tools let you inspect and manage what's registered:

• get_registered_content_list — Lists all registered documents accessible to you, with optional filters by codebase, tags, or update behavior. Use this to discover what's available before fetching.
• fetch_registered_content — Retrieves the full content of a registered document by name.
• remove_registered_content — Permanently deletes a registered document. The agent will ask for confirmation before proceeding.

Example prompts

• "What registered content is available for the backend codebase?"
• "Show me the contents of the coding standards document."
• "Remove the v1 migration guide from Driver."

You can also view registered content in the Driver web app — open Org Docs for organization-scoped entries, or Sources > Autodocs for codebase-scoped entries.