Skip to content

Commit 71ba754

Browse files
workshop: add safe-output flow diagram to two-file-structure side quest (#3667)
1 parent 2406024 commit 71ba754

3 files changed

Lines changed: 186 additions & 0 deletions

File tree

Lines changed: 90 additions & 0 deletions
Loading
Lines changed: 90 additions & 0 deletions
Loading

‎workshop/side-quest-05-03-two-file-structure.md‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -97,6 +97,12 @@ Before you reveal the answers below, write a one-sentence definition for each te
9797

9898
An agent always operates **read-only**. Any writes — posting a comment, creating an issue — go through [safe outputs](https://github.github.com/gh-aw/reference/safe-outputs/) and guardrails.
9999

100+
<picture>
101+
<source media="(prefers-color-scheme: dark)" srcset="images/05b-agent-safe-output-flow-dark.svg">
102+
<source media="(prefers-color-scheme: light)" srcset="images/05b-agent-safe-output-flow-light.svg">
103+
<img alt="Agent safe-output flow: the read-only agent inside its sandbox produces a structured output request, which a separate permission-scoped safe-outputs job validates before writing the comment or issue to GitHub" src="images/05b-agent-safe-output-flow-light.svg">
104+
</picture>
105+
100106
**Try it:** Open the `.lock.yml` you compiled earlier. Find the step or job that handles the agent's output. Notice how the write is separated from the agent's read-only work.
101107

102108
> [!TIP]

0 commit comments

Comments
 (0)