1.3.0

What's new

• Subagent hierarchy — when an agent spawns subagents, they now appear nested under it as an indented tree in the project's submenu, mirroring Solo's own agent view.
• Submenu grouped by kind — each project's processes are now grouped with a divider between them: agents (and their subagents) first, then terminals, then commands, with the optional TODO / scratchpad counts last.
• Tidier counts row — "scratchpads" is shortened to "pads" to keep the row compact (the Show Scratchpads toggle still spells it out in full), and its leading glyph changed to › so it reads as a summary rather than part of the subagent tree.

Subagent lineage is read read-only from Solo's local database (processes.parent_process_id), since Solo's HTTP API doesn't expose it. If that read ever fails, the menu falls back to a flat process list.

Requires Solo 0.8.2+ running with its HTTP API enabled.

1.2.0

What's new

• Stop a running process from the menu — hold ⌥ Option over any running process and its row turns into a ■ Stop button. Clicking it stops that process via Solo's HTTP API and refreshes the menu the moment Solo confirms. A plain click still opens the process in Solo, exactly as before.
• "About Solo Menubar" menu item — a new footer link that opens this project's GitHub repository.

Requires Solo 0.8.2+ running with its HTTP API enabled.

1.1.1

Quitting Solo no longer shows the misleading "Solo HTTP API not enabled — turn it on in Solo settings" message. The plugin previously inferred the API toggle from Solo's discovery file, which Solo removes on clean quit — so a closed Solo looked identical to a disabled API.

Fixed

• The error row now also reads the real HTTP API toggle from Solo's settings database (~/.config/soloterm/solo.db), which survives quitting Solo, and names the actual remedy:
  • Solo not running — open it — the API is enabled, Solo is just closed.
  • Solo HTTP API disabled — turn it on in Solo settings — the toggle really is off.
  • Solo not running — open it and re-enable its HTTP API — both are needed (stale discovery file from a crash, API since turned off).
• The database is opened strictly read-only, so the plugin can never create or repair files in Solo's directory; if it can't answer (missing, locked, or a future Solo renames the setting), the plugin falls back to the previous messages instead of misreporting.

1.1.0

Adapts the plugin to Solo 0.8.2, whose HTTP API moved under /api behind bearer auth — the unauthenticated endpoints this widget previously used are gone, so older plugin versions show "Solo not running" even when Solo is fine.

Now requires Solo 0.8.2 or newer. No setup beyond enabling the HTTP API: the plugin reads the base URL and token from Solo's own discovery file.

Added

• Total project count on the Show all projects (N) toggle.
• Distinct error states instead of one catch-all message: HTTP API not enabled, Solo not running, Solo running but API not responding, and Solo API changed — update this plugin (shown when a future Solo bumps its API contract version, with a link to plugin releases).

Changed

• Projects are labeled by their display name, matching what Solo's own UI shows.
• TODO/scratchpad counts come from the API's totalCount via tiny limit=1 probes, fetched concurrently — faster menu open, less data transferred.
• The menu is built fully before anything is printed, so a mid-refresh failure shows the friendly error row instead of a truncated menu.

Fixed

• Works behind corporate/system HTTP proxies: localhost API calls now bypass proxies entirely, so the auth token never leaves the machine.
• Menu toggles work when the plugin or Python lives in a path containing spaces (e.g. ~/Library/Application Support/...).
• Settings are written atomically — a killed toggle or concurrent refresh can no longer corrupt saved preferences.
• Project/process names starting with -- no longer get swallowed into the previous item's submenu, and non-ASCII names get working deep links.
• API pagination guards against stalled cursors and silent truncation.

1.0.0

Features

• Lists every project with at least one running process; click a project — or any agent/terminal under it — to deep-link straight into Solo.
• A small green donut marks each active project.
• Refreshes the moment you open the menu — no background polling.
• Friendly "Solo not running" state when Solo is closed or its HTTP API is off.

Options

All off by default, remembered between launches.

• Show all projects — also list idle projects (greyed out), so you can jump into one that isn't running yet.
• Show TODOs — show each project's number of open TODOs.
• Show Scratchpads — show each project's number of scratchpads.