Skip to content

Latest commit

 

History

History
100 lines (67 loc) · 2.43 KB

show.md

File metadata and controls

100 lines (67 loc) · 2.43 KB

duh show

Show a thread with its full debate history.

Synopsis

duh show THREAD_ID

Description

Displays the complete debate history for a consensus thread: every round's proposals, challenges, revisions, and decisions. Useful for understanding how the consensus was reached.

Arguments

Argument Required Description
THREAD_ID Yes Full UUID or prefix (minimum 8 characters).

Prefix matching

You don't need the full 36-character UUID. Any unique prefix works:

duh show a1b2c3d4        # 8-char prefix
duh show a1b2c3d4-e5f6   # Longer prefix

If the prefix matches multiple threads, duh shows the ambiguous matches so you can be more specific.

Examples

Show a thread by prefix:

duh show a1b2c3d4

Output format

Question: What are the trade-offs between PostgreSQL and MySQL for a new SaaS product?
Status: complete
Created: 2026-02-16 14:30

--- Round 1 ---
  [PROPOSER] anthropic:claude-opus-4-6
  PostgreSQL is the stronger choice for most SaaS products...

  [CHALLENGER] openai:gpt-5.2
  I disagree with the blanket PostgreSQL recommendation...

  [REVISER] anthropic:claude-opus-4-6
  The choice depends on your workload pattern...

  Decision (confidence 100%):
  The choice depends on your workload pattern...
  Dissent: [openai:gpt-5.2]: I disagree with...
  Taxonomy: intent=evaluate category=technology genus=database

Each round shows:

  • Contributions by role (PROPOSER, CHALLENGER, REVISER) with model reference
  • Decision with confidence percentage
  • Dissent if any genuine challenges were preserved
  • Taxonomy (when present) with intent, category, and genus fields

Votes

If the thread used the voting protocol, votes are displayed before the round history:

--- Votes ---
  [anthropic:claude-opus-4-6]
  PostgreSQL is the stronger choice...

  [openai:gpt-5.2]
  It depends on your workload...

Outcomes

If feedback has been recorded for the thread's decision, the outcome is displayed at the end:

  Outcome: success - Deployed to production, no issues

Error cases

  • Thread not found: Thread not found: <id>
  • Ambiguous prefix: Lists all matching threads with their IDs and question snippets

Related commands

  • threads -- Find thread IDs to inspect
  • recall -- Search for threads by keyword
  • feedback -- Record an outcome for this thread