Configuration

Intent reads consumer configuration from the intent object in package.json. Two keys control which discovered skills Intent surfaces: skills (the allowlist) and exclude (the blocklist).

{
  "intent": {
    "skills": ["@tanstack/query", "workspace:@scope/internal"],
    "exclude": ["@tanstack/router#experimental-*"]
  }
}

Configuration inheritance#

• intent.skills: Intent uses the nearest non-null declaration between the current working directory and the workspace or project root. A nearer declaration replaces its parent. An omitted or null value inherits the nearest parent declaration.
• intent.exclude: Intent combines arrays from the root through the current working directory, then adds excludes passed by the caller.

intent.skills#

intent.skills is a package-source allowlist. A permitted package can:

• Appear in list and stale.
• Resolve through load.
• Contribute mappings to install --map.

The default install command writes generic loading guidance without scanning packages. See Trust model for the reasoning and lifecycle boundaries.

The allowlist permits packages, not individual skills. An entry containing # is invalid; use intent.exclude for skill-specific filtering.

Source entries#

Each array entry names one source:

A malformed entry fails the whole command, and every bad entry is reported at once. Package patterns support * wildcards, including scoped patterns such as @tanstack/*. Intent matches both the package name and source kind: a bare entry permits only an npm source, and a workspace: entry permits only a workspace source.

Special forms#

A package that ships skills but is not listed is dropped. In human output, Intent adds one policy notice naming packages dropped this way so you can opt in. Agent sessions receive only the hidden package and skill counts. A listed package that was not discovered is reported as a notice as well.

Existing projects#

Run intent list to see which packages the current policy surfaces.

A project without intent.skills uses the absent form: Intent surfaces every discovered package and prints its deprecation notice. Add an allowlist to permit specific sources before a future version requires one.

Suppressing notices temporarily#

Use --no-notices to suppress non-critical notices on stderr for one run:

npx @tanstack/intent@latest list --no-notices
npx @tanstack/intent@latest install --map --no-notices

For CI or wrapper scripts, set INTENT_NO_NOTICES=1 to suppress notices without changing command arguments.

Discovery and resolution warnings are separate from policy notices and are not suppressed by these options. The acknowledged-risk notice for "skills": ["*"] also remains visible when other notices are suppressed.

intent.exclude#

intent.exclude removes packages or individual skills after the allowlist resolves.

Use intent exclude to manage this list from the CLI:

npx @tanstack/intent@latest exclude add @tanstack/router#experimental-*
npx @tanstack/intent@latest exclude remove @tanstack/router#experimental-*
npx @tanstack/intent@latest exclude list

{
  "intent": {
    "exclude": ["@tanstack/*devtools*", "@tanstack/router#experimental-*"]
  }
}

Pattern grammar:

• A pattern without # excludes a whole package: @scope/pkg.
• A pattern with # excludes a single skill: @scope/pkg#search-params.
• The skill segment may be a glob: @scope/pkg#experimental-*.
• A pattern may cross package boundaries at skill granularity: *#experimental-*.
• The #* shortcut excludes the whole package: @scope/pkg#*.

Only exact names and * wildcards are supported on each segment. Excludes are source-kind agnostic, so a package pattern excludes matching npm and workspace sources. An excluded package does not trigger the unlisted-source notice, because an exclude is an explicit decision.