Skip to content

fix(settings): say nothing of a setting Studio no longer has - #46

Merged
ragnorc merged 1 commit into
mainfrom
fix/retired-settings
Nov 1, 2026
Merged

ragnorc merged 1 commit into
mainfrom
fix/retired-settings

Conversation

@aaltshuler

Copy link
Copy Markdown
Contributor

First step of the plan to cut Studio's bloat, following the UX audit.

A key left in settings.json after its setting is removed raises an error toast at every start (document.rs, "is not a setting, so it does nothing"). This adds a list of the settings the plan removes, so a file that still names them reads clean. Their text stays in the file.

Nothing changes yet: every listed setting still exists, so none of them reaches this path until its removal lands. agent.omnigraph_cli is still reported, because only the agent's own settings are listed.

Listed: agent.command, agent.env, agent.ask_before_writes, models, panels, studio.window_style, studio.corner_radius, studio.bottom_dock_layout.

Test

  • cargo test -p studio_settings, with two new tests in document
  • cargo clippy -p studio_settings --all-targets -- -D warnings, cargo fmt --all --check, check-brand.py

🤖 Generated with Claude Code

A key left in `settings.json` after its setting goes raises an error
toast at every start. List the settings about to go (the agent's, model
calls', panel placement, three appearance settings) so a file that still
names them reads clean. Their text stays, as any other key's.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ragnorc
ragnorc merged commit 64fa6a6 into main Nov 1, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants