References

Add local directories and Git repositories as project references.

Esta página aún no está disponible en tu idioma.

References give OpenCode access to directories outside the current project. Use them to make documentation, shared libraries, examples, or another repository available while you work.

References are configured by alias in opencode.json or opencode.jsonc.

{
  "$schema": "https://opencode.ai/config.json",
  "references": {
    "docs": {
      "path": "../product-docs",
      "description": "Use for product behavior and documentation conventions",
    },
    "sdk": {
      "repository": "anomalyco/opencode-sdk-js",
      "branch": "main",
      "description": "Use for JavaScript SDK implementation details",
    },
  },
}

Local directories

Use path to reference a local directory.

{
  "references": {
    "docs": {
      "path": "../docs",
    },
  },
}

Paths can be:

Relative to the config file that defines the reference
Absolute, such as /home/user/docs
Relative to your home directory, such as ~/docs

You can also use a string shorthand:

{
  "references": {
    "docs": "../docs",
  },
}

Git repositories

Use repository to reference a Git repository. OpenCode materializes the repository in its local repository cache and makes the checked-out source available as a reference directory.

{
  "references": {
    "effect": {
      "repository": "Effect-TS/effect",
      "branch": "main",
    },
  },
}

repository accepts Git URLs, host/path references, and GitHub owner/repo shorthand. The optional branch field selects a branch or ref. Without branch, OpenCode uses the repository’s default branch.

You can use string shorthand when you do not need a branch, description, or other options:

{
  "references": {
    "effect": "Effect-TS/effect",
  },
}

Describe usage

Add description to explain when an agent should use a reference.

{
  "references": {
    "design-system": {
      "path": "../design-system",
      "description": "Use when implementing UI components or design tokens",
    },
  },
}

OpenCode includes references with descriptions in agent context. Descriptions should be short and specific enough to distinguish references with similar content. References without descriptions remain available through autocomplete and direct use, but are not advertised to agents.

Hide autocomplete entries

Set hidden to true to omit a reference from @ autocomplete in the TUI.

{
  "references": {
    "internal": {
      "path": "../internal",
      "description": "Use for internal implementation details",
      "hidden": true,
    },
  },
}

hidden only affects autocomplete. A hidden reference with a description remains included in agent context.

Use references

Configured references appear in TUI @ autocomplete. Type @alias to attach the reference root, or @alias/ to search for files inside it.

Compare this implementation with @sdk/src/client.ts

Agents also receive the resolved paths and descriptions of configured references that have descriptions in their system context, so they can inspect a reference when it is relevant without you attaching it manually.

OpenCode automatically allows reference directories through its external-directory permission boundary. Normal tool permissions still apply; for example, an agent that cannot edit files does not gain edit access because a directory is configured as a reference.

Configure fields

Field	Local	Git	Description
`path`	Yes	No	Local reference directory
`repository`	No	Yes	Git URL, host/path, or GitHub `owner/repo` value
`branch`	No	Yes	Optional Git branch or ref
`description`	Yes	Yes	Guidance describing when to use the reference
`hidden`	Yes	Yes	Hide the reference from TUI `@` autocomplete

Reference aliases cannot be empty or contain /, whitespace, backticks, or commas.