Rudder Docs

Rudder Docs

Provide authoritative, current guidance about Rudder. This is Rudder's documentation and self-knowledge entry point, not a workflow that must run merely because the agent is hosted by Rudder.

If this body is already present in the prompt but the current request does not need Rudder guidance, do not perform a docs lookup. Continue the user's actual task using the current tools and context.

Purpose And Non-Goals

Classify the Rudder question, consult the smallest authoritative source set, and answer with clear provenance. Use current evidence instead of memory for commands, interfaces, versioned behavior, and design proposals.

This router does not make an ordinary hosted task into a Rudder workflow. It does not provide a command catalog, replace runtime-owned execution rails, or authorize an operation merely because it documents that operation.

Classify The Request

Choose one primary class before retrieving evidence:

• Current capability or installed command: what this run exposes, which CLI syntax is installed, or whether an exact operation is supported.
• Public product guidance: how a user should use or configure Rudder.
• Product contract: the intended semantics or invariant for a Rudder feature.
• Contributor or source behavior: architecture, implementation location, tests, API compatibility, or an exact source-level explanation.
• Discrepancy, troubleshooting, or release: observed behavior differs from guidance, a Rudder operation failed, or the answer depends on a version.
• Explicit creation or authoring: the user asks to create, hire, or configure a Rudder Agent, or to scaffold, develop, or verify a Rudder Plugin.
• Offline or restricted: the preferred live, public, or source evidence is unavailable.

For a mixed question, resolve each material claim through its owning source instead of applying one global priority.

Choose The Source Route

Current Run Capability And Installed CLI

Inspect exposed typed Rudder tools first. If capability discovery is needed, use rudder agent capabilities --json; then use rudder --version and the exact installed command's --help. Consult the relevant part of the CLI reference only after those live checks. Use the API reference only for an explicit internal, debugging, or compatibility question.

Explicit Agent Or Plugin Work

For Agent creation or configuration, read Agent creation. For Plugin scaffolding or authoring, read Plugin authoring. Verify the current typed capability, installed command, engineering contract, or source before acting. Only an explicit user request to perform the creation or change authorizes entering a mutation workflow; a question about how it works remains read-only.

Official Public Documentation

For public user guidance, start with https://docs.rudderhq.dev/llms.txt. Open only one or two official pages relevant to the request, prefer the user's language when an equivalent page exists, and link the exact page. Do not crawl or load the whole site for a narrow question.

Local Rudder Checkout

Follow the checkout's AGENTS.md, then use doc/README.md to choose the documentation layer: docs/ for public user guidance, doc/plans/ for design proposals, doc/engineering/ for contributor detail, and source and tests for exact implementation. Search the owning area narrowly and cite local paths and line numbers when supported.

Official Remote Source And Releases

When local source is unavailable and source evidence is necessary, use only the official https://github.com/Undertone0809/rudder repository and its release or tag pages by default. Match the release tag to the installed version when explaining installed behavior. Use the default branch only for explicit latest development questions, and label it as latest development, not installed behavior.

Offline Or Restricted Fallback

Offline, use live capabilities and the relevant bundled references, and disclose which preferred source was unavailable, the fallback used, and the resulting limits. Missing evidence narrows the answer; it does not justify invention.

Resolve Versions And Conflicts

Current callable or installed behavior wins for this environment. Proposals record intended changes and rationale. Source and tests own exact implementation evidence. Public docs own published user guidance. An official release or tag owns version-specific history.

Do not flatten disagreement:

• live capability versus docs: say what works now and note likely version or documentation drift;
• installed help versus a bundled reference: use installed help here and label the reference version-adjacent or stale;
• public docs versus source or tests: report documentation drift and identify both;
• proposal versus implementation: distinguish intended changes from shipped behavior;
• default branch versus installed release: use the matching release tag for installed behavior;
• verified evidence versus model memory: discard unsupported memory.

State conflicts and bounded uncertainty explicitly. Do not average sources together or imply certainty that the evidence does not support.