Skip to content

Add --quiet flag to koad-io wrapper — suppress spinners and flashy output for AI sessions #7

@koad

Description

@koad

Problem

The spinner in the gestate command (and likely other commands) is great for human terminals but eats context in Claude Code sessions. Animated output, ANSI escape sequences, and spinner frames get captured as literal characters in the conversation context — noise that crowds out useful signal.

Proposed Solution

Add a --quiet (or -q) flag to the main koad-io wrapper that suppresses:

  • Spinners / progress animations
  • ANSI color codes and escape sequences
  • Any decorative / flashy output

In quiet mode, commands should still emit meaningful status lines (what's happening, what completed, what failed) — just no animation or decoration.

Usage

koad-io --quiet gestate mercury
koad-io -q install nodejs

Or via environment variable so entities can set it once in .env:

KOAD_IO_QUIET=1 koad-io gestate mercury

Why

When Juno or Vulcan run koad-io commands inside a Claude Code session, every spinner frame and escape sequence lands in the context window. The context should be pointed at the work, not at decorative terminal output.

The --quiet flag lets AI sessions stay clean without breaking the human terminal experience.

Acceptance Criteria

  • --quiet / -q flag recognized by the main wrapper before dispatching to subcommands
  • KOAD_IO_QUIET=1 env var as an alternative
  • Spinners suppressed in quiet mode
  • ANSI/color output suppressed in quiet mode
  • Meaningful plain-text status still emitted (start, done, error)
  • Human terminal (no flag) unchanged

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions