Show issue comments in the os-backlog CLI #1021

Open
opened 2026-10-16 17:35:19 +00:00 by jared · 0 comments
Owner

Problem

The os-backlog CLI cannot show the comments of an issue. issue-show prints the body and labels but omits comments, and no comments subcommand exists. Triage decisions often live in comments, so an agent that reads a ticket through the CLI misses them.

Observed

During the CRC Phase 1 triage on 2026-10-16, agents had to read ticket comments by calling Backlog::Issues#comments from a Ruby one-liner instead of the CLI.

Reproduce

n/a: missing feature; os-backlog issue-show <n> prints no comments for an issue that has comments.

Origin

  • Trigger: CRC close-out Phase 1 ticket triage (docs/crc/PLAN.md), 2026-10-16
  • Improvised this session: agents called Backlog::Issues#comments from Ruby
  • Chain: agents cannot read comments through the CLI ← issue-show omits comments and no comments subcommand exists ← DESIGN (plugins/os-backlog/lib/backlog CLI)
  • Root candidate: this ticket
  • Where: plugins/os-backlog CLI (issue-show; Backlog::Issues#comments)
  • Session: 27e5820b-26f1-4e3c-aba0-50aba31cb7c4
  • Transcript: /home/jared/.claude/projects/-home-jared-dev-cc-os--claude-worktrees-crc-os-adr-2026-10-04/27e5820b-26f1-4e3c-aba0-50aba31cb7c4.jsonl

VERDICT: CREATE
REASON: Real gap confirmed; backend comments exists; origin chain ends in DESIGN.

## Problem The os-backlog CLI cannot show the comments of an issue. `issue-show` prints the body and labels but omits comments, and no `comments` subcommand exists. Triage decisions often live in comments, so an agent that reads a ticket through the CLI misses them. ## Observed During the CRC Phase 1 triage on 2026-10-16, agents had to read ticket comments by calling `Backlog::Issues#comments` from a Ruby one-liner instead of the CLI. ## Reproduce n/a: missing feature; `os-backlog issue-show <n>` prints no comments for an issue that has comments. ## Origin - Trigger: CRC close-out Phase 1 ticket triage (docs/crc/PLAN.md), 2026-10-16 - Improvised this session: agents called `Backlog::Issues#comments` from Ruby - Chain: agents cannot read comments through the CLI ← `issue-show` omits comments and no `comments` subcommand exists ← DESIGN (plugins/os-backlog/lib/backlog CLI) - Root candidate: this ticket - Where: plugins/os-backlog CLI (`issue-show`; `Backlog::Issues#comments`) - Session: 27e5820b-26f1-4e3c-aba0-50aba31cb7c4 - Transcript: /home/jared/.claude/projects/-home-jared-dev-cc-os--claude-worktrees-crc-os-adr-2026-10-04/27e5820b-26f1-4e3c-aba0-50aba31cb7c4.jsonl VERDICT: CREATE REASON: Real gap confirmed; backend `comments` exists; origin chain ends in DESIGN.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
jared/cc-os#1021
No description provided.