Subagents: one slider with two handles, Min and Max; 1 is the agent alone
ci / check (push) Failing after 3s
ci / start (push) Failing after 3s

The chip's popover is one range from 1 to the server's cap (subagents.cap, /models
subagents_cap, else 32) with two handles: two range inputs overlaid on one track, the span
filled, aria-labels Min and Max with value text, keyboard as any slider, Min never past Max,
the values said above it ("Min 1 · Max 4") and the two ends under it. "Fewest"/"Most" are
gone. The hint says what the numbers count: the chat's own agent -- 1 is the agent alone, Max 4
is the agent and up to 3 subagents. Untouched on a new chat it still leaves the server's
defaults (1-4, shown). i18n: Min, Max and the new hint in all eight languages. CHANGELOG.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
HomerandClaude Opus 5.5 committed 2026-11-09 18:06:06 +00:00
1 parent ede91887f7
commit 3510582c8f
6 files changed
+184 -96

No files matched your search

+4 -1
View File
@@ -9,7 +9,10 @@ All notable changes to LLeMbas Desktop. The format follows
### Changed
- **Subagents**, by that name everywhere. The chip under the message box says **Subagents** with the
fewest and the most a chat runs, and opens the two fields under those words; it shows where the
least and the most agents a chat runs ("Subagents 1–4"), and opens one slider with two handles,
**Min** and **Max**, from 1 to the server's cap -- Min never passes Max, and both move with the
arrow keys as well. The numbers count the chat's own agent: **1 is the agent alone**, with no
subagents; Max 4 is the agent and up to 3 subagents. The chip shows where the
server offers subagents for the chat (for a new chat, for its model), and the most is the
server's cap. Where the chat's model serves one request at a time, it says that subagents need
another model, on another server, named in the chat. Subagents work on the chat's own model