Version: 2026.2

File Staging

Configuration for the read-only file sets agents can stage. For the mechanism, see Architecture → File Staging.

All keys live under pimcore_agent.file_staging. This is a developer/devops concern; operators do not edit it.

Key	Description
`roots`	Allowlist of project-relative subtrees. Only paths under these may be staged; a glob match outside every root is skipped with a warning. Defaults to empty (nothing stageable).
`denylist`	Filename/path glob patterns always blocked, even within an allowed root - a safety net for credential files (`.env`, `.key`, `*.pem`, `auth.json`, …).
`sets`	Map of set name → `{ description, patterns }`. `patterns` is a list of globs; `description` is shown to the agent so it can pick the right set.

pimcore_agent:
  file_staging:
    roots:                       # only paths under these subtrees may be staged
      - 'templates'
      - 'docs'
    denylist:                    # always blocked, even within an allowed root
      - '.env*'
      - '*.key'
      - '*.pem'
      - 'auth.json'
    sets:
      cms_layouts:
        description: 'CMS page layouts and reference templates for authoring new templates.'
        patterns:
          - 'templates/layouts/cms-*.html.twig'
      brand_docs:
        description: 'Brand guidelines and tone-of-voice documentation.'
        patterns:
          - 'docs/brand/*.md'

Which sets a given agent may stage is set per agent via allowedFileStagingSets - see Configuration → Agents. A non-empty value also auto-registers the stage_file_set tool.

Further reading​

Further reading