COSMO Work Radar

The Azure DevOps work items assigned to you and your pull requests from all your organizations, your GitHub pull requests, and every open item of the projects you watch, in one place in the VS Code side bar.

Features

Views

• Work Items: Organization → Project → Work item; the open items assigned to you ([System.AssignedTo] = @Me). Icon and color by type (Bug, Task, User Story, Feature, Epic…); the description shows state, priority, due date ("overdue" with an orange icon when past) and remaining work; the tooltip shows iteration, tags and the time of the last change. Order: priority (P1 first), then the earliest due date, then the most recently changed; items without priority / due date come last. Work items of watched projects are sorted the same way. Can also be grouped by state, type or iteration (Group By…); this applies to your own work items only.
• Pull Requests: Organization → "Created by me" / "Waiting for my vote" / "Voted by me" → PR; repository, target branch, your vote, draft, merge conflict marker and the age of the PR; the tooltip shows the reviewers' votes. If you created a PR and are also a reviewer, it appears only under "Created by me".
• GitHub Pull Requests (github.com): Owner → "Created by me" / "Review requested" / "Team review requested" / "Reviewed by me" / "Assigned to me" → PR; repository, base branch, your review state, draft, merge conflict marker, age and review decision. Open PRs only, without archived repositories. A PR appears only in the first matching group.
• PRs older than cosmoMyWork.stalePullRequestDays get an orange icon.
• Mentioned (Azure DevOps): work items where you were @mentioned in the last 30 days (Azure DevOps @RecentMentions), inside their project: a project with mentions has two parts, Assigned to me and Mentioned (organization and project rows show both counts as 3 · @2); without mentions the project lists its work items directly. Closed items are shown too, because a mention may still need an answer; the most recently changed comes first and the rows show the assignee. With state / type / iteration grouping they appear in a separate "Mentioned" group. The view's filter and search apply to them. Can be turned off: cosmoMyWork.showMentions.
• Linked items (Azure DevOps): expand a work item to see its linked PRs, and a PR to see its linked work items. They load on expand and are cached until the next refresh.
• Click a work item / PR (or the icon next to the row) to open it in the browser. Context menu: Copy ID, Copy ID and Title, Copy Link, Ask Copilot About This.
• Count badge on every view; the status bar shows the number of work items, of overdue ones (if any) and of PRs waiting for your review (click to open the view). Both count only your own items.
• Notifications after a refresh (can be turned off: cosmoMyWork.notifications): a work item newly assigned to you, a new @mention, a new review request (Azure DevOps and GitHub), a negative vote (Rejected / Waiting for author) on your Azure DevOps PR, and "Changes requested" on your GitHub PR. A single item can be opened with the Open button; several are shown as a summary. Changes are detected against the previous load (at startup, against the last saved state).

Watched projects (Azure DevOps)

At the bottom of the Work Items and Pull Requests views, the Watched projects group shows all open work items and active PRs of the chosen projects, not only yours.

• Add: Watch Project… (in the view's "…" menu, or "+" on the group row) – organization → project → work items / PRs / both. Adding the same project again changes what is shown and keeps its assignee filter.
• Remove: "X" on the project row (or Stop Watching Project).
• Assignee filter per project: the person icon on the project row in the Work Items view (Filter Assignees of Watched Project…). Check whose work items you want to see in that project – e.g. the lead developer who gets the open, unclaimed tasks, or, if you are the lead, your developers. Nothing checked = everyone; unassigned items can be picked as "(Unassigned)". You can also add people who have no open work item yet: Add by e-mail… at the top of the list (several addresses separated by commas) – their items appear as soon as something is assigned to them. The project row shows the setting (assigned: …), and changes apply without reloading. People are stored by e-mail (unique name), so the filter survives display name changes; older name-based entries still match.
• Work items show the assignee, PRs the author; your own PRs are marked "mine".
• At most cosmoMyWork.watchedLimit work items and as many PRs (default: 500) are loaded per project; a cut list is marked "(limit reached)". The highest-priority work items are loaded first (within the same priority, the most recently changed).
• The view's filter and search apply to them. The Copilot tools do not see watched items.

Pool – work anyone can pick up (Azure DevOps)

The Pool group in the Work Items view shows the results of a saved Azure DevOps query – typically the dashboard query listing the tickets assigned to the lead that anyone can take.

• Set up: Set Pool Query… (in the Work Items view's "…" menu). On the dashboard, click the widget title to open the query, then paste its URL (https://dev.azure.com/{org}/{project}/_queries/query/{id}/). The query may span several projects; the rows show the project.
• The query runs as saved, in its own order; cosmoMyWork.excludedStates does not apply to it. At most 500 items are loaded ("(limit reached)"). The group row shows the query name and the count.
• On the group row: open in the browser, set another query, hide it (Hide Pool).
• The view's filter and search apply to it; the badge and the status bar do not count it. There are no notifications about new pool items.

Filter and search

Every view has its own filter and search; they are kept across restarts, the active filter is shown in the view header and can be cleared with Clear Filter.

• Work Items (filter icon): organization, project, state. Everything is checked by default, uncheck what you want to hide. Only the hidden values are stored, so new organizations, projects and states appear automatically. Applies to your own and to watched work items.
• Pull Requests: organization, project; GitHub: owner, repository – here you check what you want to see.
• Search (search icon): every word you type must appear in the title, ID, organization / owner, project, repository, state, type, iteration, tag, assignee, target branch or author (case-insensitive, partial words match).

Refresh and errors

• At startup the last loaded state is shown immediately, marked "(cached)", until fresh data arrives.
• Refresh: automatically every 30 minutes (only while the VS Code window is focused), manually with Refresh All in the view headers (Azure DevOps with organization discovery, plus GitHub). To refresh only one source: Refresh / Refresh GitHub in the view's "…" menu. Header buttons appear on hover by default; workbench.view.alwaysShowHeaderActions keeps them visible. Changing a setting reloads automatically.
• If you have no access to an organization (e.g. conditional access), it is shown with a warning icon and the other organizations still load. Details: Output → COSMO Work Radar.
• On rate limiting (429/503) requests are retried according to Retry-After; 30 s timeout per request; at most 5 organizations load in parallel.

Copilot integration

• Tools (automatically in Agent mode, or referenced with #):
  • #cosmoWorkItems – the work items assigned to you (filterable by organization, project, state, text).
  • #cosmoPullRequests – your Azure DevOps and GitHub PRs by role.
  • #cosmoWorkItem – details of a work item: description, acceptance criteria, repro steps, links, last 10 comments.
  • #cosmoPullRequest – details of a PR: description, reviewers, linked work items / issues.
• @mywork chat participant: questions about your work; /today – prioritized focus list for today, /reviews – reviews waiting for you and your own PRs that need attention.
• Ask Copilot About This (context menu on a work item or PR): opens the chat with a reference to the item; you complete the question.
• The tools are read-only. Azure DevOps / GitHub content is passed to the model as delimited, untrusted data; only your own organizations can be queried.

Installation

Install COSMO Work Radar from the Extensions view (search for gergelygrubits.cosmo-my-work), or from the command line:

code --install-extension gergelygrubits.cosmo-my-work

If you used an earlier VSIX build (internal.cosmo-my-work), uninstall it first: while it is installed, the new extension only shows a warning. Your cosmoMyWork.* settings are kept; the view filters have to be set again.

First sign-in

1. Click the "COSMO Work Radar" icon in the activity bar.
2. Click Sign in and sign in with your work or school Microsoft (Entra) account. No PAT is needed.
3. The extension discovers every organization you are a member of and loads the data. The organization list is cached for 24 hours; Refresh All (or Refresh in the view's "…" menu) always rediscovers it.

If you are signed in to the wrong tenant, set cosmoMyWork.tenantId.

GitHub

In the GitHub Pull Requests view, sign in with Sign in to GitHub (the built-in VS Code GitHub account, repo scope). This is independent of the Microsoft sign-in. The repo scope also grants write access, but GitHub OAuth has no narrower scope for reading PRs of private repositories; the extension only reads. If a GitHub organization restricts OAuth app access (OAuth App access restrictions / SAML SSO), PRs from its private repositories are not shown; a warning is written to Output → COSMO Work Radar, and the organization admin has to allow the VS Code application.

Settings

Known limitations

• Read-only: no state changes or approvals.
• Azure DevOps: PRs where you are a reviewer only through a team/group are not shown (on GitHub, team review requests are shown).
• One tenant at a time.
• GitHub: github.com only (no GitHub Enterprise Server), at most 1000 PRs per category; no linked items in the tree.
• Build / policy / CI status is not shown.
• For watched projects the limit loads work items by priority; the due date only affects the order of the loaded items.

Felépítés