Show squad version number in agent label across Copilot hosts #18

Activity

1. bradygaster

   assigned

   Copilot

   and

   bradygaster

   on Feb 11, 2026
2. bradygaster commented on Feb 12, 2026

   

   bradygaster

   on Feb 12, 2026

   CollaboratorAuthor

   More actions

   Kujan — Version Display Investigation & Implementation

   Findings

   What's already in place:

   • squad.agent.md has YAML frontmatter with version: "0.0.0-source" in the source file
   • index.js already stamps the real version (from package.json) into the frontmatter via stampVersion() during both init and upgrade
   • The version is already embedded in every installed agent file — it just wasn't being surfaced to users

   What's controllable:

   • The description field in task tool calls shows in the Copilot UI, but it's per-spawn — not the right place for a persistent version indicator
   • The YAML frontmatter description field shows in the agent picker UI — could work, but mixing version into the agent description feels noisy
   • The coordinator's first response text is the cleanest place — it's visible in every host (CLI, VS Code, GitHub.com)

   Approach Chosen: Coordinator Self-Announcement

   Added a Version line to the Coordinator Identity section in squad.agent.md:

   - **Version:** Read the `version` field from the YAML frontmatter at the top of this file. Include it as `Squad v{version}` in your first response of each session.

   Why this works across all Copilot hosts:

   1. The version is already stamped into the frontmatter during install/upgrade — no new machinery needed
   2. The coordinator reads its own file at session start — the version is right there
   3. The instruction to include it in the first response is simple and reliable
   4. Works identically in CLI, VS Code, and GitHub.com — no host-specific logic
   5. Zero code changes to index.js — the stamping mechanism is already correct

   What the user sees (first response of any session):

   • Init mode: Squad v0.3.0 — Hey Brady, what are you building?
   • Team mode: Squad v0.3.0 — Fenster's on it — refactoring auth module

   Alternatives Considered & Rejected

   1. Injecting version into description frontmatter field — Would show in agent picker but is noisy (Your AI team (v0.3.0)), and the picker UI may truncate it
   2. Runtime version read from package.json — The coordinator can't read package.json at runtime (it's in the npm package, not the user's repo). The stamped frontmatter is the correct mechanism.
   3. Adding version to task tool description field — Per-spawn, not persistent. Would clutter every spawn acknowledgment.

   Implementation

   Single edit to squad.agent.md Coordinator Identity section. All 118 existing tests pass. No changes to index.js needed — the version stamping pipeline was already correct.
3. bradygaster commented on Feb 12, 2026

   

   bradygaster

   on Feb 12, 2026

   CollaboratorAuthor

   More actions

   Resolved in v0.4.0 — added version display to coordinator identity in squad.agent.md. Version is read from frontmatter and shown as 'Squad v{version}' on session start.
4. bradygaster

   closed this as completedon Feb 12, 2026
5. tamirdresher

   added 2 commits that reference this issue on Mar 2, 2026

   fix: apply P0+P1 security audit findings for remote-control

   ...

   9474ce0

   fix: add EISDIR, NaN, stream error, non-JSON PTY, and decodeURI guards

   ...

   c11b484
6. bradygaster

   added a commit that references this issue on Mar 4, 2026

   feat: Squad Remote Control - PTY mirror + devtunnel for phone access (#…

   ...

   4ecc244
7. joniba

   added a commit that references this issue on Mar 26, 2026

   feat: reusable squad template project with generic roles

   ...

   This issue will close once commit 0dbb64f is merged into the 'dev' branch.

   0dbb64f