Skip to content

Optional features

The web UI’s optional features can be turned on or off per browser in Settings > Features. A feature that is off is never downloaded: its code loads only when it is enabled. Features that default to on (Plugins, Debug Sheet) load in the background after the page has rendered, and their chunks are fetched alongside the app entry unless this browser turned them off.

  • Choices are stored in this browser’s local storage (omp.features), not in config.json. A change loads or unloads its feature at once, without a reload; the attached session, draft, and open sheets are kept.
  • The panel shows each feature’s size (gzip and raw) and the total you load: the core plus the enabled features. Sizes come from the production build’s feature-sizes.json; development builds do not produce it and show no sizes.
  • A slash command owned by a disabled feature shows a local notice and is never sent to the agent; enable the feature to use it again. A command owned by a feature that is in development, such as /git under Git Review or /plan under Plan Mode, shows a notice saying so, with no way to enable it.
  • Unknown commands and terminal-only commands, such as /collab and /live, show a local notice and are never sent to the agent. /help (also under the keyboard shortcuts) lists the commands available in the browser.
  • Features: Plugins (a Plugins tab in the Extensions dialog, between Skills and MCP; bare /plugins opens it) and Debug are on by default and can be turned off. Analysis mode, Plan Mode (/plan, /plan-review), Git Review (/git, /annotations), Todos (/todo and its subcommands, the editable todo list sheet), and Provider Login (/login, the Login Providers dialog in Settings > Providers, the palette’s Provider login and the empty sidebar’s Sign in button) are in development: they are listed in Settings > Features as “In development” but stay off and cannot be turned on, and their commands show a local notice instead of running. Log in to model providers from the omp terminal UI meanwhile. The todo tool cards still show in the transcript while Todos is in development. If plan mode is already on in a session (started from the terminal), the session bar shows a read-only badge for it. BTW, Goals, Advisor, MCP servers, Skills, and Background Jobs are not features: they are always available. /btw opens one sheet for the question, answer, history, and promote to transcript. /goal and the goal badge open one dialog for the objective, token budget, loops, and Vibe workers. Advisor notes render in the transcript, and the Ctrl+K palette’s Advisor entry opens the Advisor sheet. The Extensions dialog has a Skills tab and an MCP tab, plus a Plugins tab between them while the Plugins feature is on; each tab has its own search and shows the selected item’s detail beside its list. /skills and /mcp open the dialog on their tab, and bare /plugins (or /plugin) opens it on the Plugins tab. /plugins with arguments (list, enable, disable), and bare /plugins while the Plugins feature is off, still go to the agent. A status line above the composer shows the turn’s progress text (the working intent while the agent streams, “Compacting context…” while it compacts) and, while they have items, Subagents, Jobs, Daemons and Todo buttons with their active counts; each opens a condensed popover. The Activities panel (Alt+A, the command palette, or a popover’s popout icon) holds the same sections in full: Subagents (the tree, with each agent’s transcript and steer composer), Jobs (background jobs other than subagents’ task jobs, with Cancel on the session’s own running jobs), Daemons (supervised background processes the session reported, with restart, kill and log) and Todo (the agent’s read-only checklist). A toggle switches between an accordion, where any number of items expand in place, and a detail view that fills the panel with one subagent or job. The panel’s state is saved per workspace, and #/w/<id>[/s/<sessionId>]/activities[/<subagent|job>/<id>] links to it. /jobs still runs the agent’s own /jobs.
  • Plugin status bars: the status lines, line widgets and working message a plugin sets show around the composer. The Plugins tab of the Extensions dialog lists each bar the session shows and each hidden one under Status Bars, with a toggle: off stops showing that bar in this browser while the plugin keeps running. A row names the installed plugin that set the bar, which the session works out from the call stack; a bar set by an extension that is not an installed plugin (for example a file under ~/.omp/agent/extensions/) has no plugin name. Disabling a plugin from the tab takes its bars down in the attached session at once and locks their toggles until it is enabled again, which shows them again; a session that was not attached follows at its next start, when the plugin’s code is no longer loaded. The choice is stored in this browser’s local storage (omp.hiddenStatusBars) by the bar’s own name (status:<key>, widget:<key>, working). Hiding applies only while the Plugins feature is on: with it off, every bar shows.