From 2b789ebcf79ca8585e49cf9f4bb2963db65d1f41 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Tue, 21 Jul 2026 09:15:40 +0000 Subject: [PATCH 1/3] Initial plan From 5f371e3fcb70c931c5fff3e9fbfb0a3078788422 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Tue, 21 Jul 2026 09:26:40 +0000 Subject: [PATCH 2/3] improve active_learning and checkpoint quality in 08b-interpret-your-run.md - Convert 'write one short note' into a structured fill-in code fence exercise - Add a second code block showing a failed run log (403 permission error) for comparison - Expand checkpoint from 3 to 4 items: add 'I can identify whether a run failed due to a permission error, a vague brief, or a missing output' - File stays under 600 words (561 words total) Closes #1776 Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- workshop/08b-interpret-your-run.md | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) diff --git a/workshop/08b-interpret-your-run.md b/workshop/08b-interpret-your-run.md index 79ee3cb9..10c5f4a1 100644 --- a/workshop/08b-interpret-your-run.md +++ b/workshop/08b-interpret-your-run.md @@ -28,7 +28,12 @@ Open the completed **Daily Report Status** run from the **Actions** tab and clic ✅ Done ``` -The important question is not "Can I read every line?" It is "Can I tell where the agent decided, where it acted, and whether it finished?" Find the first `Tool call` in your own run and write one short note about what it was trying to do. +The important question is not "Can I read every line?" It is "Can I tell where the agent decided, where it acted, and whether it finished?" Find the first `Tool call` in your own run and fill in the template below: + +```text +First Tool call I saw: _______________ +What it was trying to do: _______________ +``` ## Check the output @@ -46,6 +51,15 @@ If your run does not look right, start with these quick checks before changing t - **The log shows lots of thinking but no useful action** — your instructions may be too vague. Keep the run open, then refine the workflow body in a later step. - **The run finishes but nothing changed in GitHub** — make sure your repository has an open issue and that the workflow had permission to write. +A failed run log looks different from a successful one. Compare this to the success pattern above: + +```text +🤔 Planning... Searching for open issues +🔧 Tool call: github.list_issues +📥 Error: 403 Forbidden — insufficient permissions +❌ Failed +``` + For a deeper troubleshooting guide, see [Side Quest: Diagnosing Common Agent Output Patterns](side-quest-09-01-debug-output.md). ## ✅ Checkpoint @@ -53,6 +67,7 @@ For a deeper troubleshooting guide, see [Side Quest: Diagnosing Common Agent Out - [ ] I opened the run summary and found the safe-output note - [ ] I verified the real GitHub output that the workflow created - [ ] I know the first check to make if a run is missing, confused, or finished without writing anything +- [ ] I can identify whether a run failed due to a permission error, a vague brief, or a missing output **Next:** [Refine Your Workflow with Agentic Editing](09-agentic-editing.md) From d01d7f4d86126e964c5286fdc1895fb1afade0e9 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Tue, 21 Jul 2026 09:27:39 +0000 Subject: [PATCH 3/3] address code review: improve fill-in placeholder clarity and failed-run context sentence Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- workshop/08b-interpret-your-run.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/workshop/08b-interpret-your-run.md b/workshop/08b-interpret-your-run.md index 10c5f4a1..a97afb9b 100644 --- a/workshop/08b-interpret-your-run.md +++ b/workshop/08b-interpret-your-run.md @@ -31,8 +31,8 @@ Open the completed **Daily Report Status** run from the **Actions** tab and clic The important question is not "Can I read every line?" It is "Can I tell where the agent decided, where it acted, and whether it finished?" Find the first `Tool call` in your own run and fill in the template below: ```text -First Tool call I saw: _______________ -What it was trying to do: _______________ +First Tool call I saw: [tool name, e.g. github.list_issues] +What it was trying to do: [one sentence description] ``` ## Check the output @@ -51,7 +51,7 @@ If your run does not look right, start with these quick checks before changing t - **The log shows lots of thinking but no useful action** — your instructions may be too vague. Keep the run open, then refine the workflow body in a later step. - **The run finishes but nothing changed in GitHub** — make sure your repository has an open issue and that the workflow had permission to write. -A failed run log looks different from a successful one. Compare this to the success pattern above: +Knowing what a failed run looks like helps you spot permission issues at a glance, before you spend time re-reading the brief: ```text 🤔 Planning... Searching for open issues