Skip to content

[instructions] Sync instruction files with release v0.78.1#36600

Merged
pelikhan merged 1 commit into
mainfrom
instructions-sync-v0.78.1-0e004e0742aba65e
Jun 3, 2026
Merged

[instructions] Sync instruction files with release v0.78.1#36600
pelikhan merged 1 commit into
mainfrom
instructions-sync-v0.78.1-0e004e0742aba65e

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot commented Jun 3, 2026

Summary

Syncs instruction files with release v0.78.1, introducing documentation for three new workflow frontmatter guardrails (max-turns, max-effective-tokens, max-daily-effective-tokens), deprecating the legacy engine.max-turns alias, and adding deduplicate-by-title support (with fuzzy matching) to the issue safe-output type.


What changed and why

New top-level frontmatter guardrails (.github/aw/syntax-agentic.md)

Three new top-level fields are now documented:

Field Purpose
max-turns Hard cap on the number of agentic turns per run
max-effective-tokens Per-run effective-token budget
max-daily-effective-tokens Daily rolling effective-token budget

The engine-level alias engine.max-turns is deprecated in favour of the new top-level max-turns field. No breaking change — existing workflows using the alias continue to work.

Token-optimisation technique 9 (.github/aw/token-optimization.md)

A new "Technique 9" section documents how to use max-effective-tokens and max-daily-effective-tokens as cost-control guardrails, including an inline YAML usage example showing correct frontmatter placement.

deduplicate-by-title on issue safe-outputs (.github/aw/safe-outputs-content.md)

The issue safe-output type now documents a deduplicate-by-title option that removes duplicate issues by title. Accepts either a boolean (exact match) or a positive integer (fuzzy match via edit-distance threshold).


Impact

  • Breaking changes: None
  • Runtime behaviour: Documentation only — no executable code changed
  • Diff stat: Documentation files only; no generated files affected

Checklist

  • Instruction files reflect v0.78.1 release
  • Deprecated alias noted with migration path
  • New frontmatter fields documented in both syntax and token-optimisation guides
  • Fuzzy-match semantics for deduplicate-by-title clearly specified

Generated by PR Description Updater for issue #36600 · sonnet46 1M ·

Document frontmatter/safe-output changes landed since the last sync (v0.77.5):

- max-turns: now a top-level field across all engines; engine.max-turns
  documented as a deprecated alias (PR #36451)
- max-effective-tokens / max-daily-effective-tokens: previously undocumented
  top-level ET guardrail fields, with K/M short-form support and the
  default-on daily guardrail (-1 to disable) (PR #36392, #36496)
- create-issue deduplicate-by-title option (PR #36527)

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- **`max-daily-effective-tokens:`** — Per-user 24-hour guardrail. At activation, gh-aw sums the triggering user's ET across their runs of this workflow over the last 24 hours and blocks execution once the total exceeds the threshold. Enabled by default with a system default threshold; set `-1` to disable, or an explicit value to override the default.

```yaml
max-effective-tokens: 100M # per-run cap (short-form string)
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

10M


```yaml
max-effective-tokens: 100M # per-run cap (short-form string)
max-daily-effective-tokens: 500M # per-user 24h cap; -1 disables
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@copilot 50M

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated both example values — 100M10M and 500M50M in the YAML snippet. Unfortunately the push to this branch is blocked by a repository ruleset ("Cannot create ref due to creations being restricted"), so the commit cannot be pushed. The change is ready locally and can be applied manually if needed.

@pelikhan pelikhan merged commit 1e0d047 into main Jun 3, 2026
8 checks passed
@pelikhan pelikhan deleted the instructions-sync-v0.78.1-0e004e0742aba65e branch June 3, 2026 10:45
Copilot AI requested a review from pelikhan June 3, 2026 10:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automation documentation Improvements or additions to documentation instructions

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants