Bug Circus Tuned

Turn debugging into a circus performance with dynamic performers, show counters, and audience reactions.

When to Use This Setting

Apply this setting when you need to:

• Add entertainment and personality to long debugging sessions to maintain developer morale
• Track session activity through an incrementing show counter that persists across interactions
• Create a unique team culture element with randomized audience reactions and rotating performer icons Consider alternatives when:
• You prefer a professional statusline focused on technical information like git status and context usage
• Your terminal has limited Unicode support and may not render the emoji-based display correctly

Quick Start

Configuration

Copy
name: bug-circus-tuned
type: setting
category: statusline

Example Application

Copy
claude setting:apply bug-circus-tuned

Example Output

Setting applied. Changes:
- statusLine: Bug Circus performance monitor
- Displays: [Model] Show #N | Performer | Audience | Directory

Core Concepts

Circus Performance Overview

Aspect	Details
Show Counter	Increments with each Claude Code interaction, persisted in /tmp session cache
Performers	Cycles through juggler, drama, circus, artist, and target icons every 5 interactions
Audience	Three audience members randomly display applause (30%) or sleeping (70%) each time
Session Persistence	Show state is stored per session ID in /tmp for continuity across interactions

Performance Engine Architecture

+---------------------------+
|  Interaction Trigger      |
+---------------------------+
         |
         v
+---------------------------+
|  Cache: /tmp/circus_*     |
|  Read show count          |
|  Increment by 1           |
|  Write back               |
+---------------------------+
         |
    +----+----+----+
    |    |    |    |
    v    v    v    v
  Show  Perf  Aud  Dir
  #N    Icon  x3   Name
         |
         v
+---------------------------+
| [Model] Show #42 |        |
| Performer | Audience |     |
| Directory                 |
+---------------------------+

Configuration

Parameter	Type	Default	Description
statusLine.type	string	"command"	Status line type using shell command for dynamic content
statusLine.command	string	N/A	Bash script with jq for JSON parsing and Python for randomization
Performer Cycle	number	5	Number of interactions before the performer icon rotates
Applause Probability	number	0.3	Probability (0-1) of each audience member showing applause
Cache Location	string	"/tmp/circus_*"	Temp directory path for session-persistent show counter

Best Practices

1. Use the show counter to track session productivity - The show counter doubles as an interaction counter. High numbers indicate long sessions where you may want to take breaks or compact context.
2. Customize performer icons for your team - Replace the default performer set with icons that represent your team's interests or inside jokes. This creates team identity around the debugging experience.
3. Monitor audience reactions for morale - While purely random, consistently sleeping audiences during late-night debugging sessions add a humorous meta-commentary that can lighten the mood.
4. Clear the cache between unrelated sessions - The show counter persists in /tmp based on session ID. For completely fresh sessions, the cache creates naturally as each session gets a unique ID.
5. Combine with serious statuslines for balance - Some teams use the circus statusline during development and switch to a professional statusline during demonstrations or screen shares.

Common Issues

1. jq not installed - The statusline command requires jq for JSON parsing. Install it via your package manager (brew install jq, apt install jq) before applying this setting.
2. Python3 not available for randomization - The audience reaction generator uses Python. If Python is not available, the script falls back to a static audience pattern.
3. Cache file permissions in shared environments - The /tmp cache files are created with the current user's permissions. In multi-user systems, each user gets their own session cache naturally through unique session IDs.