show should include comments by default to match the web reading experience #385
Description
When you visit a Basecamp URL on the web, you see the full picture: the content, its comments, and the entire conversation thread. When an agent uses basecamp show <url>, it only gets the recording itself — no comments, no discussion history.
This means agents routinely miss critical context. Bug cards have investigation history in comments. Messages have follow-up decisions. Todos have status updates. The comments ARE the conversation, and right now the CLI silently omits them.
Why this matters for agents
Agents using the CLI as their primary interface to Basecamp don't know what they're missing. There's no cue that comments exist unless they already know to run basecamp comments list <id> as a separate step. A human visiting the same URL on the web would see everything at once.
In practice this leads to:
- Duplicate work (re-discovering things already discussed in comments)
- Missing context that changes the meaning of the card/message
- Extra round-trips to fetch comments after realizing they exist
Suggestion
basecamp show <url> should include comments by default — or at minimum surface them with a --comments flag. The goal is: what you'd read on the web is what you get from the CLI.
The comment_count field is already in the response. If it's > 0, the comments should come along for the ride.
Additionally, the embedded agent skill file could note this pattern — a breadcrumb reminding agents to always pull comments when reading a recording, so they get full context even if the CLI doesn't bundle them automatically yet.