v4.1.0Home

Output grammar

Every fur command follows the same status-symbol grammar. It's strict on purpose — it makes screenshots feel like one product, not a patchwork of CLIs.

Status symbols

[✓]   success step                green
[✗]   failure                     red / coral
[ℹ]   info notice                 blue
[⚠]   warning                     amber
[…]   in progress (animated)      dim
[?]   prompt / confirmation       coral

Always brackets, always monospace-width, always aligned. Never emoji. Never Unicode arrows or decorations in command output.

Timings & subjects

  • Timings in monospace, dimmed: 1.4s, 12ms, 2h 14m.
  • Subjects (package, service, path) in primary text colour, full opacity.
  • Numbers and units aligned where possible (right-aligned in tables).

Spacing

  • Blank line before every $ command prompt (after previous output).
  • Output rows have no blank lines between them — density feels purposeful.
  • Final state markers ([✓] Installed in 1.4s) are followed by exactly one blank line.
  • Dashboard panes use a 1-character padding inside their borders.

Worked example

$ fur install postgres
[…] Resolving package
[✓] Resolved 1 package from official catalog
[…] Downloading 16.4 (8.2 MB)
[✓] Downloaded postgres 16.4
[✓] Installed in 4.1s

$ fur service start postgres
[✓] Service postgres is now active (running)
[ℹ] Listening on 127.0.0.1:5432

$

Why the strictness?

Output grammar is a brand surface. When every screenshot of everyfur command looks the same, the product feels solid — even before users have tried it.