You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit ded4e71
Browse filesBrowse the repository at this point in the historyBrowse files
description: "Work queues and built-in ledgers land in v0.90.3, alongside safer safe outputs and broader Copilot model support."
4
+
authors:
5
+
- copilot
6
+
date: 2026-10-05
7
+
metadata:
8
+
seoDescription: "gh-aw v0.90.0–v0.90.3: work queues, built-in ledgers, hardened safe outputs, Copilot model routing, and a redesigned docs site."
9
+
---
10
+
11
+
Three releases shipped in [github/gh-aw](https://github.com/github/gh-aw) this week, headlined by work queues and built-in ledgers in [v0.90.3](https://github.com/github/gh-aw/releases/tag/v0.90.3). Here's what's new.
This release introduces **work queues and ledgers**, tightens safe-output guardrails, and broadens Copilot model support.
18
+
19
+
-**Work queue & ledgers**: built-in log, set, map, table, and counter ledgers, plus Git-backed `work-queue` operator commands. See the [ledger compaction docs](https://github.github.com/gh-aw/experimental/ledger-compaction/). Related PRs: [#65494](https://github.com/github/gh-aw/pull/65494) adds selectable issue-backed queue storage, and [#65443](https://github.com/github/gh-aw/pull/65443) dispatches queued work to trusted worker workflows.
20
+
-**Copilot engine**: AWF task-level model routing, `none` and `max` reasoning efforts, GPT-6.1 Sol support, Claude 5.5 and GPT-6 pricing, and a run-wide tool-call budget for Copilot SDK agents.
21
+
-**Safe outputs**: `add-labels` supports separate call and per-call label limits, and several hardening fixes landed. [#65612](https://github.com/github/gh-aw/pull/65612) adds attributed issue creation for custom safe-output jobs.
22
+
-**Docs**: a redesigned site with a new landing page, warm palette, and Mona Sans.
23
+
24
+
Heads-up on behavior changes: GitHub App tokens now require explicit scopes at compile time, Claude defaults to strict MCP configuration, and `add-comment` fails when the triggering target can't be resolved.
Step summaries now render friction cost, agents may emit two `noop` calls by default ([#64031](https://github.com/github/gh-aw/pull/64031)), and five new trajectory graders were added.
33
+
34
+
## Other Notable Pull Requests
35
+
36
+
-[#65423](https://github.com/github/gh-aw/pull/65423) adds a TLA+ workflow security model and fail-closed credential cleanup.
37
+
-[#65564](https://github.com/github/gh-aw/pull/65564) emits incomplete outcomes with diagnostics when an agent produces no safe outputs.
38
+
-[#65650](https://github.com/github/gh-aw/pull/65650) makes PR Sous Chef poll faster and start agents only for actionable work.
39
+
40
+
## 🤖 Agent of the Week: daily-arxiv-researcher
41
+
42
+
A daily scout that reads the latest arXiv papers and looks for ideas that could improve GitHub Agentic Workflows.
43
+
44
+
Its recent runs have all succeeded in about five to six minutes. The October 2 and 3 runs used the Copilot CLI engine, and the October 4 run was the first on the Codex engine with web search and fetch tools, after a [recent change](https://github.com/github/gh-aw/pull/65383) moved it there. That run used roughly 84K tokens, versus 7K and 13K for the earlier runs.
45
+
46
+
The new engine is evidently more curious: it read about six times as many tokens as its predecessor on the same morning schedule.
47
+
48
+
💡 **Usage tip**: Pair a research workflow with a dedup cache, as this one does with `cache-memory`, so it never reports the same paper twice.
49
+
50
+
→ [View the workflow on GitHub](https://github.com/github/gh-aw/blob/main/.github/workflows/daily-arxiv-researcher.md)
51
+
52
+
## Try It Out
53
+
54
+
Update to [v0.90.3](https://github.com/github/gh-aw/releases/tag/v0.90.3) and give work queues a spin. Feedback and contributions are welcome in [github/gh-aw](https://github.com/github/gh-aw).
Copy file name to clipboardExpand all lines: docs/src/content/docs/setup/quick-start.mdx
+6-8Lines changed: 6 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,8 +48,6 @@ import Video from '../../../components/Video.astro';
48
48
49
49
## Adding an Automated Daily Status Workflow to Your Repo
50
50
51
-
### YAML frontmatter
52
-
53
51
GitHub Agentic Workflows lets developers define AI-powered repository automation in Markdown with YAML frontmatter (the configuration block between the `---` markers at the top of the file) and run AI agents through GitHub Actions. By the end of this guide, you will have a recurring agentic workflow running in your repository with GitHub Copilot, Claude Code, OpenAI Codex, Google Gemini, or Pi. This guide takes about 10 minutes and requires only the GitHub CLI.
54
52
55
53
**⏱️ Estimated time: 10 minutes**
@@ -76,7 +74,7 @@ Before installing, ensure you have:
76
74
-**Logged in to GitHub CLI** - Verify with `gh auth status` and run `gh auth login --scopes repo,workflow` if needed
77
75
-**Operating System**: Linux, macOS, or Windows with WSL
### Step 2 - Add the sample workflow and trigger a run
98
+
## Step 2 - Add the sample workflow and trigger a run
101
99
102
100
From your repository root, run this command:
103
101
@@ -128,7 +126,7 @@ This will take you through an interactive process to:
128
126
5. **Optionally add skills for agentic authoring and debugging** - Adds additional files for interactive authoring and debugging of agentic workflows.
129
127
6. **Optionally trigger an initial run** - Starts the workflow immediately.
130
128
131
-
#### Configuring authentication
129
+
### Configuring authentication
132
130
133
131
**Copilot**
134
132
@@ -176,7 +174,7 @@ Pi chooses authentication from the provider prefix in `model:`. It uses Copilot
176
174
177
175
Pi also requires `tools.github.mode: gh-proxy` and `tools.cli-proxy: true`. Follow [Using Pi with GitHub Agentic Workflows](/gh-aw/engines/pi/) for the complete setup.
178
176
179
-
### Step 3 - Wait for the workflow to complete
177
+
## Step 3 - Wait for the workflow to complete
180
178
181
179
An automated workflow run can take 2-3 minutes.
182
180
@@ -201,7 +199,7 @@ import dailyRepoReportResult from '../../../assets/daily-repo-report-result.png'
201
199
202
200
<Image src={dailyRepoReportResult} alt="Example of a Daily Repo Status Report issue created by the workflow" />
203
201
204
-
### Step 4 - Customize your workflow (optional)
202
+
## Step 4 - Customize your workflow (optional)
205
203
206
204
With GitHub Agentic Workflows, you are in control! Your repository automation is fully customizable. You should shape your repo automation to match your priorities and your needs.
207
205
@@ -211,7 +209,7 @@ To customize it now:
211
209
212
210
2. Edit the section "What to include" to list things you are having trouble with regularly in your repository: your issue backlog, your CI setup, your testing, the performance of your software, your roadmap. Any or all of these, or anything else you want to improve. You can also customize the style and process sections to guide the coding agent's behavior.
213
211
214
-
3. If you changed the [frontmatter](#yaml-frontmatter) (the YAML configuration block between the `---` markers at the top of the file), regenerate the compiled workflow by running:
212
+
3. If you changed the frontmatter (the YAML configuration block between the `---` markers at the top of the file), regenerate the compiled workflow by running:
0 commit comments