Skip to content

fix(init): name only detected harnesses on the .agents row - #518

Merged
theCodeDrift merged 1 commit into
mainfrom
fix/agents-row-detected-only
Oct 16, 2026
Merged

theCodeDrift merged 1 commit into
mainfrom
fix/agents-row-detected-only

Conversation

@theCodeDrift

Copy link
Copy Markdown
Member

The init picker's .agents/ row named every harness Taskless knows reads .agents/skills when none was detected, e.g. OpenCode, Codex, Gemini CLI, Crush, and other .agents harnesses (.agents/). That list grows with the catalog.

The row now names only detected harnesses. With none detected it falls back to its catalog label, Agent Skills (.agents/). A single detected harness reads Crush and other .agents harnesses, without the stray comma.

  • wizard/steps/locations.ts: agentsRowLabel filters to detected harnesses and takes the fallback label.
  • openspec/specs/cli-init/spec.md: the requirement now forbids naming an undetected harness; adds a scenario for the no-detection label.
  • Tests updated to match.

The behavior being corrected landed in 80f3934 and is unreleased, so the pending changeset (which already says "labelled with the detected harnesses") needs no edit.

With no .agents harness detected, the row listed every harness Taskless
knows reads .agents/skills, which grows with the catalog. It now names only
detected harnesses and falls back to its catalog label, Agent Skills.
A single detected harness no longer carries a stray comma.
@theCodeDrift
theCodeDrift merged commit 784899c into main Oct 16, 2026
8 checks passed
@theCodeDrift
theCodeDrift deleted the fix/agents-row-detected-only branch October 16, 2026 01:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant