Repository navigation
[deep-report] Fix max-runs schema/parser inconsistency (schema allows 0, parser silently treats as unset) #56574
Description
Activity
- added a parent issue
on Aug 28, 2026 🍪 Issue Monster selected this for Copilot
I've identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent.
If assignment succeeds, the Copilot coding agent will analyze the issue and create a pull request with the fix.
Om nom nom! 🍪
Warning
Firewall blocked 4 domains
The following domains were blocked by the firewall during workflow execution:
ab.chatgpt.comapi.github.comchatgpt.comgithub.com
[!TIP]
api.github.comis blocked because GitHub API access uses the built-in GitHub tools by default. Instead of addingapi.github.comtonetwork.allowed, usetools.github.mode: gh-proxyfor direct pre-authenticated GitHub CLI access without requiring network access toapi.github.com:tools: github: mode: gh-proxy
See GitHub Tools for more information on
gh-proxymode.To allow these domains, add them to the
network.allowedlist in your workflow frontmatter:network: allowed: - defaults - "ab.chatgpt.com" - "api.github.com" - "chatgpt.com" - "github.com"
See Network Configuration for more information.
🍪 Om nom nom by Issue Monster · codex · mai10 · 3.2 AIC · ⌖ 0.528 AIC · ⊞ 19.1K · ◷
🍪 Issue Monster selected this for Copilot
I've identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent.
If assignment succeeds, the Copilot coding agent will analyze the issue and create a pull request with the fix.
Om nom nom! 🍪
Warning
Firewall blocked 4 domains
The following domains were blocked by the firewall during workflow execution:
ab.chatgpt.comapi.github.comchatgpt.comgithub.com
[!TIP]
api.github.comis blocked because GitHub API access uses the built-in GitHub tools by default. Instead of addingapi.github.comtonetwork.allowed, usetools.github.mode: gh-proxyfor direct pre-authenticated GitHub CLI access without requiring network access toapi.github.com:tools: github: mode: gh-proxy
See GitHub Tools for more information on
gh-proxymode.To allow these domains, add them to the
network.allowedlist in your workflow frontmatter:network: allowed: - defaults - "ab.chatgpt.com" - "api.github.com" - "chatgpt.com" - "github.com"
See Network Configuration for more information.
🍪 Om nom nom by Issue Monster · codex · mai10 · 2.21 AIC · ⌖ 0.61 AIC · ⊞ 20.3K · ◷
- linked a pull request that will close this issueRequire positive `max-runs` values in workflow schema #56911
on Aug 29, 2026
Description
Schema Consistency Checker (#56553, finding 1) found that
max-runsis schema-valid down to0(pkg/parser/schemas/main_workflow_schema.jsonviatemplatable_integer'sminimum: 0), but the compiler'sparsePositiveIntValue(pkg/workflow/engine_config_parser.go:31-46) silently requires>= 1and treats0as unset/default. A workflow author can pass schema validation withmax-runs: 0and get silently different runtime behavior than what they configured.Expected Impact
Removes a schema/runtime disagreement that could silently produce unexpected run-limit behavior; closes a validation gap that currently gives users false confidence their config is enforced.
Suggested Agent
New Agent / manual — either tighten the schema's
minimumto1formax-runs, or make the parser accept and document0's actual semantics explicitly.Estimated Effort
Quick (< 1 hour)
Data Source
DeepReport analysis 2026-08-28 cycle, from Schema Consistency Checker #56553, finding 1 (verified live against
pkg/workflow/engine_config_parser.go:31-46andpkg/workflow/engine.go:233-245).Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
api.anthropic.comTo allow these domains, add them to the
network.allowedlist in your workflow frontmatter:See Network Configuration for more information.