From 93f368e4e5bfa1aa9a91d2e0136941b313dbb2ef Mon Sep 17 00:00:00 2001
From: James Montemagno <james.montemagno@gmail.com>
Date: Mon, 5 Oct 2026 10:06:51 -0700
Subject: [PATCH 1/6] docs: split My work into Pull requests and Issues in app
 tour

Sync the Copilot app first steps workshop with upstream jamesmontemagno/first-steps-with-github-copilot#11. The app replaced My work with separate Pull requests and Issues views, so update the workspace overview, the issue and plan lessons, and the Canvas fallback note. Redraw the Issues illustration and refresh the Automations sidebar from upstream art.js.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
---
 docs/_images/first-steps-app-automations.svg  | 19 ++----
 ...my-work.svg => first-steps-app-issues.svg} | 62 ++++++++-----------
 .../copilot-app/0-prerequisites.md            |  6 +-
 docs/first-steps/copilot-app/11-canvas.md     |  4 +-
 .../copilot-app/6-issues-and-sessions.md      | 14 ++---
 docs/first-steps/copilot-app/7-plan-mode.md   |  4 +-
 6 files changed, 48 insertions(+), 61 deletions(-)
 rename docs/_images/{first-steps-app-my-work.svg => first-steps-app-issues.svg} (50%)

diff --git a/docs/_images/first-steps-app-automations.svg b/docs/_images/first-steps-app-automations.svg
index d28de07d..d38288ac 100644
--- a/docs/_images/first-steps-app-automations.svg
+++ b/docs/_images/first-steps-app-automations.svg
@@ -67,19 +67,12 @@
 <rect class="stroke" x="84" y="20" width="18" height="16" rx="3"/><path class="stroke" d="M91 20v16"/>
 <circle class="stroke" cx="130" cy="28" r="6"/><path class="stroke" d="m135 33 4 4"/>
 <path class="stroke" d="M162 22l-6 6 6 6M180 22l6 6-6 6"/>
-<path class="stroke" d="M28 66h16M36 58v16"/><text class="t-sm txt" x="56" y="71">New</text>
-<path class="stroke" d="M28 96h6v6h-6zM28 106h6v4h-6zM40 99h10M40 108h10"/>
-<text class="t-sm mut" x="58" y="105">My work</text>
-<rect class="card sel" x="14" y="118" width="184" height="30" rx="8"/>
-<rect class="stroke" x="27" y="126" width="15" height="13" rx="2.5"/><path class="stroke" d="M27 130h15M31 124v4M38 124v4"/>
-<text class="t-sm txt" x="58" y="137">Automations</text>
-<rect class="stroke" x="27" y="158" width="7" height="7" rx="1.5"/><rect class="stroke" x="36" y="158" width="7" height="7" rx="1.5"/><rect class="stroke" x="27" y="167" width="7" height="7" rx="1.5"/>
-<text class="t-sm mut" x="58" y="170">Customize</text>
-<path class="rule" d="M14 194h184"/>
-<text class="t-xs mut" x="28" y="218">Projects</text>
-<path class="stroke" d="M158 213h12M160 217h8M162 221h4M180 217h12M186 211v12"/>
-<rect class="card" x="14" y="232" width="184" height="26" rx="7"/>
-<text class="t-xs mut" x="28" y="249">space-quiz</text>
+<path class="stroke" d="M29 57h14M36 50v14"/><text class="t-sm txt" x="58" y="62">New</text><circle class="stroke" cx="31" cy="79" r="2.2"/><circle class="stroke" cx="31" cy="91" r="2.2"/><circle class="stroke" cx="41" cy="91" r="2.2"/><path class="stroke" d="M31 81.2v7.6M41 88.8V82a3 3 0 0 0-3-3h-3.5m2.5-2.5-2.5 2.5 2.5 2.5"/><text class="t-sm mut" x="58" y="90">Pull requests</text><circle class="stroke" cx="36" cy="113" r="7"/><circle class="stroke" cx="36" cy="113" r="1.5"/><text class="t-sm mut" x="58" y="118">Issues</text><rect class="card sel" x="14" y="128" width="184" height="26" rx="8"/><rect class="stroke" x="27" y="135" width="15" height="13" rx="2.5"/><path class="stroke" d="M27 139h15M31 133v4M38 133v4"/><text class="t-sm txt" x="58" y="146">Automations</text><rect class="stroke" x="27" y="162" width="7" height="7" rx="1.5"/><rect class="stroke" x="36" y="162" width="7" height="7" rx="1.5"/><rect class="stroke" x="27" y="171" width="7" height="7" rx="1.5"/><text class="t-sm mut" x="58" y="174">Customize</text><circle class="stroke" cx="29" cy="197" r="1.2"/><circle class="stroke" cx="36" cy="197" r="1.2"/><circle class="stroke" cx="43" cy="197" r="1.2"/><text class="t-sm mut" x="58" y="202">More</text>
+<path class="rule" d="M14 216h184"/>
+<text class="t-xs mut" x="28" y="236">Projects</text>
+<path class="stroke" d="M158 231h12M160 235h8M162 239h4M180 235h12M186 229v12"/>
+<rect class="card" x="14" y="248" width="184" height="26" rx="7"/>
+<text class="t-xs mut" x="28" y="265">space-quiz</text>
 <text class="t-sm txt" x="236" y="34">Automations</text>
 <rect class="chip" x="430" y="18" width="88" height="24" rx="7"/><text class="t-xs txt" x="474" y="34" text-anchor="middle">Templates</text>
 <rect class="cta" x="526" y="18" width="110" height="24" rx="7"/><text class="t-xs inv" x="581" y="34" text-anchor="middle">New automation</text>
diff --git a/docs/_images/first-steps-app-my-work.svg b/docs/_images/first-steps-app-issues.svg
similarity index 50%
rename from docs/_images/first-steps-app-my-work.svg
rename to docs/_images/first-steps-app-issues.svg
index bbab0bc0..9ab5fc8d 100644
--- a/docs/_images/first-steps-app-my-work.svg
+++ b/docs/_images/first-steps-app-issues.svg
@@ -1,5 +1,5 @@
 <!-- Adapted from First Steps with GitHub Copilot by James Montemagno (MIT License): https://github.com/jamesmontemagno/first-steps-with-github-copilot -->
-<svg xmlns="http://www.w3.org/2000/svg" width="640" height="300" class="art" viewBox="0 0 640 300" role="img" aria-label="The My work view in the Copilot app with the sidebar and a list of pull requests"><title>The My work view in the Copilot app with the sidebar and a list of pull requests</title><style>svg { --bg: #080b12; --bg-elevated: #0d111a; --surface: #121824; --surface-2: #171e2c; --border: #283043; --border-soft: #1d2636; --text: #f1f5fb; --muted: #9ca8ba; --subtle: #6d788b; --purple: #a371f7; --purple-bright: #bf8cff; --blue: #58a6ff; --cyan: #56d4dd; --green: #3fb950; --yellow: #d29922; }
+<svg xmlns="http://www.w3.org/2000/svg" width="640" height="300" class="art" viewBox="0 0 640 300" role="img" aria-label="The Issues view in the Copilot app with the sidebar and a list of issues assigned to you"><title>The Issues view in the Copilot app with the sidebar and a list of issues assigned to you</title><style>svg { --bg: #080b12; --bg-elevated: #0d111a; --surface: #121824; --surface-2: #171e2c; --border: #283043; --border-soft: #1d2636; --text: #f1f5fb; --muted: #9ca8ba; --subtle: #6d788b; --purple: #a371f7; --purple-bright: #bf8cff; --blue: #58a6ff; --cyan: #56d4dd; --green: #3fb950; --yellow: #d29922; }
 @media (prefers-color-scheme: light) { svg { --bg: #f7f8fb; --bg-elevated: #fff; --surface: #fff; --surface-2: #f1f3f8; --border: #d5dae5; --border-soft: #e7eaf0; --text: #161b26; --muted: #536071; --subtle: #727c8c; --purple: #6f42c1; --purple-bright: #8250df; --blue: #0969da; --cyan: #087e8b; --green: #1a7f37; --yellow: #9a6700; } }
 .art .plate { fill: var(--bg-elevated); stroke: var(--border); }
 .art .panel { fill: var(--surface); }
@@ -67,38 +67,30 @@
 <rect class="stroke" x="84" y="20" width="18" height="16" rx="3"/><path class="stroke" d="M91 20v16"/>
 <circle class="stroke" cx="130" cy="28" r="6"/><path class="stroke" d="m135 33 4 4"/>
 <path class="stroke" d="M162 22l-6 6 6 6M180 22l6 6-6 6"/>
-<path class="stroke" d="M28 66h16M36 58v16"/><text class="t-sm txt" x="56" y="71">New</text>
-<rect class="card sel" x="14" y="86" width="184" height="30" rx="8"/>
-<path class="stroke" d="M28 96h6v6h-6zM28 106h6v4h-6z"/><path class="stroke" d="M40 99h10M40 108h10"/>
-<text class="t-sm txt" x="58" y="105">My work</text>
-<rect class="stroke" x="27" y="126" width="15" height="13" rx="2.5"/><path class="stroke" d="M27 130h15M31 124v4M38 124v4"/>
-<text class="t-sm mut" x="58" y="137">Automations</text>
-<rect class="stroke" x="27" y="158" width="7" height="7" rx="1.5"/><rect class="stroke" x="36" y="158" width="7" height="7" rx="1.5"/><rect class="stroke" x="27" y="167" width="7" height="7" rx="1.5"/>
-<text class="t-sm mut" x="58" y="170">Customize</text>
-<path class="rule" d="M14 194h184"/>
-<text class="t-xs mut" x="28" y="218">Projects</text>
-<path class="stroke" d="M158 213h12M160 217h8M162 221h4"/>
-<path class="stroke" d="M180 217h12M186 211v12"/>
-<rect class="card" x="14" y="232" width="184" height="26" rx="7"/>
-<text class="t-xs mut" x="28" y="249">space-quiz</text>
-<text class="t-sm txt" x="236" y="34">My work</text>
-<rect class="chip sel" x="236" y="52" width="46" height="24" rx="8"/><text class="t-xs accent" x="259" y="68" text-anchor="middle">All</text>
-<text class="t-xs mut" x="298" y="68">Active</text>
-<text class="t-xs mut" x="352" y="68">Review requests</text>
-<text class="t-xs mut" x="464" y="68">Done</text>
-<path class="stroke" d="M508 64h12M514 58v12"/>
-<path class="rule" d="M224 88h416"/>
-<g>
-<circle class="ok-stroke" cx="242" cy="112" r="3"/><circle class="ok-stroke" cx="242" cy="128" r="3"/><circle class="ok-stroke" cx="256" cy="112" r="3"/><path class="ok-stroke" d="M242 115v10M256 115v8a5 5 0 0 1-5 5h-6"/>
-<text class="t-sm txt" x="272" y="116">Move the route picker into the lab</text><text class="t-sm mut" x="512" y="116">#5</text>
-<text class="t-xs mut" x="272" y="134">jamesmontemagno/first-steps-with-github-copilot</text>
-<text class="t-xs mut" x="272" y="150">10m ago</text>
-</g>
-<g>
-<circle class="alt-stroke" cx="242" cy="186" r="3"/><circle class="alt-stroke" cx="242" cy="202" r="3"/><circle class="alt-stroke" cx="256" cy="194" r="3"/><path class="alt-stroke" d="M242 189v10M245 193h8"/>
-<text class="t-sm txt" x="272" y="190">Polish the multi-product lab</text><text class="t-sm mut" x="470" y="190">#4</text>
-<text class="t-xs mut" x="272" y="208">jamesmontemagno/first-steps-with-github-copilot</text>
-<text class="t-xs mut" x="272" y="224">3h ago</text>
-</g>
-<text class="t-xs accent" x="236" y="266">Every issue and pull request you care about, without leaving the app.</text>
+<path class="stroke" d="M29 57h14M36 50v14"/><text class="t-sm txt" x="58" y="62">New</text><circle class="stroke" cx="31" cy="79" r="2.2"/><circle class="stroke" cx="31" cy="91" r="2.2"/><circle class="stroke" cx="41" cy="91" r="2.2"/><path class="stroke" d="M31 81.2v7.6M41 88.8V82a3 3 0 0 0-3-3h-3.5m2.5-2.5-2.5 2.5 2.5 2.5"/><text class="t-sm mut" x="58" y="90">Pull requests</text><rect class="card sel" x="14" y="100" width="184" height="26" rx="8"/><circle class="stroke" cx="36" cy="113" r="7"/><circle class="stroke" cx="36" cy="113" r="1.5"/><text class="t-sm txt" x="58" y="118">Issues</text><rect class="stroke" x="27" y="135" width="15" height="13" rx="2.5"/><path class="stroke" d="M27 139h15M31 133v4M38 133v4"/><text class="t-sm mut" x="58" y="146">Automations</text><rect class="stroke" x="27" y="162" width="7" height="7" rx="1.5"/><rect class="stroke" x="36" y="162" width="7" height="7" rx="1.5"/><rect class="stroke" x="27" y="171" width="7" height="7" rx="1.5"/><text class="t-sm mut" x="58" y="174">Customize</text><circle class="stroke" cx="29" cy="197" r="1.2"/><circle class="stroke" cx="36" cy="197" r="1.2"/><circle class="stroke" cx="43" cy="197" r="1.2"/><text class="t-sm mut" x="58" y="202">More</text>
+<path class="rule" d="M14 216h184"/>
+<text class="t-xs mut" x="28" y="236">Projects</text>
+<path class="stroke" d="M158 231h12M160 235h8M162 239h4M180 235h12M186 229v12"/>
+<rect class="card" x="14" y="248" width="184" height="26" rx="7"/>
+<text class="t-xs mut" x="28" y="265">space-quiz</text>
+<text class="t-sm txt" x="236" y="34">Issues</text>
+<rect class="chip" x="432" y="18" width="112" height="24" rx="7"/><text class="t-xs txt" x="488" y="34" text-anchor="middle">All repositories ⌄</text>
+<rect class="chip" x="552" y="18" width="84" height="24" rx="7"/><text class="t-xs txt" x="594" y="34" text-anchor="middle">New issue</text>
+<rect class="chip sel" x="236" y="52" width="86" height="24" rx="8"/><text class="t-xs accent" x="279" y="68" text-anchor="middle">Assigned to me</text>
+<text class="t-xs mut" x="336" y="68">Created by me</text>
+<text class="t-xs mut" x="420" y="68">Mentioning me</text>
+<text class="t-xs mut" x="508" y="68">Done</text>
+<path class="stroke" d="M548 64h12M554 58v12"/>
+<rect class="input" x="236" y="86" width="120" height="22" rx="7"/>
+<circle class="stroke" cx="250" cy="96" r="4"/><path class="stroke" d="m253 99 3 3"/>
+<text class="t-xs mut" x="262" y="101">Search…</text>
+<rect class="chip" x="364" y="86" width="96" height="22" rx="7"/>
+<text class="t-xs mut" x="374" y="101">State is</text><circle class="ok-stroke" cx="420" cy="97" r="4"/><text class="t-xs txt" x="428" y="101">Open</text>
+<rect class="chip" x="468" y="86" width="98" height="22" rx="7"/>
+<text class="t-xs mut" x="478" y="101">Assignee is</text><text class="t-xs txt" x="534" y="101">@me</text>
+<path class="rule" d="M224 120h416"/>
+<rect class="stroke" x="236" y="132" width="10" height="10" rx="2"/><circle class="ok-stroke" cx="262" cy="138" r="6"/><circle class="ok-fill" cx="262" cy="138" r="2"/><text class="t-sm txt" x="276" y="142">Add a per-question timer <tspan class="mut">#12</tspan></text><text class="t-xs mut" x="276" y="160">jamesmontemagno/space-quiz · 5m ago</text>
+<rect class="stroke" x="236" y="176" width="10" height="10" rx="2"/><circle class="ok-stroke" cx="262" cy="182" r="6"/><circle class="ok-fill" cx="262" cy="182" r="2"/><text class="t-sm txt" x="276" y="186">Show a review screen after the last question <tspan class="mut">#13</tspan></text><text class="t-xs mut" x="276" y="204">jamesmontemagno/space-quiz · 5m ago</text>
+<rect class="stroke" x="236" y="220" width="10" height="10" rx="2"/><circle class="ok-stroke" cx="262" cy="226" r="6"/><circle class="ok-fill" cx="262" cy="226" r="2"/><text class="t-sm txt" x="276" y="230">Save a local high score board <tspan class="mut">#14</tspan></text><text class="t-xs mut" x="276" y="248">jamesmontemagno/space-quiz · 5m ago</text>
+<text class="t-xs accent" x="236" y="280">Open any issue and start a session on it without leaving the app.</text>
 </svg>
diff --git a/docs/first-steps/copilot-app/0-prerequisites.md b/docs/first-steps/copilot-app/0-prerequisites.md
index 61e31e86..f732ed76 100644
--- a/docs/first-steps/copilot-app/0-prerequisites.md
+++ b/docs/first-steps/copilot-app/0-prerequisites.md
@@ -3,7 +3,7 @@ title: "Lesson 0 - Prerequisites and setup"
 description: "Verify the workshop prerequisites, install the GitHub Copilot app, and get familiar with its workspace."
 authors:
   - jamesmontemagno
-lastUpdated: 2026-09-28
+lastUpdated: 2026-10-05
 ---
 
 Before you build the Space Quiz, confirm that you have what you need, install the GitHub Copilot app, and get familiar with its workspace.
@@ -50,9 +50,11 @@ Model availability depends on your plan, organization policy, and product versio
 The app brings the development workflow into one place:
 
 - **New**: Start a session on a project, or choose **Chat** for a quick question.
-- **My work**: Browse your GitHub issues and pull requests.
+- **Pull requests**: Review and track your pull requests across every repository.
+- **Issues**: Find issues assigned to you, created by you, or mentioning you.
 - **Automations**: Schedule recurring agent work on a repository.
 - **Customize**: Change themes and models, and manage Canvas extensions.
+- **Projects**: Open your repositories, with each one's sessions listed underneath.
 
 ## Try a quick chat
 
diff --git a/docs/first-steps/copilot-app/11-canvas.md b/docs/first-steps/copilot-app/11-canvas.md
index 55a181dc..60338519 100644
--- a/docs/first-steps/copilot-app/11-canvas.md
+++ b/docs/first-steps/copilot-app/11-canvas.md
@@ -3,7 +3,7 @@ title: "Lesson 11 - Explore a Canvas"
 description: "Install a Repository Issues Kanban Canvas and start a session from an issue card."
 authors:
   - jamesmontemagno
-lastUpdated: 2026-09-28
+lastUpdated: 2026-10-05
 ---
 
 A **Canvas** is a shared, bidirectional surface where you and an agent can update the same plan, board, checklist, or dashboard. Explore a Kanban Canvas that turns repository issues into a visual workflow.
@@ -37,7 +37,7 @@ In this lesson, you will:
 When you drop a card into a lane, the Canvas hands that issue to a new session with the issue already loaded.
 
 > [!NOTE]
-> The current Repository Issues Kanban extension moves cards with pointer-based drag and drop. If you cannot use that interaction, note the issue number on the board, open the issue in **My work**, then select **New session**. This creates the same issue-grounded session without moving the card.
+> The current Repository Issues Kanban extension moves cards with pointer-based drag and drop. If you cannot use that interaction, note the issue number on the board, open the issue from **Issues**, then select **New session**. This creates the same issue-grounded session without moving the card.
 
 The Canvas provides a visual way to select and begin work while keeping the agent grounded in the issue.
 
diff --git a/docs/first-steps/copilot-app/6-issues-and-sessions.md b/docs/first-steps/copilot-app/6-issues-and-sessions.md
index 268c9ff3..b40f2454 100644
--- a/docs/first-steps/copilot-app/6-issues-and-sessions.md
+++ b/docs/first-steps/copilot-app/6-issues-and-sessions.md
@@ -3,7 +3,7 @@ title: "Lesson 6 - Work with issues and sessions"
 description: "Create a focused backlog, select an issue, implement it in an isolated worktree, and review the diff yourself."
 authors:
   - jamesmontemagno
-lastUpdated: 2026-09-28
+lastUpdated: 2026-10-05
 ---
 
 Ask the agent to suggest focused product improvements, turn those ideas into GitHub issues, and implement one issue in an isolated session.
@@ -11,11 +11,11 @@ Ask the agent to suggest focused product improvements, turn those ideas into Git
 In this lesson, you will:
 
 - create three focused issues for the Space Quiz.
-- browse the issues in **My work**.
+- browse your backlog in **Issues**.
 - start a session from an issue in a new worktree.
 - review the diff in the **Changes** tab and verify the feature.
 
-## Build a backlog in My work
+## Build a backlog in Issues
 
 Send the following prompt:
 
@@ -23,15 +23,15 @@ Send the following prompt:
 Review the space quiz and suggest three focused feature ideas that could each be completed in a short session. Create a separate GitHub issue for each idea with a clear title, user-focused description, and acceptance criteria. Do not implement them yet.
 ```
 
-Open **My work**, review the three issues, and choose one that has clear value and a manageable scope.
+Open **Issues**, review the three issues, and choose one that has clear value and a manageable scope.
 
-![Illustration of the Copilot app My work view. The sidebar lists New, My work, Automations, Customize, and the space-quiz project. The main area has All, Active, Review requests, and Done filters above a list of pull requests.](../../_images/first-steps-app-my-work.svg)
+![Illustration of the Copilot app Issues view. The sidebar lists New, Pull requests, Issues, Automations, Customize, More, and the space-quiz project. The main area has Assigned to me, Created by me, Mentioning me, and Done tabs, a search box, State and Assignee filters, and a list of three open issues in the space-quiz repository.](../../_images/first-steps-app-issues.svg)
 
-**My work** pulls your GitHub issues and pull requests into the app, filtered by **All**, **Active**, **Review requests**, and **Done**.
+**Issues** pulls your GitHub issues from every repository into the app, filtered by **Assigned to me**, **Created by me**, **Mentioning me**, and **Done**. If the new issues are not listed under **Assigned to me**, select **Created by me**.
 
 ## Implement an issue
 
-1. Open the selected issue in **My work**.
+1. Open the selected issue from **Issues**.
 2. Select **New session**.
 3. Choose a **new worktree** when prompted.
 4. Use **Interactive** mode and your preferred model.
diff --git a/docs/first-steps/copilot-app/7-plan-mode.md b/docs/first-steps/copilot-app/7-plan-mode.md
index 1a9fd983..c7ec90ba 100644
--- a/docs/first-steps/copilot-app/7-plan-mode.md
+++ b/docs/first-steps/copilot-app/7-plan-mode.md
@@ -3,7 +3,7 @@ title: "Lesson 7 - Plan before you edit"
 description: "Use Plan mode on a second issue so the agent researches the project and proposes an approach before it changes any files."
 authors:
   - jamesmontemagno
-lastUpdated: 2026-09-28
+lastUpdated: 2026-10-05
 ---
 
 Not every issue should start with edits. Plan mode researches the project, proposes an approach, and waits for your approval before any code changes.
@@ -16,7 +16,7 @@ In this lesson, you will:
 
 ## Agree on the approach before any code changes
 
-1. Open a **second issue** from **My work** and select **New session**.
+1. Open a **second issue** from **Issues** and select **New session**.
 2. In the session configuration, choose **Plan** instead of **Interactive** or **Autopilot**.
 3. Send the following prompt and let the agent investigate without changing files:
 

From 2339508304e05a856820d3b05069485b12e49264 Mon Sep 17 00:00:00 2001
From: James Montemagno <james.montemagno@gmail.com>
Date: Mon, 5 Oct 2026 10:06:52 -0700
Subject: [PATCH 2/6] docs: clarify that /remote keeps app sessions running
 locally

Sync the Copilot app first steps workshop with upstream jamesmontemagno/first-steps-with-github-copilot#10. /remote makes a local session available on the web and in the GitHub Copilot mobile app; it does not move execution to the cloud, and the machine must stay on.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
---
 docs/first-steps/copilot-app/10-remote.md | 18 +++++++++---------
 docs/first-steps/copilot-app/12-review.md |  6 +++---
 docs/first-steps/copilot-app/README.md    |  4 ++--
 3 files changed, 14 insertions(+), 14 deletions(-)

diff --git a/docs/first-steps/copilot-app/10-remote.md b/docs/first-steps/copilot-app/10-remote.md
index aea857dc..e58309cd 100644
--- a/docs/first-steps/copilot-app/10-remote.md
+++ b/docs/first-steps/copilot-app/10-remote.md
@@ -1,33 +1,33 @@
 ---
 title: "Lesson 10 - Continue a session remotely (optional)"
-description: "Use /remote to continue an in-progress app session on GitHub and follow it from any device."
+description: "Use /remote to follow an in-progress app session on the web or in the GitHub Copilot mobile app while it keeps running on your machine."
 authors:
   - jamesmontemagno
-lastUpdated: 2026-09-28
+lastUpdated: 2026-10-05
 ---
 
-This lesson is optional, and worth saving until the local loop feels natural. The `/remote` command continues the session you are already in on GitHub, so you can step away from your machine and keep following it.
+This lesson is optional, and worth saving until the local loop feels natural. The `/remote` command keeps the session running locally while making it available on the web and in the GitHub Copilot mobile app. Your machine needs to stay on while you follow the session from another device.
 
 In this lesson, you will:
 
-- continue an in-progress session remotely.
-- follow the remote session from your browser.
+- make an in-progress session available remotely.
+- follow the session from your browser or the GitHub Copilot mobile app.
 - review the resulting changes like any other pull request.
 
 ## Continue a session remotely
 
 1. Open a session that has work in progress.
-2. Run `/remote` to continue that session remotely.
-3. Select the link it returns to open the remote session in your browser.
+2. Run `/remote` to make that session available remotely.
+3. Open the link it returns in your browser, or access the session in the GitHub Copilot mobile app.
 4. Follow its progress from there, then review the changes exactly as you would any other pull request.
 
 > [!NOTE]
 > **This is not delegation**
 >
-> You are not handing the task to a different agent. It is the same session, continuing somewhere you can reach from any device.
+> The session still runs on your machine. You are not handing the task to a different agent or moving it to the cloud.
 
 ## Summary and next steps
 
-You continued a session beyond your local machine. Continue to [Lesson 11: Explore a Canvas][next-lesson].
+You made a local session available from another device. Continue to [Lesson 11: Explore a Canvas][next-lesson].
 
 [next-lesson]: ../11-canvas/
diff --git a/docs/first-steps/copilot-app/12-review.md b/docs/first-steps/copilot-app/12-review.md
index 5c82a6cc..0c1a2d5c 100644
--- a/docs/first-steps/copilot-app/12-review.md
+++ b/docs/first-steps/copilot-app/12-review.md
@@ -3,10 +3,10 @@ title: "Lesson 12 - Review and next steps"
 description: "Review the GitHub Copilot app workflow and find resources for continued learning."
 authors:
   - jamesmontemagno
-lastUpdated: 2026-09-28
+lastUpdated: 2026-10-05
 ---
 
-You directed an agent through a complete development workflow, from an empty folder to planned work, an isolated implementation, code review, automation, a remote session, and a visual Canvas.
+You directed an agent through a complete development workflow, from an empty folder to planned work, an isolated implementation, code review, automation, remote access to a session, and a visual Canvas.
 
 ## What you completed
 
@@ -22,7 +22,7 @@ You:
 - planned a second issue before any code changed.
 - shipped an issue through pull request review and Agent Merge.
 - automated weekly issue triage.
-- continued a session remotely.
+- followed a local session remotely.
 - explored a shared Kanban Canvas.
 
 ## Keep exploring
diff --git a/docs/first-steps/copilot-app/README.md b/docs/first-steps/copilot-app/README.md
index e8d83e36..97ddebb7 100644
--- a/docs/first-steps/copilot-app/README.md
+++ b/docs/first-steps/copilot-app/README.md
@@ -4,7 +4,7 @@ description: "Take a guided tour of the GitHub Copilot app by building and shipp
 slug: first-steps/copilot-app
 authors:
   - jamesmontemagno
-lastUpdated: 2026-09-28
+lastUpdated: 2026-10-05
 ---
 
 Take a beginner-friendly, hands-on tour of the GitHub Copilot app. You will build a colorful Space Quiz from an empty folder and take it through the complete development loop, from your first prompt to a reviewed pull request.
@@ -28,7 +28,7 @@ The workshop takes approximately 60 to 90 minutes. Your project uses a single HT
 | [7. Plan before you edit][lesson-7] | Plan | Use Plan mode to agree on an approach for a second issue |
 | [8. Complete the review loop][lesson-8] | Review | Open a pull request, address Copilot review feedback, and use Agent Merge |
 | [9. Automate issue triage][lesson-9] | Automate | Schedule and run a weekly issue-triage automation |
-| [10. Continue a session remotely][lesson-10] | Remote (optional) | Continue an in-progress session on GitHub with `/remote` |
+| [10. Continue a session remotely][lesson-10] | Remote (optional) | Follow an in-progress local session from the web or mobile with `/remote` |
 | [11. Explore a Canvas][lesson-11] | Canvas | Start work from a Repository Issues Kanban Canvas |
 | [12. Review and next steps][lesson-12] | Review | Recap the workflow and continue learning |
 

From f07222387d41a3a1c6519138b8b4f8f5afdcb679 Mon Sep 17 00:00:00 2001
From: James Montemagno <james.montemagno@gmail.com>
Date: Mon, 5 Oct 2026 10:34:46 -0700
Subject: [PATCH 3/6] docs: clarify /remote and plan access in CLI and VS Code
 first steps

Port the CLI and VS Code parts of upstream jamesmontemagno/first-steps-with-github-copilot#10. The CLI lesson now says /remote keeps the session running locally and the machine must stay on, and no longer suggests closing the laptop. The CLI delegate and VS Code cloud session lessons note that they need an eligible paid Copilot plan.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
---
 .../first-steps/copilot-cli/7-resume-and-remote.md | 14 +++++++-------
 docs/first-steps/copilot-cli/9-delegate.md         |  5 ++++-
 docs/first-steps/copilot-cli/README.md             |  4 ++--
 docs/first-steps/vscode/9-cloud-session.md         |  5 ++++-
 4 files changed, 17 insertions(+), 11 deletions(-)

diff --git a/docs/first-steps/copilot-cli/7-resume-and-remote.md b/docs/first-steps/copilot-cli/7-resume-and-remote.md
index 4a1daa6f..e3249165 100644
--- a/docs/first-steps/copilot-cli/7-resume-and-remote.md
+++ b/docs/first-steps/copilot-cli/7-resume-and-remote.md
@@ -1,18 +1,18 @@
 ---
 title: "Lesson 7 - Resume and go remote"
-description: "Leave a Copilot CLI session and come back to it later with copilot --resume or /resume, and optionally continue it on GitHub with /remote."
+description: "Leave a Copilot CLI session and come back to it later with copilot --resume or /resume, and optionally follow it from another device with /remote."
 authors:
   - jamesmontemagno
-lastUpdated: 2026-09-28
+lastUpdated: 2026-10-05
 ---
 
-Sessions can be paused without losing their conversation or workspace context. Leave a session, return to it later, and optionally continue it somewhere you can reach from any device.
+Sessions can be paused without losing their conversation or workspace context. Leave a session, return to it later, and optionally make it available from another device.
 
 In this lesson, you will:
 
 - exit a session and resume it from the terminal.
 - switch between sessions without leaving the CLI.
-- optionally continue a session remotely.
+- optionally make a session available remotely.
 
 ## Leave a session and come back later
 
@@ -23,13 +23,13 @@ In this lesson, you will:
 
 ## Optional: Continue a session remotely
 
-Suppose you are deep in one of these sessions and want to keep it going after you close your laptop. Run `/remote` to continue *that same session* on GitHub, then select the link it returns to open and browse the session in your browser.
+Run `/remote` to keep *that same session* running locally while making it available on the web and in the GitHub Copilot mobile app. Your machine needs to stay on. Open the link it returns in your browser, or access the session in the GitHub Copilot mobile app.
 
 > [!NOTE]
-> `/remote` is not delegation, and it is not required for this workshop. Try it once the local loop feels natural.
+> `/remote` is not delegation and does not move execution to the cloud. It is not required for this workshop, so try it once the local loop feels natural.
 
 ## Summary and next steps
 
-You can pause, resume, and continue sessions wherever you work. Continue to [Lesson 8: Create, review, and merge from the CLI][next-lesson].
+You can pause and resume sessions, and follow a local session from another device. Continue to [Lesson 8: Create, review, and merge from the CLI][next-lesson].
 
 [next-lesson]: ../8-pull-request/
diff --git a/docs/first-steps/copilot-cli/9-delegate.md b/docs/first-steps/copilot-cli/9-delegate.md
index 90f41528..f3f918b9 100644
--- a/docs/first-steps/copilot-cli/9-delegate.md
+++ b/docs/first-steps/copilot-cli/9-delegate.md
@@ -3,7 +3,7 @@ title: "Lesson 9 - Delegate work once you trust the loop"
 description: "Hand a new Space Quiz feature to /delegate, keep working while it runs, and follow a cloud session from the CLI."
 authors:
   - jamesmontemagno
-lastUpdated: 2026-09-28
+lastUpdated: 2026-10-05
 ---
 
 You have shipped a feature. Now that you know what good output looks like, a whole new idea is worth running beside you rather than in front of you. In this lesson, you delegate a **shareable mission report** that turns a finished run into a card the player can post.
@@ -14,6 +14,9 @@ In this lesson, you will:
 - keep working in your primary session while the delegated work runs.
 - compare the delegated result before accepting it.
 
+> [!NOTE]
+> `/delegate` and cloud sessions require an eligible paid Copilot plan. Business and Enterprise access may also need to be enabled by an administrator.
+
 ## Delegate a new feature
 
 Run `/delegate` and hand over the following task:
diff --git a/docs/first-steps/copilot-cli/README.md b/docs/first-steps/copilot-cli/README.md
index 70bba804..0a71bcf1 100644
--- a/docs/first-steps/copilot-cli/README.md
+++ b/docs/first-steps/copilot-cli/README.md
@@ -4,7 +4,7 @@ description: "Take a guided, terminal-first tour of GitHub Copilot CLI by buildi
 slug: first-steps/copilot-cli
 authors:
   - jamesmontemagno
-lastUpdated: 2026-09-28
+lastUpdated: 2026-10-05
 ---
 
 Take a beginner-friendly, hands-on tour of GitHub Copilot CLI. You will build a colorful Space Quiz from an empty folder and learn the terminal-first loop: build and review diffs before Git writes anything, run sessions side by side, plan before you edit, then create and merge the pull request without leaving your shell.
@@ -25,7 +25,7 @@ The workshop takes approximately 60 to 90 minutes. Your project uses a single HT
 | [4. Work on issues in parallel][lesson-4] | Implement | Create a backlog, add an issue to chat, review with `/diff`, and start a second session in a worktree |
 | [5. Plan before you edit][lesson-5] | Plan | Use `/plan` to agree on an approach for the second issue |
 | [6. Know what the agent can see][lesson-6] | Context | Inspect and reset context with `/context` and `/clear` |
-| [7. Resume and go remote][lesson-7] | Resume | Leave and return to sessions with `/resume`, and optionally continue with `/remote` |
+| [7. Resume and go remote][lesson-7] | Resume | Leave and return to sessions with `/resume`, and optionally follow a local session from another device with `/remote` |
 | [8. Create, review, and merge][lesson-8] | Review | Create and merge a pull request with `/pr create` and `/pr agentmerge` |
 | [9. Delegate work][lesson-9] | Delegate | Hand a new feature to `/delegate` and follow a cloud session |
 | [10. Review and next steps][lesson-10] | Review | Recap the workflow and continue learning |
diff --git a/docs/first-steps/vscode/9-cloud-session.md b/docs/first-steps/vscode/9-cloud-session.md
index 5ce23bc3..0f1e099b 100644
--- a/docs/first-steps/vscode/9-cloud-session.md
+++ b/docs/first-steps/vscode/9-cloud-session.md
@@ -3,7 +3,7 @@ title: "Lesson 9 - Hand the next idea to a cloud session"
 description: "Switch the Copilot Chat harness from Local to Cloud and delegate a self-contained feature that arrives as a pull request."
 authors:
   - jamesmontemagno
-lastUpdated: 2026-09-28
+lastUpdated: 2026-10-05
 ---
 
 You have done the whole loop locally, so you now know what good output looks like. That is the right moment to let something run without you. Copilot Chat can switch the harness it runs on from your machine to GitHub.
@@ -14,6 +14,9 @@ In this lesson, you will:
 - delegate a self-contained feature with clear acceptance criteria.
 - review the resulting pull request.
 
+> [!NOTE]
+> Cloud sessions require an eligible paid Copilot plan. Business and Enterprise access may also need to be enabled by an administrator.
+
 ## Delegate to the cloud
 
 ![Illustration of Copilot Chat in VS Code with the Harness picker open. Under Copilot, Cloud is selected instead of Local, and other harnesses such as Claude and Codex are listed. Above, a request to add three new color themes shows Working in the cloud with a link to follow the session on GitHub.](../../_images/first-steps-vscode-cloud-harness.svg)

From 973e30a917242225c9bca63b406e876bd4eeecb3 Mon Sep 17 00:00:00 2001
From: James Montemagno <james.montemagno@gmail.com>
Date: Mon, 5 Oct 2026 10:34:47 -0700
Subject: [PATCH 4/6] docs: spell out account and plan steps in first steps
 prerequisites

Sync all three first steps workshops with upstream jamesmontemagno/first-steps-with-github-copilot@db820cd. The prerequisites now link to GitHub signup, name Copilot Free or a paid plan, and tell learners to use organization-provided access where they have it.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
---
 docs/first-steps/copilot-app/0-prerequisites.md | 4 +++-
 docs/first-steps/copilot-cli/0-prerequisites.md | 6 ++++--
 docs/first-steps/vscode/0-prerequisites.md      | 6 ++++--
 3 files changed, 11 insertions(+), 5 deletions(-)

diff --git a/docs/first-steps/copilot-app/0-prerequisites.md b/docs/first-steps/copilot-app/0-prerequisites.md
index f732ed76..50eb3868 100644
--- a/docs/first-steps/copilot-app/0-prerequisites.md
+++ b/docs/first-steps/copilot-app/0-prerequisites.md
@@ -20,7 +20,8 @@ In this lesson, you will:
 
 You need:
 
-- a GitHub account with a [Copilot plan][copilot-plans].
+- a GitHub account. [Create a GitHub account][github-signup], or use your existing account.
+- an active Copilot plan. [Activate Copilot Free or a paid Copilot plan][copilot-plans]. If your organization already provides Copilot access, use that account.
 - a computer running macOS, Windows, or Linux.
 
 The app ships with Git, so there is nothing else to install.
@@ -70,6 +71,7 @@ How does the GitHub Copilot app use worktrees?
 
 You verified the prerequisites, installed the app, chose a model, and explored its main work areas. Continue to [Lesson 1: Create the Space Quiz workspace][next-lesson].
 
+[github-signup]: https://github.com/signup
 [copilot-plans]: https://github.com/features/copilot/plans
 [download-app]: https://gh.io/app
 [active-models]: https://docs.github.com/copilot/reference/copilot-billing/models-and-pricing
diff --git a/docs/first-steps/copilot-cli/0-prerequisites.md b/docs/first-steps/copilot-cli/0-prerequisites.md
index 59073929..f4a0a7ec 100644
--- a/docs/first-steps/copilot-cli/0-prerequisites.md
+++ b/docs/first-steps/copilot-cli/0-prerequisites.md
@@ -3,7 +3,7 @@ title: "Lesson 0 - Prerequisites and setup"
 description: "Verify the workshop prerequisites, install GitHub Copilot CLI, sign in, and choose a model from an empty project folder."
 authors:
   - jamesmontemagno
-lastUpdated: 2026-09-28
+lastUpdated: 2026-10-05
 ---
 
 Put an agent in your terminal. Confirm that you have what you need, install GitHub Copilot CLI, sign in, and get ready to make your first request from an empty folder.
@@ -19,7 +19,8 @@ In this lesson, you will:
 
 You need:
 
-- a GitHub account with a [Copilot plan][copilot-plans].
+- a GitHub account. [Create a GitHub account][github-signup], or use your existing account.
+- an active Copilot plan. [Activate Copilot Free or a paid Copilot plan][copilot-plans]. If your organization already provides Copilot access, use that account.
 - [Git][git] installed. Run `git --version` to verify it.
 - a computer running macOS, Windows, or Linux.
 
@@ -62,6 +63,7 @@ Model availability depends on your plan, organization policy, and product versio
 
 Copilot CLI is installed, signed in, and running in an empty `space-quiz` folder. Continue to [Lesson 1: Build the quiz from the terminal][next-lesson].
 
+[github-signup]: https://github.com/signup
 [copilot-plans]: https://github.com/features/copilot/plans
 [git]: https://git-scm.com/downloads
 [gh-cli]: https://cli.github.com/
diff --git a/docs/first-steps/vscode/0-prerequisites.md b/docs/first-steps/vscode/0-prerequisites.md
index 1cb97420..adf82037 100644
--- a/docs/first-steps/vscode/0-prerequisites.md
+++ b/docs/first-steps/vscode/0-prerequisites.md
@@ -3,7 +3,7 @@ title: "Lesson 0 - Prerequisites and setup"
 description: "Verify the workshop prerequisites, confirm Copilot Chat in VS Code, add the GitHub Pull Requests and Issues extension, and choose a model."
 authors:
   - jamesmontemagno
-lastUpdated: 2026-09-28
+lastUpdated: 2026-10-05
 ---
 
 Bring Copilot into the editor. Copilot ships with VS Code, so there is nothing to install for chat. Add the GitHub extension, then open an empty folder.
@@ -19,7 +19,8 @@ In this lesson, you will:
 
 You need:
 
-- a GitHub account with a [Copilot plan][copilot-plans].
+- a GitHub account. [Create a GitHub account][github-signup], or use your existing account.
+- an active Copilot plan. [Activate Copilot Free or a paid Copilot plan][copilot-plans]. If your organization already provides Copilot access, use that account.
 - [Visual Studio Code][vscode].
 - [Git][git] installed. Run `git --version` in a terminal to verify it.
 
@@ -44,6 +45,7 @@ Model availability depends on your plan, organization policy, and product versio
 
 VS Code is ready with Copilot Chat, the GitHub extension, and an empty `space-quiz` folder. Continue to [Lesson 1: Build in the workspace][next-lesson].
 
+[github-signup]: https://github.com/signup
 [copilot-plans]: https://github.com/features/copilot/plans
 [vscode]: https://code.visualstudio.com/
 [git]: https://git-scm.com/downloads

From bcbf8788669da2d4dc7baeae0ba34a9bedcb8c10 Mon Sep 17 00:00:00 2001
From: James Montemagno <james.montemagno@gmail.com>
Date: Mon, 5 Oct 2026 10:49:54 -0700
Subject: [PATCH 5/6] docs: replace My work with Issues and Pull requests in
 real-world app workshop

The app's My work view is now separate Pull requests and Issues views. Update the workspace overview, the seeded backlog steps, and the issue-linked session steps in lessons 1, 3, and the Foundry module, in English and the five translations.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
---
 .../app/1-install-copilot-app.md                      | 11 ++++++-----
 .../es-es/real-world-development/app/3-agent-modes.md |  4 ++--
 .../app/8-foundry-canvas/1-project-and-model.md       |  4 ++--
 .../app/1-install-copilot-app.md                      | 11 ++++++-----
 .../ja-jp/real-world-development/app/3-agent-modes.md |  4 ++--
 .../app/8-foundry-canvas/1-project-and-model.md       |  4 ++--
 .../app/1-install-copilot-app.md                      | 11 ++++++-----
 .../ko-kr/real-world-development/app/3-agent-modes.md |  4 ++--
 .../app/8-foundry-canvas/1-project-and-model.md       |  4 ++--
 .../app/1-install-copilot-app.md                      | 11 ++++++-----
 .../pt-br/real-world-development/app/3-agent-modes.md |  4 ++--
 .../app/8-foundry-canvas/1-project-and-model.md       |  4 ++--
 .../app/1-install-copilot-app.md                      | 11 ++++++-----
 docs/real-world-development/app/3-agent-modes.md      |  4 ++--
 .../app/8-foundry-canvas/1-project-and-model.md       |  4 ++--
 .../app/1-install-copilot-app.md                      | 11 ++++++-----
 .../zh-cn/real-world-development/app/3-agent-modes.md |  4 ++--
 .../app/8-foundry-canvas/1-project-and-model.md       |  4 ++--
 18 files changed, 60 insertions(+), 54 deletions(-)

diff --git a/docs/es-es/real-world-development/app/1-install-copilot-app.md b/docs/es-es/real-world-development/app/1-install-copilot-app.md
index b8f1d453..a79a3d33 100644
--- a/docs/es-es/real-world-development/app/1-install-copilot-app.md
+++ b/docs/es-es/real-world-development/app/1-install-copilot-app.md
@@ -3,7 +3,7 @@ title: "Lección 1 - Instalar la aplicación GitHub Copilot"
 description: "Instala la aplicación GitHub Copilot, conecta el repositorio que has creado a partir de la plantilla, familiarízate con el espacio de trabajo y prueba un chat rápido."
 authors:
   - geektrainer
-lastUpdated: 2026-07-09
+lastUpdated: 2026-10-05
 ---
 
 La [**aplicación GitHub Copilot**][about-copilot-app] es una aplicación de escritorio para el desarrollo dirigido por agentes. Se basa en GitHub Copilot CLI y se integra de forma nativa con GitHub, por lo que los repositorios, las ramas y las canalizaciones de CI funcionan sin configuración adicional. Está diseñada para flujos de trabajo en los que diriges varios agentes en paralelo, cada uno en su propio espacio de trabajo aislado, en lugar de realizar todo el trabajo y automatizar las tareas repetitivas por tu cuenta. Con Node.js instalado y tu copia del proyecto preparada, el siguiente paso es instalar la aplicación y conectar ese repositorio.
@@ -42,7 +42,8 @@ Como cabe esperar, el primer paso para utilizar la aplicación GitHub Copilot es
 Con el proyecto conectado, dedica un momento a conocer el espacio de trabajo. La aplicación organiza todo en varias áreas de la barra lateral:
 
 - **New**: como cabe esperar, aquí puedes iniciar una nueva sesión de chat con Copilot.
-- **My work**: tus incidencias y solicitudes de incorporación de cambios, disponibles mediante la integración nativa con GitHub de la aplicación. Desde aquí puedes examinar y filtrar incidencias y solicitudes de incorporación de cambios, comprobar el estado de CI, iniciar una sesión a partir de una incidencia y revisar solicitudes de incorporación de cambios, todo ello sin salir de la aplicación.
+- **Pull requests**: tus solicitudes de incorporación de cambios, disponibles mediante la integración nativa con GitHub de la aplicación. Desde aquí puedes examinar y filtrar solicitudes de incorporación de cambios, comprobar el estado de CI y revisar solicitudes de incorporación de cambios, todo ello sin salir de la aplicación.
+- **Issues**: tus incidencias, disponibles del mismo modo. Desde aquí puedes examinar y filtrar incidencias e iniciar una sesión a partir de una incidencia.
 - **Automations**: tareas de agente guardadas que se ejecutan según una programación o bajo demanda. Son útiles para gestionar listas de tareas, realizar el mantenimiento periódico del proyecto o delegar otras tareas tediosas. El resumen final enlaza a ellas como siguiente paso, no como otro ejercicio del taller.
 - **Customize**: añade funcionalidades a la aplicación Copilot mediante servidores MCP, plugins, habilidades y otros componentes. Lo utilizarás para configurar MCP de Playwright.
 - **Chats**: conversaciones ligeras para preguntas y lluvias de ideas que no necesitan una rama ni un espacio de trabajo propios. Probarás una al final de esta lección.
@@ -57,7 +58,7 @@ A lo largo del taller, explorarás el espacio de trabajo.
 
 Prácticamente todos los proyectos tienen trabajo pendiente, y Tailspin Toys no es una excepción. Vamos a explorar la lista de incidencias que se generó al crear el repositorio a partir de la plantilla.
 
-1. Selecciona **My work** en la barra lateral.
+1. Selecciona **Issues** en la barra lateral.
 2. Busca estas incidencias por su título en lugar de dar por hecho su número:
 
    - Allow users to filter games by category and publisher
@@ -66,7 +67,7 @@ Prácticamente todos los proyectos tienen trabajo pendiente, y Tailspin Toys no
 3. Selecciona una incidencia para leer sus detalles. Cada incidencia también sirve como punto de partida para una sesión de agente. Partirás de la incidencia de filtrado después de completar un primer cambio rápido.
 
 > [!NOTE]
-> La lista de elementos de **My work** se filtra automáticamente para mostrar solo los elementos de los repositorios que has añadido a la aplicación Copilot. Para ver elementos de trabajo de otros repositorios, añádelos a la aplicación.
+> Las listas de elementos de **Issues** y **Pull requests** se filtran automáticamente para mostrar solo los elementos de los repositorios que has añadido a la aplicación Copilot. Para ver elementos de trabajo de otros repositorios, añádelos a la aplicación.
 
 ## Probar un chat rápido
 
@@ -87,7 +88,7 @@ Has instalado la aplicación GitHub Copilot, conectado el proyecto y explorado e
 
 - instalar la aplicación e iniciar sesión en GitHub.
 - añadir un proyecto desde su repositorio de GitHub.
-- familiarizarte con el espacio de trabajo y localizar la lista de trabajo pendiente inicial en **My work**.
+- familiarizarte con el espacio de trabajo y localizar la lista de trabajo pendiente inicial en **Issues**.
 - utilizar un chat rápido para formular una pregunta breve y desechable.
 
 A continuación, iniciarás tu primera sesión de agente y realizarás el primer cambio en el proyecto: mostrar una valoración por estrellas en las tarjetas de los juegos. Continúa con la [Lección 2 - Añadir valoraciones por estrellas: una mejora rápida][next-lesson].
diff --git a/docs/es-es/real-world-development/app/3-agent-modes.md b/docs/es-es/real-world-development/app/3-agent-modes.md
index 33e830c3..4b70cc22 100644
--- a/docs/es-es/real-world-development/app/3-agent-modes.md
+++ b/docs/es-es/real-world-development/app/3-agent-modes.md
@@ -3,7 +3,7 @@ title: "Lección 3 - Modos de agente: Plan y Autopilot"
 description: "Explora los modos de agente: utiliza Plan para acordar un enfoque, Autopilot para crear el filtrado a partir de una incidencia e Interactive para revisar y verificar el resultado."
 authors:
   - geektrainer
-lastUpdated: 2026-07-13
+lastUpdated: 2026-10-05
 ---
 
 Empezamos añadiendo una pequeña funcionalidad al proyecto. Sin embargo, los cambios más amplios requieren un proceso más sólido. Por suerte, la aplicación GitHub Copilot está diseñada para adaptarse al flujo existente de una organización y garantizar que creamos lo adecuado de la forma correcta. Esta es la primera de varias lecciones en las que seguirás un proceso de desarrollo habitual dirigido por agentes: partirás de una incidencia para generar una funcionalidad, comprobarás que el código es válido y que la funcionalidad se comporta como se espera y, finalmente, la combinarás correctamente con el proyecto.
@@ -56,7 +56,7 @@ Empieza en modo Plan, revisa el plan y, después, utiliza Autopilot para impleme
 
 Antes de empezar, confirma que la PR de valoraciones por estrellas está combinada y que tu rama `main` local está actualizada.
 
-1. Selecciona **My work** y abre **Allow users to filter games by category and publisher**.
+1. Selecciona **Issues** y abre **Allow users to filter games by category and publisher**.
 2. Selecciona **New session** y elige un **new working tree** basado en la rama `main` actualizada.
 
     ![Vista de una incidencia en la aplicación GitHub Copilot con una flecha que señala el botón New session](../../../_images/app-new-session-from-issue.png)
diff --git a/docs/es-es/real-world-development/app/8-foundry-canvas/1-project-and-model.md b/docs/es-es/real-world-development/app/8-foundry-canvas/1-project-and-model.md
index b8d4c76d..e940fa0e 100644
--- a/docs/es-es/real-world-development/app/8-foundry-canvas/1-project-and-model.md
+++ b/docs/es-es/real-world-development/app/8-foundry-canvas/1-project-and-model.md
@@ -3,7 +3,7 @@ title: "Preparar el proyecto y el modelo"
 description: "Exporta el catálogo de Tailspin, crea un proyecto de Foundry y una implementación de modelo, y valídalos en Canvas."
 authors:
   - juliamuiruri4
-lastUpdated: 2026-09-16
+lastUpdated: 2026-10-05
 prev:
   link: /copilot-workshops/es-es/real-world-development/app/8-foundry-canvas/
   label: "Opcional: Incorporar Foundry"
@@ -36,7 +36,7 @@ La configuración conecta la aplicación GitHub Copilot con Azure y mantiene uni
    ![Instalar el complemento Microsoft Foundry](../../../../_images/app-8-install-foundry-plugin.png)
 
 5. En **Customize**, selecciona **Plugins**, busca `azure` o selecciónalo en la lista **Featured** y, después, selecciona **Install** para el complemento Azure.
-6. En la pestaña **My work**, busca y abre la incidencia titulada **Add a Backer Concierge assistant for catalog questions** en el repositorio de Tailspin Toys. Selecciona **New session** para iniciar una sesión vinculada a la incidencia en un worktree nuevo. Conserva este repositorio, esta rama del worktree y esta sesión de la incidencia durante los tres módulos.
+6. Selecciona **Issues** en la barra lateral y, a continuación, busca y abre la incidencia titulada **Add a Backer Concierge assistant for catalog questions** en el repositorio de Tailspin Toys. Selecciona **New session** para iniciar una sesión vinculada a la incidencia en un worktree nuevo. Conserva este repositorio, esta rama del worktree y esta sesión de la incidencia durante los tres módulos.
 7. Escribe `/microsoft-foundry` y, después, `/azure` para confirmar que ambas habilidades están instaladas y disponibles; no envíes ninguna indicación todavía. Si un complemento no aparece de inmediato, reinicia la aplicación, vuelve a esta misma sesión de la incidencia y compruébalo de nuevo.
 
 ## Generar la exportación del catálogo
diff --git a/docs/ja-jp/real-world-development/app/1-install-copilot-app.md b/docs/ja-jp/real-world-development/app/1-install-copilot-app.md
index f60226f3..e7f929d8 100644
--- a/docs/ja-jp/real-world-development/app/1-install-copilot-app.md
+++ b/docs/ja-jp/real-world-development/app/1-install-copilot-app.md
@@ -3,7 +3,7 @@ title: "レッスン 1 - GitHub Copilot app のインストール"
 description: "GitHub Copilot app をインストールし、テンプレートから作成したリポジトリを接続して、ワークスペースを確認し、クイックチャットを試します。"
 authors:
   - geektrainer
-lastUpdated: 2026-07-09
+lastUpdated: 2026-10-05
 ---
 
 [**GitHub Copilot app**][about-copilot-app] は、エージェント主導の開発に使用するデスクトップアプリケーションです。GitHub Copilot CLI を基盤とし、GitHub とネイティブに統合されているため、リポジトリ、ブランチ、CI パイプラインをすぐに利用できます。すべての作業を自分で行うのではなく、複数のエージェントをそれぞれ分離されたワークスペースで並列に指示し、繰り返し発生するタスクを自動化するワークフロー向けに設計されています。Node.js のインストールとプロジェクトのコピーが完了したので、次はアプリをインストールして、そのリポジトリを接続します。
@@ -42,7 +42,8 @@ GitHub Copilot app を使用するには、まずアプリをインストール
 プロジェクトを接続したら、各領域を確認します。アプリのサイドバーは、主に次の領域で構成されています。
 
 - **New** - 名前のとおり、ここから Copilot との新しいチャットセッションを開始できます。
-- **My work** - アプリの GitHub ネイティブ統合を通じて表示される Issue と pull request です。アプリを離れずに、Issue と pull request の参照や絞り込み、CI ステータスの確認、Issue からのセッション開始、pull request のレビューを行えます。
+- **Pull requests** - アプリの GitHub ネイティブ統合を通じて表示される pull request です。アプリを離れずに、pull request の参照や絞り込み、CI ステータスの確認、pull request のレビューを行えます。
+- **Issues** - 同じように表示される Issue です。Issue の参照や絞り込み、Issue からのセッション開始を行えます。
 - **Automations** - スケジュールまたはオンデマンドで実行する、保存済みのエージェントタスクです。やることリストの管理、定期的なプロジェクトの保守、その他の手間のかかる作業を任せるのに役立ちます。振り返りでは次のステップとしてリンクを紹介し、追加の演習にはしません。
 - **Customize** - MCP server、プラグイン、スキルなどのコンポーネントによって、Copilot app に機能を追加します。Playwright MCP の設定に使用します。
 - **Chats** - 独自のブランチやワークスペースを必要としない、質問やブレインストーミング向けの簡易的な会話です。このレッスンの最後に試します。
@@ -57,7 +58,7 @@ GitHub Copilot app を使用するには、まずアプリをインストール
 
 バックログのないプロジェクトはほとんどなく、Tailspin Toys も例外ではありません。テンプレートからリポジトリを作成したときに用意された、現在のバックログを確認しましょう。
 
-1. サイドバーで **My work** を選択します。
+1. サイドバーで **Issues** を選択します。
 2. Issue 番号を決めつけず、次のタイトルで検索します。
 
    - Allow users to filter games by category and publisher
@@ -66,7 +67,7 @@ GitHub Copilot app を使用するには、まずアプリをインストール
 3. Issue を選択して詳細を読みます。各 Issue はエージェントセッションの開始点にもなります。小規模な最初の変更を完了した後、フィルター機能の Issue から作業を開始します。
 
 > [!NOTE]
-> My work の項目一覧は自動的に絞り込まれ、Copilot app に追加したリポジトリの項目だけが表示されます。ほかのリポジトリの作業項目を表示するには、そのリポジトリをアプリに追加してください。
+> **Issues** と **Pull requests** の項目一覧は自動的に絞り込まれ、Copilot app に追加したリポジトリの項目だけが表示されます。ほかのリポジトリの作業項目を表示するには、そのリポジトリをアプリに追加してください。
 
 ## クイックチャットを試す
 
@@ -87,7 +88,7 @@ GitHub Copilot app をインストールし、プロジェクトを接続して
 
 - アプリをインストールして GitHub にサインインする。
 - GitHub リポジトリからプロジェクトを追加する。
-- ワークスペースを確認し、**My work** で用意されたバックログを見つける。
+- ワークスペースを確認し、**Issues** で用意されたバックログを見つける。
 - クイックチャットを使って、その場限りの簡単な質問をする。
 
 次は、最初のエージェントセッションを開始し、ゲームカードに星評価を表示する最初の変更をプロジェクトに加えます。[レッスン 2「星評価の追加で小さな成果を得る」][next-lesson]に進んでください。
diff --git a/docs/ja-jp/real-world-development/app/3-agent-modes.md b/docs/ja-jp/real-world-development/app/3-agent-modes.md
index f743e6ca..46bc6882 100644
--- a/docs/ja-jp/real-world-development/app/3-agent-modes.md
+++ b/docs/ja-jp/real-world-development/app/3-agent-modes.md
@@ -3,7 +3,7 @@ title: "レッスン 3 - エージェントモード: Plan と Autopilot"
 description: "エージェントモードを確認します。Plan でアプローチに合意し、Autopilot で Issue からフィルター機能を構築して、Interactive で結果をレビューおよび検証します。"
 authors:
   - geektrainer
-lastUpdated: 2026-07-13
+lastUpdated: 2026-10-05
 ---
 
 まず、プロジェクトに小さな機能を追加しました。しかし、より大規模な変更には、さらに堅牢なプロセスが必要です。GitHub Copilot app は組織の既存のフローに沿って作業できるように設計されており、適切なものを適切な方法で構築できます。このレッスンから数回にわたり、一般的なエージェント主導の開発プロセスを実践します。Issue を使って新機能を生成するところから始め、コードが有効で機能が期待どおりに動作することを確認し、最終的にプロジェクトへのマージを成功させます。
@@ -56,7 +56,7 @@ Plan モードで開始し、計画をレビューしてから、Autopilot で
 
 開始前に、星評価の PR がマージされ、ローカルの `main` が最新であることを確認します。
 
-1. **My work** を選択し、**Allow users to filter games by category and publisher** を開きます。
+1. **Issues** を選択し、**Allow users to filter games by category and publisher** を開きます。
 2. **New session** を選択し、更新済みの `main` に基づく **new working tree** を選びます。
 
     ![GitHub Copilot app の Issue ビューで、New session ボタンを矢印で示した画面](../../../_images/app-new-session-from-issue.png)
diff --git a/docs/ja-jp/real-world-development/app/8-foundry-canvas/1-project-and-model.md b/docs/ja-jp/real-world-development/app/8-foundry-canvas/1-project-and-model.md
index f49234c3..526497d8 100644
--- a/docs/ja-jp/real-world-development/app/8-foundry-canvas/1-project-and-model.md
+++ b/docs/ja-jp/real-world-development/app/8-foundry-canvas/1-project-and-model.md
@@ -3,7 +3,7 @@ title: "プロジェクトとモデルを準備する"
 description: "Tailspin のカタログをエクスポートし、Foundry プロジェクトとモデルデプロイを作成して、Canvas で検証します。"
 authors:
   - juliamuiruri4
-lastUpdated: 2026-09-16
+lastUpdated: 2026-10-05
 prev:
   link: /copilot-workshops/ja-jp/real-world-development/app/8-foundry-canvas/
   label: "オプション: Foundry を組み込む"
@@ -36,7 +36,7 @@ Tailspin Toys の支援者は、カテゴリやパブリッシャーでゲーム
    ![Microsoft Foundry プラグインのインストール](../../../../_images/app-8-install-foundry-plugin.png)
 
 5. **Customize** で **Plugins** を選択し、`azure` を検索するか、**Featured** 一覧から選択します。次に、Azure プラグインの **Install** を選択します。
-6. **My work** タブで、Tailspin Toys リポジトリの **Add a Backer Concierge assistant for catalog questions** というタイトルの Issue を探して開きます。**New session** を選択し、新しい worktree で Issue にリンクされたセッションを開始します。3 つのモジュールすべてで、このリポジトリ、worktree ブランチ、Issue セッションを使い続けてください。
+6. サイドバーで **Issues** を選択し、Tailspin Toys リポジトリの **Add a Backer Concierge assistant for catalog questions** というタイトルの Issue を探して開きます。**New session** を選択し、新しい worktree で Issue にリンクされたセッションを開始します。3 つのモジュールすべてで、このリポジトリ、worktree ブランチ、Issue セッションを使い続けてください。
 7. `/microsoft-foundry`、続いて `/azure` と入力し、両方のスキルがインストールされ、利用可能であることを確認します。まだプロンプトは送信しないでください。プラグインがすぐに表示されない場合は、アプリを再起動し、同じ Issue セッションに戻って再確認します。
 
 ## カタログをエクスポートする
diff --git a/docs/ko-kr/real-world-development/app/1-install-copilot-app.md b/docs/ko-kr/real-world-development/app/1-install-copilot-app.md
index e50f6fc5..f928917a 100644
--- a/docs/ko-kr/real-world-development/app/1-install-copilot-app.md
+++ b/docs/ko-kr/real-world-development/app/1-install-copilot-app.md
@@ -3,7 +3,7 @@ title: "레슨 1 - GitHub Copilot app 설치"
 description: "GitHub Copilot app을 설치하고, 템플릿에서 만든 리포지토리를 연결하고, 워크스페이스를 살펴보고, 빠른 채팅을 사용해 봅니다."
 authors:
   - geektrainer
-lastUpdated: 2026-07-09
+lastUpdated: 2026-10-05
 ---
 
 [**GitHub Copilot app**][about-copilot-app]은 에이전트 기반 개발을 위한 데스크톱 애플리케이션입니다. GitHub Copilot CLI를 기반으로 하며 GitHub와 기본적으로 통합되어 리포지토리, 브랜치, CI 파이프라인을 바로 사용할 수 있습니다. 모든 작업을 직접 수행하고 반복 작업을 자동화하는 방식 대신, 각자 격리된 워크스페이스에서 여러 에이전트를 병렬로 지시하는 워크플로를 위해 설계되었습니다. Node.js를 설치하고 프로젝트 복사본을 준비했으므로 이제 앱을 설치하고 해당 리포지토리를 연결합니다.
@@ -42,7 +42,8 @@ GitHub Copilot app을 사용하려면 먼저 앱을 설치해야 합니다. Wind
 프로젝트를 연결했으므로 잠시 워크스페이스의 구성을 살펴봅니다. 앱의 사이드바는 몇 가지 영역으로 구성됩니다.
 
 - **New** - 이름에서 알 수 있듯이 여기서 Copilot과 새 채팅 세션을 시작할 수 있습니다.
-- **My work** - 앱의 GitHub 기본 통합을 통해 이슈와 끌어오기 요청을 표시합니다. 앱을 벗어나지 않고 이슈와 끌어오기 요청을 찾아 필터링하고, CI 상태를 확인하고, 이슈에서 세션을 시작하고, 끌어오기 요청을 검토할 수 있습니다.
+- **Pull requests** - 앱의 GitHub 기본 통합을 통해 끌어오기 요청을 표시합니다. 앱을 벗어나지 않고 끌어오기 요청을 찾아 필터링하고, CI 상태를 확인하고, 끌어오기 요청을 검토할 수 있습니다.
+- **Issues** - 같은 방식으로 이슈를 표시합니다. 이슈를 찾아 필터링하고 이슈에서 세션을 시작할 수 있습니다.
 - **Automations** — 일정에 따라 또는 요청 시 실행되는 저장된 에이전트 작업입니다. 할 일 목록 관리, 정기적인 프로젝트 유지 관리, 기타 반복 작업을 맡기는 데 유용합니다. 마무리에서 다음 단계로 링크를 제공하며 추가 워크숍 실습으로 다루지는 않습니다.
 - **Customize** - MCP 서버, 플러그인, 스킬, 기타 구성 요소 형태로 Copilot app에 기능을 추가합니다. Playwright MCP를 구성할 때 사용합니다.
 - **Chats** — 별도의 브랜치나 워크스페이스가 필요하지 않은 질문과 브레인스토밍을 위한 가벼운 대화입니다. 이 레슨의 마지막에서 사용해 봅니다.
@@ -57,7 +58,7 @@ GitHub Copilot app을 사용하려면 먼저 앱을 설치해야 합니다. Wind
 
 백로그가 없는 프로젝트는 거의 없으며 Tailspin Toys도 마찬가지입니다. 템플릿에서 리포지토리를 만들 때 생성된 백로그를 살펴봅니다.
 
-1. 사이드바에서 **My work**를 선택합니다.
+1. 사이드바에서 **Issues**를 선택합니다.
 2. 이슈 번호를 가정하지 말고 다음 제목으로 이슈를 찾습니다.
 
    - Allow users to filter games by category and publisher
@@ -66,7 +67,7 @@ GitHub Copilot app을 사용하려면 먼저 앱을 설치해야 합니다. Wind
 3. 이슈를 선택하여 세부 정보를 읽습니다. 각 이슈는 에이전트 세션을 시작하는 지점이기도 합니다. 먼저 빠른 변경을 완료한 후 필터링 이슈에서 시작합니다.
 
 > [!NOTE]
-> My work의 항목 목록은 Copilot app에 추가한 리포지토리의 항목만 표시하도록 자동으로 필터링됩니다. 다른 리포지토리의 작업 항목을 보려면 해당 리포지토리를 앱에 추가합니다.
+> **Issues**와 **Pull requests**의 항목 목록은 Copilot app에 추가한 리포지토리의 항목만 표시하도록 자동으로 필터링됩니다. 다른 리포지토리의 작업 항목을 보려면 해당 리포지토리를 앱에 추가합니다.
 
 ## 빠른 채팅 사용해 보기
 
@@ -87,7 +88,7 @@ GitHub Copilot app을 설치하고 프로젝트를 연결하고 워크스페이
 
 - 앱을 설치하고 GitHub에 로그인합니다.
 - GitHub 리포지토리에서 프로젝트를 추가합니다.
-- 워크스페이스를 살펴보고 **My work**에서 미리 생성된 백로그를 찾습니다.
+- 워크스페이스를 살펴보고 **Issues**에서 미리 생성된 백로그를 찾습니다.
 - 빠른 채팅을 사용하여 일회성 질문을 합니다.
 
 다음으로 첫 번째 에이전트 세션을 시작하고 프로젝트를 처음으로 변경하여 게임 카드에 별점을 표시합니다. [레슨 2 - 별점 추가로 작은 성과 얻기][next-lesson]를 계속 진행합니다.
diff --git a/docs/ko-kr/real-world-development/app/3-agent-modes.md b/docs/ko-kr/real-world-development/app/3-agent-modes.md
index 727b55a6..bd14d283 100644
--- a/docs/ko-kr/real-world-development/app/3-agent-modes.md
+++ b/docs/ko-kr/real-world-development/app/3-agent-modes.md
@@ -3,7 +3,7 @@ title: "레슨 3 - 에이전트 모드: Plan 및 Autopilot"
 description: "에이전트 모드를 살펴봅니다. Plan으로 접근 방식에 합의하고, Autopilot으로 이슈의 필터링 기능을 구축하고, Interactive로 결과를 검토하고 검증합니다."
 authors:
   - geektrainer
-lastUpdated: 2026-07-13
+lastUpdated: 2026-10-05
 ---
 
 프로젝트에 작은 기능을 추가하는 것으로 시작했습니다. 하지만 더 큰 변경에는 더 견고한 프로세스가 필요합니다. 다행히 GitHub Copilot app은 조직의 기존 흐름에 맞춰 올바른 대상을 올바른 방식으로 구축하도록 설계되어 있습니다. 이 레슨부터 여러 레슨에 걸쳐 일반적인 에이전트 기반 개발 프로세스를 따릅니다. 이슈를 바탕으로 새 기능을 생성하고, 코드가 유효하며 기능이 예상대로 동작하는지 확인한 뒤, 최종적으로 프로젝트에 성공적으로 병합합니다.
@@ -56,7 +56,7 @@ Plan 모드에서 시작하여 계획을 검토한 다음 Autopilot으로 구현
 
 시작하기 전에 별점 PR이 병합되었고 로컬 `main`이 최신 상태인지 확인합니다.
 
-1. **My work**를 선택하고 **Allow users to filter games by category and publisher**를 엽니다.
+1. **Issues**를 선택하고 **Allow users to filter games by category and publisher**를 엽니다.
 2. **New session**을 선택하고 업데이트된 `main`을 기반으로 하는 **new working tree**를 선택합니다.
 
     ![New session 버튼을 화살표로 가리키는 GitHub Copilot app 이슈 보기](../../../_images/app-new-session-from-issue.png)
diff --git a/docs/ko-kr/real-world-development/app/8-foundry-canvas/1-project-and-model.md b/docs/ko-kr/real-world-development/app/8-foundry-canvas/1-project-and-model.md
index 6812143f..71a2db5b 100644
--- a/docs/ko-kr/real-world-development/app/8-foundry-canvas/1-project-and-model.md
+++ b/docs/ko-kr/real-world-development/app/8-foundry-canvas/1-project-and-model.md
@@ -3,7 +3,7 @@ title: "프로젝트와 모델 준비"
 description: "Tailspin 카탈로그를 내보내고, Foundry 프로젝트와 모델 배포를 만든 다음 Canvas에서 검증합니다."
 authors:
   - juliamuiruri4
-lastUpdated: 2026-09-16
+lastUpdated: 2026-10-05
 prev:
   link: /copilot-workshops/ko-kr/real-world-development/app/8-foundry-canvas/
   label: "선택 사항: Foundry 통합"
@@ -36,7 +36,7 @@ Tailspin Toys 후원자는 카테고리와 퍼블리셔로 게임을 필터링
    ![Microsoft Foundry 플러그인 설치](../../../../_images/app-8-install-foundry-plugin.png)
 
 5. **Customize**에서 **Plugins**를 선택하고 `azure`를 검색하거나 **Featured** 목록에서 선택한 다음, Azure 플러그인의 **Install**을 선택합니다.
-6. **My work** 탭에서 Tailspin Toys 리포지토리의 **Add a Backer Concierge assistant for catalog questions** 이슈를 찾아 엽니다. **New session**을 선택하여 새 워크트리(Worktree)에서 이슈에 연결된 세션을 시작합니다. 세 모듈 모두에서 이 리포지토리, 워크트리 브랜치, 이슈 세션을 유지합니다.
+6. 사이드바에서 **Issues**를 선택한 다음 Tailspin Toys 리포지토리의 **Add a Backer Concierge assistant for catalog questions** 이슈를 찾아 엽니다. **New session**을 선택하여 새 워크트리(Worktree)에서 이슈에 연결된 세션을 시작합니다. 세 모듈 모두에서 이 리포지토리, 워크트리 브랜치, 이슈 세션을 유지합니다.
 7. `/microsoft-foundry`를 입력한 다음 `/azure`를 입력하여 두 스킬이 모두 설치되어 사용할 수 있는지 확인합니다. 아직 프롬프트를 보내지는 않습니다. 플러그인이 바로 나타나지 않으면 앱을 다시 시작하고 동일한 이슈 세션으로 돌아와 다시 확인합니다.
 
 ## 카탈로그 내보내기 파일 생성
diff --git a/docs/pt-br/real-world-development/app/1-install-copilot-app.md b/docs/pt-br/real-world-development/app/1-install-copilot-app.md
index 0a501c52..3e634da6 100644
--- a/docs/pt-br/real-world-development/app/1-install-copilot-app.md
+++ b/docs/pt-br/real-world-development/app/1-install-copilot-app.md
@@ -3,7 +3,7 @@ title: "Lição 1 - Instalar o aplicativo GitHub Copilot"
 description: "Instale o aplicativo GitHub Copilot, conecte o repositório criado a partir do modelo, conheça o espaço de trabalho e experimente um chat rápido."
 authors:
   - geektrainer
-lastUpdated: 2026-07-09
+lastUpdated: 2026-10-05
 ---
 
 O [**aplicativo GitHub Copilot**][about-copilot-app] é um aplicativo para desktop voltado ao desenvolvimento orientado por agentes. Ele foi criado com base no GitHub Copilot CLI e tem integração nativa com o GitHub, portanto seus repositórios, branches e pipelines de CI funcionam sem configuração adicional. Ele foi projetado para fluxos de trabalho nos quais você orienta vários agentes em paralelo, cada um em seu espaço de trabalho isolado, em vez de fazer todo o trabalho por conta própria, além de automatizar tarefas repetitivas. Com o Node.js instalado e sua cópia do projeto pronta, a próxima etapa é instalar o aplicativo e conectar esse repositório.
@@ -42,7 +42,8 @@ Como você pode imaginar, a primeira etapa para usar o aplicativo GitHub Copilot
 Com o projeto conectado, reserve um momento para conhecer o espaço de trabalho. O aplicativo organiza tudo em algumas áreas na barra lateral:
 
 - **New**: como você pode imaginar, aqui você pode iniciar uma nova sessão de chat com o Copilot!
-- **My work**: suas issues e pull requests, exibidos por meio da integração nativa com o GitHub. Nessa área, você pode procurar e filtrar issues e pull requests, verificar o status da CI, iniciar uma sessão a partir de uma issue e revisar pull requests sem sair do aplicativo.
+- **Pull requests**: seus pull requests, exibidos por meio da integração nativa com o GitHub. Nessa área, você pode procurar e filtrar pull requests, verificar o status da CI e revisar pull requests sem sair do aplicativo.
+- **Issues**: suas issues, exibidas da mesma forma. Nessa área, você pode procurar e filtrar issues e iniciar uma sessão a partir de uma issue.
 - **Automations**: tarefas de agente salvas que são executadas em uma agenda ou sob demanda. São ótimas para gerenciar listas de tarefas, a manutenção regular do projeto ou outras atividades repetitivas que você queira delegar. O encerramento traz links para elas como próximo passo, não como outro exercício do workshop.
 - **Customize**: adicione recursos e funções ao aplicativo Copilot na forma de servidores MCP, plugins, skills e outros componentes. Você usará essa área para configurar o MCP do Playwright.
 - **Chats**: conversas leves para perguntas e brainstorming que não precisam de branch ou espaço de trabalho próprios. Você experimentará uma ao final desta lição.
@@ -57,7 +58,7 @@ Ao longo do workshop, você explorará o espaço de trabalho!
 
 Provavelmente não existe projeto sem backlog, e o Tailspin Toys não é diferente. Vamos explorar o backlog existente, gerado quando você criou sua cópia a partir do modelo.
 
-1. Selecione **My work** na barra lateral.
+1. Selecione **Issues** na barra lateral.
 2. Encontre estas issues pelo título em vez de presumir seus números:
 
    - Allow users to filter games by category and publisher
@@ -66,7 +67,7 @@ Provavelmente não existe projeto sem backlog, e o Tailspin Toys não é diferen
 3. Selecione uma issue para ler os detalhes. Cada issue também serve como ponto de partida para uma sessão de agente. Você começará pela issue de filtragem depois de concluir uma primeira alteração rápida.
 
 > [!NOTE]
-> A lista de itens em My work é filtrada automaticamente para exibir somente itens dos repositórios adicionados ao aplicativo Copilot. Quer ver itens de trabalho de outros repositórios? Adicione-os ao aplicativo.
+> As listas de itens em **Issues** e **Pull requests** são filtradas automaticamente para exibir somente itens dos repositórios adicionados ao aplicativo Copilot. Quer ver itens de trabalho de outros repositórios? Adicione-os ao aplicativo.
 
 ## Experimentar um chat rápido
 
@@ -87,7 +88,7 @@ Parabéns! Você instalou o aplicativo GitHub Copilot, conectou o projeto e expl
 
 - instalar o aplicativo e entrar no GitHub.
 - adicionar um projeto por meio do repositório do GitHub.
-- conhecer o espaço de trabalho e localizar o backlog criado em **My work**.
+- conhecer o espaço de trabalho e localizar o backlog criado em **Issues**.
 - usar um chat rápido para fazer uma pergunta rápida e descartável.
 
 Em seguida, você [iniciará sua primeira sessão de agente][next-lesson] e a usará para exibir uma avaliação por estrelas nos cards dos jogos.
diff --git a/docs/pt-br/real-world-development/app/3-agent-modes.md b/docs/pt-br/real-world-development/app/3-agent-modes.md
index 82761c3a..37720100 100644
--- a/docs/pt-br/real-world-development/app/3-agent-modes.md
+++ b/docs/pt-br/real-world-development/app/3-agent-modes.md
@@ -3,7 +3,7 @@ title: "Lição 3 - Modos de agente: Plan e Autopilot"
 description: "Explore os modos de agente: use Plan para definir uma abordagem, Autopilot para criar a filtragem a partir de uma issue e Interactive para revisar e verificar o resultado."
 authors:
   - geektrainer
-lastUpdated: 2026-07-13
+lastUpdated: 2026-10-05
 ---
 
 Começamos adicionando um pequeno recurso ao projeto. No entanto, alterações maiores exigem um processo mais robusto. Felizmente, o aplicativo GitHub Copilot foi desenvolvido para trabalhar com o fluxo existente de uma organização, garantindo que as soluções certas sejam criadas da maneira correta. Esta é a primeira de várias lições nas quais você seguirá um processo típico de desenvolvimento orientado por agentes: começará usando uma issue para gerar um novo recurso, garantirá que o código seja válido e que o recurso se comporte como esperado e, por fim, fará o merge dele no projeto.
@@ -56,7 +56,7 @@ Comece no modo Plan, revise o plano e use o Autopilot para implementá-lo.
 
 Confirme que o PR das avaliações por estrelas foi integrado e que a branch `main` local está atualizada antes de começar.
 
-1. Selecione **My work** e abra **Allow users to filter games by category and publisher**.
+1. Selecione **Issues** e abra **Allow users to filter games by category and publisher**.
 2. Selecione **New session** e escolha uma **new working tree** baseada na `main` atualizada.
 
     ![Visualização da issue no aplicativo GitHub Copilot com uma seta apontando para o botão New session](../../../_images/app-new-session-from-issue.png)
diff --git a/docs/pt-br/real-world-development/app/8-foundry-canvas/1-project-and-model.md b/docs/pt-br/real-world-development/app/8-foundry-canvas/1-project-and-model.md
index 4465e733..c3f850c0 100644
--- a/docs/pt-br/real-world-development/app/8-foundry-canvas/1-project-and-model.md
+++ b/docs/pt-br/real-world-development/app/8-foundry-canvas/1-project-and-model.md
@@ -3,7 +3,7 @@ title: "Preparar o projeto e o modelo"
 description: "Exporte o catálogo da Tailspin, crie um projeto do Foundry e uma implantação de modelo e valide ambos no Canvas."
 authors:
   - juliamuiruri4
-lastUpdated: 2026-09-16
+lastUpdated: 2026-10-05
 prev:
   link: /copilot-workshops/pt-br/real-world-development/app/8-foundry-canvas/
   label: "Opcional: Incorporar o Foundry"
@@ -36,7 +36,7 @@ A configuração conecta o aplicativo GitHub Copilot ao Azure e mantém todo o t
    ![Instalar o plugin Microsoft Foundry](../../../../_images/app-8-install-foundry-plugin.png)
 
 5. Em **Customize**, selecione **Plugins**, pesquise por `azure` ou selecione-o na lista **Featured** e selecione **Install** para o plugin Azure.
-6. Na aba **My work**, encontre e abra a issue intitulada **Add a Backer Concierge assistant for catalog questions** no repositório Tailspin Toys. Selecione **New session** para iniciar uma sessão vinculada à issue em um novo worktree. Mantenha este repositório, branch do worktree e sessão da issue nos três módulos.
+6. Selecione **Issues** na barra lateral e, em seguida, encontre e abra a issue intitulada **Add a Backer Concierge assistant for catalog questions** no repositório Tailspin Toys. Selecione **New session** para iniciar uma sessão vinculada à issue em um novo worktree. Mantenha este repositório, branch do worktree e sessão da issue nos três módulos.
 7. Digite `/microsoft-foundry` e depois `/azure` para confirmar que as duas skills estão instaladas e disponíveis; não envie prompts ainda. Se um plugin não aparecer imediatamente, reinicie o aplicativo, volte para esta mesma sessão da issue e verifique novamente.
 
 ## Gerar a exportação do catálogo
diff --git a/docs/real-world-development/app/1-install-copilot-app.md b/docs/real-world-development/app/1-install-copilot-app.md
index deaaec8e..368feeec 100644
--- a/docs/real-world-development/app/1-install-copilot-app.md
+++ b/docs/real-world-development/app/1-install-copilot-app.md
@@ -3,7 +3,7 @@ title: "Lesson 1 - Installing the GitHub Copilot app"
 description: "Install the GitHub Copilot app, connect the repository you created from the template, get oriented in the workspace, and try a quick chat."
 authors:
   - geektrainer
-lastUpdated: 2026-07-09
+lastUpdated: 2026-10-05
 ---
 
 The **[GitHub Copilot app][about-copilot-app]** is a desktop application for agent-driven development. It is built on GitHub Copilot CLI and integrates natively with GitHub, so your repositories, branches, and CI pipelines work out of the box. It's designed for workflows where you direct several agents in parallel — each in its own isolated workspace — rather than doing all of the work yourself, and automating repetitive tasks. With Node.js installed and your copy of the project ready, the next step is to install the app and connect that repository.
@@ -42,7 +42,8 @@ To use the GitHub Copilot app the first step, as you might imagine, is to instal
 With your project connected, take a moment to learn your way around. The app organizes everything into a few areas in the sidebar:
 
 - **New** - like you might expect, you can start a new chat session with Copilot here!
-- **My work** - your issues and pull requests, surfaced through the app's native GitHub integration. From here you can browse and filter issues and pull requests, check CI status, start a session from an issue, and review pull requests — all without leaving the app.
+- **Pull requests** - your pull requests, surfaced through the app's native GitHub integration. From here you can browse and filter pull requests, check CI status, and review pull requests — all without leaving the app.
+- **Issues** - your issues, surfaced the same way. From here you can browse and filter issues and start a session from an issue.
 - **Automations** — saved agent tasks that run on a schedule or on demand. These are great for managing todo lists, regular project maintenance, or other bits of tedium you'd like to offload. The wrap-up links to these as a next step, not another workshop exercise.
 - **Customize** - add features and functions to the Copilot app in the form of MCP servers, plugins, skills, and other components. You'll use it to configure Playwright MCP.
 - **Chats** — lightweight conversations for questions and brainstorming that don't need a branch or workspace of their own. You'll try one at the end of this lesson.
@@ -57,7 +58,7 @@ As you work through the workshop, you'll explore the workspace!
 
 There's likely not a single project without a backlog, and Tailspin Toys isn't any different. Let's explore the backlog that currently exists, which was created when you created your template.
 
-1. Select **My work** in the sidebar.
+1. Select **Issues** in the sidebar.
 2. Find these issues by title rather than assuming their issue numbers:
 
    - Allow users to filter games by category and publisher
@@ -66,7 +67,7 @@ There's likely not a single project without a backlog, and Tailspin Toys isn't a
 3. Select an issue to read its details. Each issue is also a launch point for an agent session. You'll start from the filtering issue after completing a quick first change.
 
 > [!NOTE]
-> The list of items in My work is automatically filtered to only display items from the repositories you've added to Copilot app. Want to see work items from other repos? Add those repos to the app!
+> The lists of items in **Issues** and **Pull requests** are automatically filtered to only display items from the repositories you've added to Copilot app. Want to see work items from other repos? Add those repos to the app!
 
 ## Try a quick chat
 
@@ -87,7 +88,7 @@ Congratulations! You've installed the GitHub Copilot app, connected your project
 
 - install the app and sign in to GitHub.
 - add a project from its GitHub repository.
-- get oriented in the workspace and find your seeded backlog in **My work**.
+- get oriented in the workspace and find your seeded backlog in **Issues**.
 - use a quick chat to ask a fast, throwaway question.
 
 Next, you'll [start your first agent session][next-lesson] and use it to show a star rating on the game cards.
diff --git a/docs/real-world-development/app/3-agent-modes.md b/docs/real-world-development/app/3-agent-modes.md
index c085a459..dc6c1411 100644
--- a/docs/real-world-development/app/3-agent-modes.md
+++ b/docs/real-world-development/app/3-agent-modes.md
@@ -3,7 +3,7 @@ title: "Lesson 3 - Agent modes: Plan and Autopilot"
 description: "Explore agent modes: use Plan to agree on an approach, Autopilot to build filtering from an issue, and Interactive to review and verify the result."
 authors:
   - geektrainer
-lastUpdated: 2026-07-13
+lastUpdated: 2026-10-05
 ---
 
 We started by adding a small feature into our project. But larger changes require a more robust process. Fortunately, the GitHub Copilot app is built to work with an organization's existing flow, ensuring we build the right things the right way. This is the first of several lessons where you will follow a typical agent-driven development process, starting by using an issue to generate a new feature, ensuring the code is valid, the feature behaves as expected, and eventually merged successfully into the project.
@@ -56,7 +56,7 @@ Start in Plan mode, review the plan, then use Autopilot to implement it.
 
 Confirm the star-rating PR is merged and your local `main` is up to date before starting.
 
-1. Select **My work** and open **Allow users to filter games by category and publisher**.
+1. Select **Issues** and open **Allow users to filter games by category and publisher**.
 2. Select **New session** and choose a **new working tree** based on the updated `main`.
 
     ![The issue view in the GitHub Copilot app with an arrow pointing to the New session button](../../_images/app-new-session-from-issue.png)
diff --git a/docs/real-world-development/app/8-foundry-canvas/1-project-and-model.md b/docs/real-world-development/app/8-foundry-canvas/1-project-and-model.md
index f5602b09..4cce2b19 100644
--- a/docs/real-world-development/app/8-foundry-canvas/1-project-and-model.md
+++ b/docs/real-world-development/app/8-foundry-canvas/1-project-and-model.md
@@ -3,7 +3,7 @@ title: "Prepare project and model"
 description: "Export the Tailspin catalog, create a Foundry project and model deployment, and validate them in Canvas."
 authors:
   - juliamuiruri4
-lastUpdated: 2026-09-16
+lastUpdated: 2026-10-05
 prev:
   link: /copilot-workshops/real-world-development/app/8-foundry-canvas/
   label: "Optional: Incorporate Foundry"
@@ -36,7 +36,7 @@ The setup connects the GitHub Copilot app to Azure while keeping all feature wor
    ![Install Microsoft Foundry plugin](../../../_images/app-8-install-foundry-plugin.png)
 
 5. In **Customize**, select **Plugins**, search for `azure` or select it from the **Featured** list, then select **Install** for the Azure plugin.
-6. On the **My work** tab, find and open the issue titled **Add a Backer Concierge assistant for catalog questions** in your Tailspin Toys repository. Select **New session** to start an issue-linked session in a new worktree. Keep this repository, worktree branch, and issue session for all three modules.
+6. Select **Issues** in the sidebar, then find and open the issue titled **Add a Backer Concierge assistant for catalog questions** in your Tailspin Toys repository. Select **New session** to start an issue-linked session in a new worktree. Keep this repository, worktree branch, and issue session for all three modules.
 7. Type `/microsoft-foundry`, then `/azure` to confirm both skills are installed and available; don't send any prompts yet. If a plugin does not appear immediately, restart the app, return to this same issue session, and check again.
 
 ## Generate the catalog export
diff --git a/docs/zh-cn/real-world-development/app/1-install-copilot-app.md b/docs/zh-cn/real-world-development/app/1-install-copilot-app.md
index 3f6125ce..616bdb60 100644
--- a/docs/zh-cn/real-world-development/app/1-install-copilot-app.md
+++ b/docs/zh-cn/real-world-development/app/1-install-copilot-app.md
@@ -3,7 +3,7 @@ title: "第 1 课 - 安装 GitHub Copilot app"
 description: "安装 GitHub Copilot app，连接通过模板创建的存储库，熟悉工作区并尝试快速聊天。"
 authors:
   - geektrainer
-lastUpdated: 2026-07-09
+lastUpdated: 2026-10-05
 ---
 
 [**GitHub Copilot app**][about-copilot-app] 是一款用于智能体驱动开发的桌面应用。它基于 GitHub Copilot CLI 构建，并与 GitHub 原生集成，因此存储库、分支和 CI 管道均可直接使用。它适用于同时指挥多个智能体的工作流：每个智能体都在隔离的工作区中运行，无需手动完成所有工作，还可自动执行重复性任务。安装 Node.js 并准备好项目副本后，下一步是安装应用并连接该存储库。
@@ -42,7 +42,8 @@ lastUpdated: 2026-07-09
 连接项目后，花一点时间熟悉工作区。应用将功能组织在侧边栏的以下几个区域：
 
 - **New**：顾名思义，可以在这里启动与 Copilot 的新聊天会话。
-- **My work**：通过应用与 GitHub 的原生集成显示议题和拉取请求。在这里，无需离开应用即可浏览和筛选议题与拉取请求、检查 CI 状态、从议题启动会话以及审查拉取请求。
+- **Pull requests**：通过应用与 GitHub 的原生集成显示拉取请求。在这里，无需离开应用即可浏览和筛选拉取请求、检查 CI 状态以及审查拉取请求。
+- **Issues**：以同样的方式显示议题。在这里，可以浏览和筛选议题，并从议题启动会话。
 - **Automations**：可按计划或按需运行的已保存智能体任务。适合管理待办事项、定期维护项目，或处理其他重复性工作。总结课程会将其作为后续方向提供链接，而不再添加工作坊练习。
 - **Customize**：通过 MCP 服务器、插件、技能和其他组件，为 Copilot app 添加功能。你将使用它配置 Playwright MCP。
 - **Chats**：适合提问和集思广益的轻量对话，无需单独创建分支或工作区。本课结束时会进行一次快速聊天。
@@ -57,7 +58,7 @@ lastUpdated: 2026-07-09
 
 几乎每个项目都有待办事项，Tailspin Toys 也不例外。下面探索通过模板创建项目时生成的待办事项。
 
-1. 在侧边栏中选择 **My work**。
+1. 在侧边栏中选择 **Issues**。
 2. 按标题查找以下议题，不要假设议题编号：
 
    - Allow users to filter games by category and publisher
@@ -66,7 +67,7 @@ lastUpdated: 2026-07-09
 3. 选择一个议题以阅读详细信息。每个议题也可以作为智能体会话的启动点。完成一项快速的首次更改后，你将从筛选功能议题启动会话。
 
 > [!NOTE]
-> My work 中的项目会自动筛选，仅显示已添加到 Copilot app 的存储库中的项目。要查看其他存储库中的工作项，请将相应存储库添加到应用。
+> **Issues** 和 **Pull requests** 中的项目会自动筛选，仅显示已添加到 Copilot app 的存储库中的项目。要查看其他存储库中的工作项，请将相应存储库添加到应用。
 
 ## 尝试快速聊天
 
@@ -87,7 +88,7 @@ lastUpdated: 2026-07-09
 
 - 安装应用并登录 GitHub。
 - 从 GitHub 存储库添加项目。
-- 熟悉工作区，并在 **My work** 中找到模板创建的待办事项。
+- 熟悉工作区，并在 **Issues** 中找到模板创建的待办事项。
 - 使用快速聊天提出一次性问题。
 
 接下来，你将[启动第一个智能体会话][next-lesson]，并用它在游戏卡片上显示星级评分。
diff --git a/docs/zh-cn/real-world-development/app/3-agent-modes.md b/docs/zh-cn/real-world-development/app/3-agent-modes.md
index 075e5af4..32a3b531 100644
--- a/docs/zh-cn/real-world-development/app/3-agent-modes.md
+++ b/docs/zh-cn/real-world-development/app/3-agent-modes.md
@@ -3,7 +3,7 @@ title: "第 3 课 - 智能体模式：Plan 和 Autopilot"
 description: "探索智能体模式：使用 Plan 确定方案，使用 Autopilot 根据议题构建筛选功能，再使用 Interactive 审查并验证结果。"
 authors:
   - geektrainer
-lastUpdated: 2026-07-13
+lastUpdated: 2026-10-05
 ---
 
 我们先为项目添加了一项小功能，但更复杂的更改需要更完善的流程。GitHub Copilot app 支持组织现有的工作流程，帮助我们用正确的方法构建所需功能。从本课开始，你将通过几节课遵循典型的智能体驱动开发流程：先使用议题生成新功能，确认代码有效且功能行为符合预期，最终将更改成功合并到项目中。
@@ -56,7 +56,7 @@ Tailspin Toys 的游戏目录不断扩大，访客需要按类别和发行商缩
 
 开始前，确认星级评分 PR 已合并，并且本地 `main` 已更新。
 
-1. 选择 **My work**，打开 **Allow users to filter games by category and publisher**。
+1. 选择 **Issues**，打开 **Allow users to filter games by category and publisher**。
 2. 选择 **New session**，再选择基于更新后 `main` 的 **new working tree**。
 
     ![GitHub Copilot app 的议题视图，箭头指向 New session 按钮](../../../_images/app-new-session-from-issue.png)
diff --git a/docs/zh-cn/real-world-development/app/8-foundry-canvas/1-project-and-model.md b/docs/zh-cn/real-world-development/app/8-foundry-canvas/1-project-and-model.md
index a1f3d4d8..7170e0fb 100644
--- a/docs/zh-cn/real-world-development/app/8-foundry-canvas/1-project-and-model.md
+++ b/docs/zh-cn/real-world-development/app/8-foundry-canvas/1-project-and-model.md
@@ -3,7 +3,7 @@ title: "准备项目和模型"
 description: "导出 Tailspin 目录，创建 Foundry 项目和模型部署，并在 Canvas 中验证。"
 authors:
   - juliamuiruri4
-lastUpdated: 2026-09-16
+lastUpdated: 2026-10-05
 prev:
   link: /copilot-workshops/zh-cn/real-world-development/app/8-foundry-canvas/
   label: "可选：集成 Foundry"
@@ -36,7 +36,7 @@ Tailspin Toys 的支持者可以按类别和发行商筛选游戏，但*哪些
    ![安装 Microsoft Foundry 插件](../../../../_images/app-8-install-foundry-plugin.png)
 
 5. 在 **Customize** 中选择 **Plugins**，搜索 `azure` 或从 **Featured** 列表中选择它，然后为 Azure 插件选择 **Install**。
-6. 在 **My work** 选项卡中，找到并打开 Tailspin Toys 存储库中标题为 **Add a Backer Concierge assistant for catalog questions** 的议题。选择 **New session**，在新工作树中启动关联该议题的会话。三个模块均使用此存储库、工作树分支和议题会话。
+6. 在侧边栏中选择 **Issues**，然后找到并打开 Tailspin Toys 存储库中标题为 **Add a Backer Concierge assistant for catalog questions** 的议题。选择 **New session**，在新工作树中启动关联该议题的会话。三个模块均使用此存储库、工作树分支和议题会话。
 7. 输入 `/microsoft-foundry`，然后输入 `/azure`，确认两个技能均已安装且可用；暂时不要发送任何提示词。如果插件未立即出现，请重启应用，返回同一个议题会话并再次检查。
 
 ## 生成目录导出文件

From 51de504c9e1ce65c402691b1f0a4370035792243 Mon Sep 17 00:00:00 2001
From: James Montemagno <james.montemagno@gmail.com>
Date: Mon, 5 Oct 2026 10:49:55 -0700
Subject: [PATCH 6/6] docs: drop the Created by me hint from the app tour

The hint was not in upstream and assumed the default Issues view only lists assigned issues. Unassigned issues appear there, so the hint is not needed.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
---
 docs/first-steps/copilot-app/6-issues-and-sessions.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/first-steps/copilot-app/6-issues-and-sessions.md b/docs/first-steps/copilot-app/6-issues-and-sessions.md
index b40f2454..b4498167 100644
--- a/docs/first-steps/copilot-app/6-issues-and-sessions.md
+++ b/docs/first-steps/copilot-app/6-issues-and-sessions.md
@@ -27,7 +27,7 @@ Open **Issues**, review the three issues, and choose one that has clear value an
 
 ![Illustration of the Copilot app Issues view. The sidebar lists New, Pull requests, Issues, Automations, Customize, More, and the space-quiz project. The main area has Assigned to me, Created by me, Mentioning me, and Done tabs, a search box, State and Assignee filters, and a list of three open issues in the space-quiz repository.](../../_images/first-steps-app-issues.svg)
 
-**Issues** pulls your GitHub issues from every repository into the app, filtered by **Assigned to me**, **Created by me**, **Mentioning me**, and **Done**. If the new issues are not listed under **Assigned to me**, select **Created by me**.
+**Issues** pulls your GitHub issues from every repository into the app, filtered by **Assigned to me**, **Created by me**, **Mentioning me**, and **Done**.
 
 ## Implement an issue