the TUI needs to be able to operate on the same preferences as the GUI application. so there needs a new panel and sidebar linked to number 6 to open the preferences editor and when selecting a sidebar entry, a specific editor for that section of the preferences is opened and allows the user to work on preferences there.
the TUI needs to be able to operate on the same preferences as the GUI application. so there needs a new panel and sidebar linked to number 6 to open the preferences editor and when selecting a sidebar entry, a specific editor for that section of the preferences is opened and allows the user to work on preferences there.
hugo
added the idea label 2026-07-15 18:29:02 +00:00
hugo
added the ctritical label 2026-07-16 20:28:26 +00:00
The TUI now has a settings panel on key 6, matching the GUI panel numbering. The sidebar lists the same preference sections as the GUI settings editor (Project, Editor, Content, AI, Technology, Publishing, Data, MCP, Style), and pressing enter on a section opens a section-specific editor in the main area:
enter edits a text field in a status-line prompt, toggles a boolean, or cycles an enum through its options
ctrl+s saves the section through the exact same backends the GUI uses (BDS.Metadata, BDS.Settings, BDS.AI, BDS.MCP.AgentConfig), so both frontends operate on the same preferences
esc cancels the prompt, then closes the editor
The section forms come from a new shared, renderer-agnostic module (BDS.UI.SettingsForm); the AI save pipeline was extracted from the GUI settings editor so both frontends share it. Data is shown read-only (maintenance commands already live under the : prompt), and category removal plus AI model discovery remain GUI-only for now.
Covered by tests (10 new for the shared forms, 4 new TUI panel tests), localized for de/fr/it/es, and the tui.allium spec was extended with a SettingsPanel rule.
Implemented in 505527a and pushed to main.
The TUI now has a settings panel on key **6**, matching the GUI panel numbering. The sidebar lists the same preference sections as the GUI settings editor (Project, Editor, Content, AI, Technology, Publishing, Data, MCP, Style), and pressing enter on a section opens a section-specific editor in the main area:
- **enter** edits a text field in a status-line prompt, toggles a boolean, or cycles an enum through its options
- **ctrl+s** saves the section through the exact same backends the GUI uses (BDS.Metadata, BDS.Settings, BDS.AI, BDS.MCP.AgentConfig), so both frontends operate on the same preferences
- **esc** cancels the prompt, then closes the editor
The section forms come from a new shared, renderer-agnostic module (BDS.UI.SettingsForm); the AI save pipeline was extracted from the GUI settings editor so both frontends share it. Data is shown read-only (maintenance commands already live under the : prompt), and category removal plus AI model discovery remain GUI-only for now.
Covered by tests (10 new for the shared forms, 4 new TUI panel tests), localized for de/fr/it/es, and the tui.allium spec was extended with a SettingsPanel rule.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
the TUI needs to be able to operate on the same preferences as the GUI application. so there needs a new panel and sidebar linked to number 6 to open the preferences editor and when selecting a sidebar entry, a specific editor for that section of the preferences is opened and allows the user to work on preferences there.
Implemented in
505527aand pushed to main.The TUI now has a settings panel on key 6, matching the GUI panel numbering. The sidebar lists the same preference sections as the GUI settings editor (Project, Editor, Content, AI, Technology, Publishing, Data, MCP, Style), and pressing enter on a section opens a section-specific editor in the main area:
The section forms come from a new shared, renderer-agnostic module (BDS.UI.SettingsForm); the AI save pipeline was extracted from the GUI settings editor so both frontends share it. Data is shown read-only (maintenance commands already live under the : prompt), and category removal plus AI model discovery remain GUI-only for now.
Covered by tests (10 new for the shared forms, 4 new TUI panel tests), localized for de/fr/it/es, and the tui.allium spec was extended with a SettingsPanel rule.