description	Agentic workflow specific frontmatter fields for GitHub Agentic Workflows.

Agentic Workflow Frontmatter Fields

Agentic Workflow Specific Fields

description: - Human-readable workflow description (string)
emoji: - Optional single emoji used to represent the workflow visually; recommended for quicker recognition in workflow lists and status output (string)
source: - Workflow origin tracking in format owner/repo/path@ref (string)
labels: - Array of labels to categorize and organize workflows (array)
- Labels filter workflows in status/list commands
- Example: labels: [automation, security, daily]
metadata: - Custom key-value pairs compatible with custom agent spec (object)
- Key names limited to 64 characters
- Values limited to 1024 characters
- Example: metadata: { team: "platform", priority: "high" }
github-token: - GitHub token override (must use ${{ secrets.* }} syntax). Not a top-level field: set it under on: (trigger checks), tools.github, or safe-outputs.
on.roles: - Repository access roles that can trigger workflow (array or "all"). Default [admin, maintainer, write]; available roles: admin, maintainer, maintain, write, triage, read, all.
on.bots: - Bot identifiers allowed to trigger workflow regardless of role permissions (array; e.g. [dependabot[bot], renovate[bot], github-actions[bot]]). The bot must be active (installed) on the repository to trigger.
strict: - Enable enhanced validation for production workflows (boolean, defaults to true; strongly recommended)
- Prefer strict: true; strict: false is dangerous, should be extremely rare, and must be carefully security reviewed before use
max-turns: - AWF turn cap applied consistently across all agentic engines (integer or expression, e.g. ${{ inputs.max-turns }}). The engine-level engine.max-turns is a deprecated alias kept for backward compatibility — prefer this top-level field. Not supported by the gemini engine.
max-runs: - Deprecated legacy alias for the AWF invocation cap (apiProxy.maxRuns, defaults to 500 when omitted). Use max-turns instead; run gh aw fix to migrate.
max-ai-credits: - Per-run AI Credits (AIC) budget enforced by the AWF firewall (integer or K/M short-form string like 100M; default 1000). Set a negative value to disable enforcement and token steering. See token-optimization.md.
max-turn-cache-misses: - Maximum consecutive AWF cache misses allowed before the API proxy blocks further requests (integer, default 5). Maps to apiProxy.maxCacheMisses; precedence is frontmatter → GH_AW_DEFAULT_MAX_TURN_CACHE_MISSES env override → built-in default.
models: - Model policy and optional pricing (object). Experimental policy fields allowed / blocked (lists of model names or patterns) restrict which models the workflow may use; they map to AWF apiProxy.allowedModels / disallowedModels and merge as unions across imports. Environment-variable overrides are supported. The separate providers field supplies custom pricing (see token-optimization.md).
```
models:
  allowed: ["gpt-5", "claude-*"]
  blocked: ["*-preview"]
```
max-daily-ai-credits: - Per-user 24-hour AI Credits (AIC) guardrail: activation blocks execution once the triggering user's aggregated AI Credits for this workflow over the last 24h exceed the threshold (integer or K/M short-form string, or -1). Enabled by default with a system default threshold; set -1 to disable or an explicit value to override. See token-optimization.md.
user-rate-limit: - Rate limiting configuration to prevent users from triggering the workflow too frequently (object)
- max-runs-per-window: - Maximum runs allowed per user per time window (required, integer 1-10)
- window: - Time window in minutes (integer 1-180, default: 60)
- events: - Event types to apply rate limiting to (array; if omitted, applies to all programmatic events)
  - Available: workflow_dispatch, issue_comment, pull_request_review, pull_request_review_comment, issues, pull_request, discussion_comment, discussion
- ignored-roles: - Roles exempt from rate limiting (array of admin, maintain, write, triage, read; default: [admin, maintain, write]). Set to [] to apply to all users.
- Example:
```
user-rate-limit:
  max-runs-per-window: 5
  window: 60
  ignored-roles: [admin, maintain]
```
check-for-updates: - Whether the activation job checks that the compiled gh-aw version is still supported (boolean, default true). When true, blocked versions fail fast and below-recommended versions warn. Set false only for isolated environments (compiler then warns at compile time).
features: - Feature flags for experimental or optional features (object)
- Each flag is a key-value pair; boolean flags (true/false) or string values are accepted
- Known feature flags:
  - copilot-requests: true - Use GitHub Actions token for Copilot authentication instead of COPILOT_GITHUB_TOKEN secret
  - disable-xpia-prompt: true - Disable the built-in cross-prompt injection attack (XPIA) system prompt
  - action-tag: "v0" - Pin compiled action references to a specific version of the gh-aw-actions repository. Accepts version tags (e.g., "v0", "v1", "v1.0.0") or a full 40-character commit SHA. When set, overrides the compiler's default action mode and resolves all action references from the external github/gh-aw-actions repository at the specified tag.
  - action-mode: "script" - Control how the compiler generates action references: "dev" (local paths, default), "release" (SHA-pinned remote), "action" (gh-aw-actions repo), "script" (direct shell calls). Can also be overridden via --action-mode CLI flag.
  - difc-proxy: true - Enable DIFC (Data Integrity and Flow Control) proxy injection. When set alongside tools.github.min-integrity, injects proxy steps around the agent for full network-boundary integrity enforcement.
  - cli-proxy: true - Enable AWF CLI proxy sidecar for secure read-only gh CLI access without exposing GITHUB_TOKEN (requires AWF v0.26.0+). Prerequisite for integrity-reactions; the compiler enables it automatically when integrity-reactions: true is set.
  - integrity-reactions: true - Enable reaction-based integrity promotion/demotion. Maintainers can use 👍/❤️ reactions to promote content to approved and 👎/😕 to demote it to none. Compiler automatically enables cli-proxy. Requires tools.github.min-integrity to be set and MCPG >= v0.2.18. Defaults: endorsement reactions THUMBS_UP/HEART, disapproval reactions THUMBS_DOWN/CONFUSED, endorser-min-integrity: approved, disapproval-integrity: none.
  - dangerously-disable-sandbox-agent: "<justification>" - Required when sandbox.agent: false is set. Must be a plain string justification (minimum 20 characters; expressions are not allowed) that explains why disabling the sandbox is safe for this workflow.

experiments: - A/B testing experiments for balanced variant selection (object)

Maps experiment names to variant lists (bare array) or full config objects
Bare array form: prompt_style: [concise, detailed] — round-robin balanced across runs

Object form for weighted/gated experiments:

experiments:
  prompt_style:
    variants: [concise, detailed, step_by_step]
    weight: [2, 1, 1]           # Optional: proportional weights (defaults to round-robin)
    start_date: "2026-05-01"    # Optional: ISO-8601; returns control variant before this date
    end_date: "2026-06-01"      # Optional: ISO-8601; returns control variant after this date
    description: "Verbosity test"  # Optional: experiment description
    metric: "token_count"       # Optional: primary metric name
    issue: "42"                 # Optional: linked tracking issue number

Selected variant available as ${{ experiments.<name> }} and in {{#if experiments.<name> }} template blocks
See A/B Testing Experiments for full design guidance

evals: - ⚠️ Experimental. BinEval binary (YES/NO) evaluation questions run after safe-outputs and before the conclusion job. Shorthand: a list of { id, question, model? } objects. Extended form: object with questions, plus optional model (default alias/ID for all questions) and runs-on.
imports: - Array of workflow specifications to import (array)
- Format: owner/repo/path@ref or local paths like shared/common.md
- Markdown files under .github/agents/ are treated as custom agent files
- Only one agent file is allowed per workflow
- See Imports Field section for detailed documentation
inlined-imports: - Inline all imports at compile time (boolean, default: false)
- When true, all imports (including those without inputs) are inlined in the generated .lock.yml instead of using runtime-import macros
- The frontmatter hash covers the entire markdown body when enabled, so any content change invalidates the hash
- Required for repository rulesets: Workflows used as required status checks in repository rulesets run without access to repository files at runtime. Set inlined-imports: true to bundle all imported content at compile time to avoid "Runtime import file not found" errors
- Constraint: Cannot be combined with agent file imports (.github/agents/ files). Remove any custom agent file imports before enabling
import-schema: - Define typed input parameters for this shared workflow (object). Use when other workflows import this one via the uses:/with: syntax (see Imports Field).
- Parameters are accessible inside the shared workflow via ${{ github.aw.import-inputs.<name> }} expressions
- Object inputs (type: object) allow one-level deep sub-fields: ${{ github.aw.import-inputs.<name>.<subkey> }}
- Fields per parameter:
  - type: - Input type: string, number, boolean, choice, or array
  - description: - Human-readable parameter description
  - required: - Whether the input is required when imported (default: false)
  - default: - Default value when not provided
  - options: - Allowed values for choice type inputs
- Example:
```
import-schema:
  environment:
    type: choice
    description: "Target environment"
    options: [dev, staging, prod]
    required: true
  max-issues:
    type: number
    default: 5
```
mcp-servers: - MCP (Model Context Protocol) server definitions (object)
- Defines custom MCP servers for additional tools beyond built-in ones
private: - Mark this workflow as private, preventing it from being shared via gh aw add (boolean, default: false)
- Example: private: true
redirect: - Workflow relocation path for updates (string). When present, gh aw update follows this location and rewrites the source: field. Format: owner/repo/path@ref or full GitHub URL.
- Example: redirect: "org/agentics/workflows/my-workflow-v2.md@main"
resources: - Additional workflow or action files fetched alongside this workflow when running gh aw add (array). Entries are relative paths from the same directory to .md or .yml/.yaml files.
- Example: resources: [shared/tool-setup.md, shared/mcp/tavily.md]
tracker-id: - Optional identifier to tag all created assets (string)
- Must be at least 8 characters and contain only alphanumeric characters, hyphens, and underscores
- This identifier is inserted in the body/description of all created assets (issues, discussions, comments, pull requests)
- Enables searching and retrieving assets associated with this workflow
- Examples: "workflow-2024-q1", "team-alpha-bot", "security_audit_v2"
secret-masking: - Configuration for secret redaction behavior in workflow outputs and artifacts (object)
- steps: - Additional secret redaction steps to inject after the built-in secret redaction (array)
- Use this to mask secrets in generated files using custom patterns
- Example:
```
secret-masking:
  steps:
    - name: Redact custom secrets
      run: find /tmp/gh-aw -type f -exec sed -i 's/password123/REDACTED/g' {} +
```
observability: - Workflow observability and telemetry configuration (object)
- otlp: - Export OpenTelemetry spans to any OTLP-compatible backend (Honeycomb, Grafana Tempo, Sentry, etc.) (object)
  - endpoint: - OTLP collector endpoint URL. When a static URL is provided, its hostname is added to the AWF firewall allowlist automatically. Supports GitHub Actions expressions.
  - github-app: - Optional runtime auth configuration.
    - Preferred: provide GitHub App credentials (app-id/client-id + private-key) to mint a token with actions/create-github-app-token before actions/setup.
    - OIDC mode is used when github-app is configured without credentials (app-id/client-id + private-key).
    - OIDC mode requires permissions.id-token: write on the workflow/job.
  - headers: - Comma-separated key=value HTTP headers included in every OTLP export request (e.g. Authorization=Bearer <token>). Injected as OTEL_EXPORTER_OTLP_HEADERS. Supports GitHub Actions expressions.
  - resource-attributes: - Optional map of additional OTEL resource attributes appended to gh-aw/GitHub defaults. Values may be static strings or GitHub Actions expressions. Do not use secrets.* or vars.* here because resource attributes are exported to external observability backends and are not treated as secret values.
- Example:
```
observability:
  otlp:
    endpoint: ${{ secrets.GH_AW_OTEL_ENDPOINT }}
    github-app:
      app-id: ${{ vars.APP_ID }}
      private-key: ${{ secrets.APP_PRIVATE_KEY }}
    headers: ${{ secrets.GH_AW_OTEL_HEADERS }}
```
  Every job emits setup and conclusion spans with rich attributes (gh-aw.job.name, gh-aw.workflow.name, gh-aw.engine.id, token usage). All jobs in a run share one trace ID. Dispatched child workflows inherit the parent's trace context via aw_context.
runtimes: - Runtime environment version overrides (object)
- Allows customizing runtime versions (e.g., Node.js, Python) or defining new runtimes
- Runtimes from imported shared workflows are also merged
- Each runtime is identified by a runtime ID (e.g., 'node', 'python', 'go')
- Runtime configuration properties:
  - version: - Runtime version as string or number (e.g., '22', '3.12', 'latest', 22, 3.12)
  - action-repo: - GitHub Actions repository for setup (e.g., 'actions/setup-node')
  - action-version: - Version of the setup action (e.g., 'v4', 'v5')
  - if: - Optional GitHub Actions condition to control when runtime setup runs (e.g., "hashFiles('go.mod') != ''")
- Example:
```
runtimes:
  node:
    version: "22"
  python:
    version: "3.12"
    action-repo: "actions/setup-python"
    action-version: "v5"
  go:
    version: "1.22"
    if: "hashFiles('go.mod') != ''"   # Only install Go when go.mod exists
```
runtimes.node.run-install-scripts: - Allow npm pre/post install scripts to execute during package installation for the Node.js runtime (boolean, default: false)
- By default, --ignore-scripts is added to all generated npm install commands to prevent supply chain attacks via malicious install hooks
- Set run-install-scripts: true under runtimes.node to allow scripts for Node.js installs
- A supply chain security warning is emitted at compile time; in strict mode this is an error
checkout: - Override how the repository is checked out in the agent job (object, array, or false)
- By default, the workflow automatically checks out the repository. Use this field to customize checkout behavior.
- Set to false to disable automatic checkout entirely (reduces startup time when repo access is not needed):
```
checkout: false
```
- Single checkout (object):
```
checkout:
  fetch-depth: 0              # Fetch full history (default: 1 = shallow clone)
  github-token: ${{ secrets.MY_PAT }}  # Override token for private repos
```
- Multiple checkouts (array):
```
checkout:
  - path: .
    fetch-depth: 0
  - repository: owner/other-repo
    path: ./libs/other
    ref: main
```
- Supported fields per checkout entry:
  - repository: - Repository in owner/repo format (defaults to current repository)
  - ref: - Branch, tag, or SHA to check out (defaults to triggering ref)
  - path: - Relative path within GITHUB_WORKSPACE (defaults to workspace root)
  - fetch-depth: - Number of commits to fetch; 0 = full history, 1 = shallow (default)
  - fetch: - Additional Git refs to fetch after checkout (array of patterns)
    - "*" - fetch all remote branches
    - "refs/pulls/open/*" - all open pull-request refs
    - Branch names, glob patterns (e.g., "feature/*")
    - Example: fetch: ["*"], fetch: ["refs/pulls/open/*"]
  - sparse-checkout: - Newline-separated glob patterns for sparse checkout
  - submodules: - Submodule handling: "recursive", "true", or "false"
  - lfs: - Download Git LFS objects (boolean, default: false)
  - wiki: - Check out the repository's wiki (boolean, default: false). When true, automatically appends .wiki to the repository name. Combine with repository: to check out a different repo's wiki.
  - github-token: - Token for authentication (${{ secrets.MY_PAT }}); credentials removed after checkout
jobs: - Groups together all the jobs that run in the workflow (object)
- Standard GitHub Actions jobs configuration
- Each job can have: name, runs-on, steps, needs, if, env, permissions, timeout-minutes, etc.
- For most agentic workflows, jobs are auto-generated; only specify this for advanced multi-job workflows
- Security Notice: Custom jobs run OUTSIDE the firewall sandbox. Execute with standard GitHub Actions security but NO network egress controls. Use only for deterministic preprocessing, data fetching, or static analysis—not agentic compute or untrusted AI execution.
- setup-steps: - Steps injected at the earliest point in a custom or built-in job, before framework GitHub App token minting and before checkout (array). Use this for OIDC login, secret fetch, and credential bootstrap that must happen before framework token/checkout steps. Imported setup-steps run before main workflow setup-steps.
- pre-steps: - Steps injected after framework setup scaffolding and before the job's main steps: in a custom or built-in job (array). For built-in jobs, this is after the id: setup step (which includes framework token minting/checkout setup) and before the first checkout. Imported pre-steps run before main workflow pre-steps.
- setup-steps vs pre-steps - Use setup-steps for work that must run before framework GitHub App token minting and checkout (e.g., OIDC/secret bootstrap). Use pre-steps for work that should run later, after setup scaffolding and before the job's main steps:.
- Migration note - No migration is required. setup-steps is additive; existing workflows that only use pre-steps continue to behave as before.
- Example:
```
jobs:
  custom-job:
    runs-on: ubuntu-latest
    setup-steps:
      - name: Bootstrap credentials
        run: echo "runs before framework token/checkout setup"
    pre-steps:
      - name: Pre-flight setup
        run: echo "runs before checkout"
    steps:
      - name: Custom step
        run: echo "Custom job"
```
- setup-steps/pre-steps also apply to built-in jobs (e.g. activation): use setup-steps for OIDC/secret bootstrap that must run before framework token minting, then verify the result in pre-steps.
engine: - AI processor configuration
- String format: "copilot" (default, recommended), "claude", "codex", "gemini", or the experimental "antigravity", "opencode", "crush", "pi"
- Object format for extended configuration:
```
engine:
  id: copilot                       # Required: coding agent identifier (copilot, claude, codex, gemini; experimental: antigravity, opencode, crush, pi)
  version: beta                     # Optional: version of the action (has sensible default); also accepts GitHub Actions expressions: ${{ inputs.engine-version }}
  model: gpt-5                      # Optional: LLM model to use (has sensible default)
  permission-mode: acceptEdits      # Optional (claude only): auto | acceptEdits | plan | bypassPermissions. Default: acceptEdits (auto when tools.edit is false)
  agent: technical-doc-writer       # Optional: custom agent file (Copilot only, references .github/agents/{agent}.agent.md)
  max-turns: 5                      # Deprecated alias for the top-level `max-turns`; prefer the top-level field
  max-continuations: 3              # Optional: max autopilot continuations (copilot only; >1 enables --autopilot mode, default: 1)
  concurrency: "gh-aw-${{ github.workflow }}"  # Optional: agent job concurrency group (string or GitHub Actions concurrency object)
  env:                              # Optional: custom environment variables (object)
    DEBUG_MODE: "true"
  args: ["--verbose"]               # Optional: custom CLI arguments injected before prompt (array)
  api-target: api.acme.ghe.com      # Optional: custom API endpoint hostname for GHEC/GHES (hostname only, no protocol/path)
  command: /usr/local/bin/copilot   # Optional: override default engine executable (skips installation)
  bare: true                        # Optional: disable automatic context loading (copilot: --no-custom-instructions; claude: --bare; codex: --no-system-prompt; gemini: GEMINI_SYSTEM_MD=/dev/null). Default: false
  user-agent: "myapp/1.0"           # Optional: custom user agent string (codex engine only)
  config: |                         # Optional: additional TOML config appended to config.toml (codex engine only)
    [extra]
    key = "value"
```
- gemini engine: Google Gemini CLI. Requires GEMINI_API_KEY secret. Does not support max-turns, web-fetch, or web-search. Supports AWF firewall and LLM gateway.
- antigravity engine (experimental): Google Antigravity CLI in headless mode. Requires ANTIGRAVITY_API_KEY secret; model via model: (maps to ANTIGRAVITY_MODEL). Supports max-turns, tools allow-list, AWF firewall, and LLM gateway. Does not support web-search, max-continuations, or native agent files (agent content is prepended to the prompt).
- opencode engine (experimental): Provider-agnostic, open-source AI coding agent (BYOK). Defaults to Copilot routing via COPILOT_GITHUB_TOKEN (or ${{ github.token }} with copilot-requests feature). Supports 75+ models via provider/model format. Supports AWF firewall and LLM gateway.
- engine.driver: — canonical field to run a custom inner driver script instead of the engine's built-in CLI. For the pi engine it launches the driver directly with Node.js (e.g. built-in pi_agent_core_driver.cjs, or a workspace-relative path like .github/drivers/pi_agent_core_driver_sample_node.cjs); the driver must emit JSONL compatible with parse_pi_log.cjs so step summaries and token tracking keep working. Accepts a bare basename (resolved from the setup-action directory) or a workspace-relative path; no absolute paths, no .., only .js/.cjs/.mjs (pi).
- copilot-sdk / engine.driver (experimental, copilot only): set copilot-sdk: true to start a headless Copilot CLI SDK sidecar. Set driver: <path-or-command> on the copilot engine to supply a custom SDK driver (.js/.cjs/.mjs/.py/.ts/.mts/.rb, or a bare PATH command); this also enables copilot-sdk: true automatically. Tune the repeated-tool-denial safeguard with the top-level max-tool-denials: field (default 5).
- engine.auth: — keyless Workload Identity Federation via the AWF API proxy instead of a static API key; requires id-token: write. Set type: github-oidc (only supported type) plus provider: azure (azure-tenant-id, azure-client-id, optional azure-scope/azure-cloud) for Azure OpenAI, or provider: anthropic (federation-rule-id, organization-id, service-account-id, workspace-id) for Claude. Optional audience:. Maps to AWF_AUTH_* env vars.
- Advanced engine sub-fields (see the engine_config definition in pkg/parser/schemas/main_workflow_schema.json): model-provider (github | anthropic | openai), harness (retry policy), engine-level mcp (session-timeout/tool-timeout), extensions, and cwd.
network: - Network access control for AI engines (top-level field)
- String format: "defaults" (curated allow-list of development domains)
- Empty object format: {} (no network access)
- Object format for custom permissions:
```
network:
  allowed:
    - "example.com"
    - "*.trusted-domain.com"
    - "https://api.secure.com"        # Optional: protocol-specific filtering
  blocked:
    - "blocked-domain.com"
    - "*.untrusted.com"
    - python                          # Block ecosystem identifiers
```
- Firewall (AWF) configuration is set under sandbox.agent, not network. Use sandbox.agent.version to pin the AWF version (see below). The legacy network.firewall field is deprecated; run gh aw fix to migrate.
sandbox: - Sandbox configuration for AI engines (string or object)
- String format: "default" (default sandbox), "awf" (Agent Workflow Firewall)
- Object format to pin an AWF version (strict mode requires explicit id: awf):
```
sandbox:
  agent:
    id: awf                     # Required in strict mode
    version: "v0.25.29"         # Optional: pin AWF version
    model-fallback: false       # Optional: disable model fallback (default true); set false for BYOK Azure OpenAI to prevent deployment-name rewriting
```
- To disable the agent firewall while keeping MCP gateway enabled, you must provide the dangerous-disable justification feature:
```
features:
  dangerously-disable-sandbox-agent: "controlled environment with no internet access"
sandbox:
  agent: false
```
- sandbox.agent.sudo (boolean) controls whether AWF runs in root mode. Default is false: AWF runs rootless in network-isolation egress mode (--network-isolation), with MCP sidecars attached as bridge containers on the internal awf-net network. Set sudo: true for the legacy root mode; in strict mode explicit sudo: true is an error (warning otherwise).
- Strict mode: sandbox.agent blocks without an explicit id: awf are rejected in strict mode. Any non-nil, non-disabled agent config without id/type defaults to AWF at runtime.
tools: - Tool configuration for the coding agent (github, agentic-workflows, edit, web-fetch, web-search, bash, playwright, custom MCP server names, plus timeout/startup-timeout/cli-proxy). See syntax-tools-imports.md for the full schema (GitHub mode/toolsets/integrity fields, bash allowlist decision rule, Playwright CLI mode).
safe-outputs: - Safe output processing configuration. See safe-outputs.md for complete documentation of all output types: create-issue, create-discussion, add-comment, create-pull-request, push-to-pull-request-branch, close-issue, close-discussion, update-issue, update-pull-request, add-labels, remove-labels, replace-label, dispatch-workflow, call-workflow, create-code-scanning-alert, upload-asset, upload-artifact, assign-to-agent, assign-to-user, and more.

Key safe-outputs global fields (detail in safe-outputs-runtime.md): github-token, github-app, staged (preview mode, no API calls), footer, threat-detection, runs-on (default ubuntu-slim), messages, env, max-patch-size (KB, default 4096).
mcp-scripts: - Define custom lightweight MCP tools as JavaScript, shell, Python, or Go scripts (object)
- Tools mounted in MCP server with access to specified secrets
- Each tool requires description and one of: script (JavaScript), run (shell), py (Python), or go (Go)
- Tool configuration properties:
  - description: - Tool description (required)
  - inputs: - Input parameters with type and description (object)
  - script: - JavaScript implementation (CommonJS format)
  - run: - Shell script implementation
  - py: - Python script implementation
  - go: - Go script implementation (executed via go run, receives inputs as JSON via stdin)
  - env: - Environment variables for secrets (supports ${{ secrets.* }})
  - dependencies: - Runtime packages installed before first invocation (list of strings). Manager inferred from script type: script→npm, py→pip, go→go get, run→apt. Must be exact-version-pinned (name@1.2.3, name==1.2.3, module@v1.2.3, name=1.6); floating refs are rejected.
  - timeout: - Execution timeout in seconds (default: 60)
- Example:
```
mcp-scripts:
  search-issues:
    description: "Search GitHub issues using API"
    inputs:
      query: { type: string, description: "Search query", required: true }
    script: |
      const { Octokit } = require('@octokit/rest');
      const octokit = new Octokit({ auth: process.env.GH_TOKEN });
      const r = await octokit.search.issuesAndPullRequests({ q: inputs.query });
      return r.data.items;
    dependencies: ["@octokit/rest@21.0.2"]
    env:
      GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
```
slash_command: - Command trigger configuration for /mention workflows (under on:)
cache: - Cache configuration for workflow dependencies (object or array)
cache-memory: - Memory MCP server with persistent cache storage (boolean or object, under tools:)
repo-memory: - Repository-specific memory storage (boolean, under tools:)
comment-memory: - Managed issue/PR comment memory with file-based agent editing (boolean or object, under tools:)

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Agentic Workflow Frontmatter Fields

Agentic Workflow Specific Fields

Uh oh!

FilesExpand file tree

syntax-agentic.md

Latest commit

History

syntax-agentic.md

File metadata and controls

Agentic Workflow Frontmatter Fields

Agentic Workflow Specific Fields