You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: revert --interactive to boolean True/False, update all surfaces
The display simplification changed --interactive to auto/on/off, but
the runtime consumers (selfy.py, media_loop.py, input_handlers.py)
all need a boolean — they gate input processing loops.
Decision: --interactive stays boolean (True/False) for the CLI and
runtime. The 'auto' concept (DM campaigns prompt, generative sims
don't) is handled internally by the simulation layer based on campaign
type, not exposed as a CLI flag value.
Changes:
- cli_parser.py: --interactive back to True/False (removed duplicate)
- cli_utils.py: validate as boolean
- cli.py: convert bool to on/off for sim display layer
- api.py: configure() docstring updated (on/off, not auto)
- display_simplification_plan.md: documented the decision
- test defaults updated
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: docs/plans/display_simplification_plan.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,10 +2,12 @@
2
2
3
3
**Goal:** Replace 4 overlapping output systems and 5+ display flags with two orthogonal flags that control what the user sees and how they interact. Default should be clean narrative with smart interactive behavior.
4
4
5
-
**Status:**Planning
5
+
**Status:**Partially shipped (DisplayTier + sim_logger display system). `--interactive` reverted to boolean True/False — "auto" detection belongs in the simulation layer, not the CLI flag.
6
6
**Priority:** First post-publication UX improvement (v1.0.1)
7
7
**Estimated effort:**~500 LOC across ~15 files
8
8
9
+
> **Decision (2026-04-09):**`--interactive` stays as a boolean (True/False) controlling whether the runtime accepts user input. The "auto" concept (DM campaigns prompt, generative sims don't) is handled by the simulation layer internally based on campaign type — not exposed as a CLI flag value. The `InteractiveMode` enum in `sim_logger.py` still supports auto/on/off for the display system's internal use via `maxim.configure(interactive="on"/"off")`.
0 commit comments