Repository navigation
Feature Request: Centralize Infrastructure Settings and Improve Configuration UX #136
Description
Summary
The current navigation scatters infrastructure and administration features across multiple areas of the application.
Features such as:
- SSH Hosts
- Remote Access
- Telegram Integration
feel more like application configuration than day-to-day LLM usage and would be easier to discover if grouped under a single Configuration / Administration section.
This would also be a good opportunity to modernize and simplify the entire settings experience.
Current Situation
Today, configuration-related features are spread throughout the UI.
Examples:
Main UI
├─ Projects
├─ Kanban
├─ Schedule
├─ Chat
├─ SSH Hosts
├─ Remote Access
├─ Telegram
└─ ...
As a result:
- Navigation feels cluttered.
- Infrastructure settings are mixed with operational workflows.
- New users may struggle to find configuration options.
- The Settings experience feels fragmented.
Proposed Solution
Move infrastructure and administration features into a centralized configuration area.
Example:
Configuration
├─ General
├─ Models & Providers
├─ Agents
├─ SSH Hosts
├─ Remote Access
├─ Telegram
├─ MCP
├─ Security
├─ Notifications
└─ Advanced
Benefits
Cleaner Main Navigation
Focus the main UI on:
Projects
Kanban
Schedule
Chat
which are the primary day-to-day workflows.
Better Discoverability
Users naturally expect infrastructure-related settings in:
Settings
Configuration
Administration
rather than mixed into the application workspace.
Easier Maintenance
A centralized configuration model makes future features easier to organize.
Additional UX Improvements
Since the Configuration UI would be reorganized, this would be a good opportunity to improve it further.
Full-Screen Settings
Allow the configuration page to use available screen space:
Current Settings Window
↓
Full Settings Workspace
Search
Add:
Search settings...
to quickly find:
- SSH
- Telegram
- Agent
- Model
- MCP
- Turns
- Context
- Quotas
Source Visibility
Clearly display where values come from:
Global Settings
Workspace Settings
config.json
settings.json
.env
Categories
Group settings into logical sections:
AI Providers
Agents
Infrastructure
Notifications
Security
Workspace
Advanced
Advanced / Basic Mode
Support:
Basic Mode
Advanced Mode
to reduce complexity for new users.
Expected Result
The application would have:
- A cleaner main UI.
- A centralized administration experience.
- Better discoverability.
- Reduced navigation complexity.
- A more professional and scalable configuration interface.
Priority
Medium-High
Use Case
As a user, I want SSH Hosts, Remote Access, Telegram, and other infrastructure settings grouped under a dedicated Configuration section so that operational workflows remain focused on Kanban, Chat, and Schedule while all administration settings are managed in a single place.
Activity
Lexus2016 commentedon Nov 10, 2026
Thanks — this one splits cleanly in two, and the first half already ships.
Already in the app today. The Settings dialog is literally titled Configuration, and it
has a search box across every setting, collapsible sections, and content grouped as Models and
engine, New-chat defaults, Agents and run limits, Workspace, MCP / skills / commands,
Server and network, Security, Data storage, Interface and Advanced. So "search
settings", "categories" and an "advanced" area exist; that part of the request is not missing.
Not there. SSH Hosts, Remote Access and Telegram are still their own sections in the right
sidebar; the dialog is a modal rather than a full-screen workspace; nothing tells you where a
value comes from (global settings / workspace /
config.json/.env); and there is noBasic-vs-Advanced switch.
Why I am not landing that as one change. Those three panels are inline sidebar sections
with their own markup, state and handlers, and the sidebar layout is covered by its own tests.
Moving them changes where people click every day, so it deserves an agreed shape rather than a
half-move in a drive-by PR.
The slice I can take now: move SSH Hosts, Remote Access and Telegram into one
Infrastructure section of the Configuration dialog, keeping their markup and handlers intact,
and leave the sidebar to Projects / Kanban / Schedule / Chat. Then, as separate pieces:
full-screen settings, per-value source indicators, and the Basic/Advanced switch.
Tell me which you want first and I will scope it — the Infrastructure move is the smallest and
the one that removes the clutter this issue is really about.
settings: give the Configuration dialog the available screen (#140)
Lexus2016 commentedon Nov 11, 2026
First slice is in: #140, squash
a4482fc0. The Configuration dialog had a fixed 740px width and an 86vh cap, so on a large screen the window stayed mostly empty while the tabs, the search bar and the form were squeezed into a narrow column. It now usesmin(1180px, 96vw)by88dvh. Small screens are unchanged.On the bigger part of the request: SSH Hosts, Remote Access and Telegram are server-backed panels, while the Configuration form is rendered from the config schema. Moving them under one Infrastructure group therefore needs a tab host that can render arbitrary panels — a separate change, not a markup move. I would rather do that once, properly, than reshape the sidebar twice.
Worth knowing about what already exists: search across settings with Escape to clear, collapsible sections with "Collapse all", grouped tabs, and a "form fields save automatically" notice. What is genuinely missing from your list is the source of each value (global / workspace / config.json / .env) and a Basic/Advanced switch.
engine: opt-in idle reaper for subscription tmux sessions (#141) (#142)