You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Added
A Claude Code command whose screen exists only in its own terminal opens there in one
click. The line that says so, under /vim or /privacy-settings, has "Open in Claude
Code". It starts Claude Code on that command in the session's terminal, in place of the shell
until you quit it or go back to the shell. It runs with your own sign-in, in a conversation of
its own, and nothing it shows is sent to the agent. The usage screen has the same button for /usage-credits, where Claude Code buys usage credits and sets their monthly cap. An
action's command still goes to the shell, which is shown again for it.
The coins warn before a limit is reached. Once a usage window is 75% used, as Claude Code
starts to warn, they carry a small yellow triangle, red once a limit is used up, and the bars
in the card and the overview turn yellow and red likewise. Extra usage's bar is grey now, so
that yellow always means a warning.
The coins at the top right of a Claude Code session show your usage as it is now. They
open an overview of the plan's limits, extra usage and what the session spent, with a bar for
each that carries its share, and ask Claude Code for the figures as they open, with nothing
sent to the model and nothing added to the conversation. The context card keeps the figures
last heard, from a turn, the coins or /usage, now with a thin bar under each limit.
Claude Code's own commands do in Swarmed what they do in a terminal./usage, /status, /context, /cost, /memory, /skills, /hooks and /mcp show their screen in the
conversation, with your plan's limits as bars, instead of a block of text or "isn't available
in this environment". /model, /effort and /config ask where the conversation stands and
are set by your answer; /model opus sets it at once. None of them is sent to the model or
interrupts a turn. The list after / says which commands are shown here, which ask here,
and which are not sent, with what to do instead; those cannot wait in the queue either.
Any other command that only opens a screen in Claude Code's terminal, such as /vim, is
said to, instead of "isn't available in this environment" as if the agent had answered. /usage-credits shows your usage and extra usage, and says that credits are bought in the
terminal. /clear, /new and /reset are not sent: Claude Code would forget the
conversation while the session went on showing it, so they point to a new session. /cd
and /add-dir are refused, since a session works in its task's worktree, and so are /remote-control, /teleport and /desktop, which would hand the session elsewhere.
The context window's card shows your extra usage: what is spent beyond your plan this
month, billed at API prices, against the monthly cap you set, and when this session's turns
run on it. When a plan's limit is reached and Claude Code goes on with extra usage, the
conversation says so, once, instead of "Usage limit reached".
The context window's card shows your usage limits and what the session has spent. For
Claude Code, each usage window (5-hour, weekly and the like) with how much is used and when it
resets; for any agent that reports a cost, what the session has spent in all, and whether that
is billed or covered by a subscription. Agents over the Agent Client Protocol report no limits.
Changed
swarmed-core: Core::task_remove and Core::project_remove return what was passed
over (Vec<String>) instead of nothing; Core::session_send and Core::session_message
do Claude Code's own commands themselves instead of sending them; and AgentEvent, AgentCommand and Error have new variants, which a match over them has to cover.
swarmed-core: Core::slash_commands returns each command with what is done with it
(SlashCommand: its name, its kind and a note) instead of only its name.
Removing a task no longer waits for its worktree to be deleted, and only unsaved work stops
it. The worktree is moved aside and deleted in the background; what is not deleted yet, or
could not be, is counted in Settings under what Swarmed takes up. A stop or teardown that
fails or takes over a minute is passed over, and what was passed over is shown afterwards.
The dialog's "Keep it" button is now "Close", and closing it does not stop a removal under
way.
An environment cannot be removed while a task still uses it.
The button that ends a session is the last in the session's header, at the far right, apart
from the ones that carry the session on.
The task panel opens a task in your terminal or editor from two icons beside the one that
hides the panel. Which terminal and editor they open is chosen in Settings, so the panel no
longer has a menu of editors of its own.
The swarm's icons and words are called True swarm and Weak swarm in Settings →
Appearance: True swarm, which a new installation starts in, renames the tree too, and Weak
swarm keeps the plain names there. Nothing else about them changed, and a setting saved
before keeps its choice.
The plain icons and words are called Boring in Settings → Appearance. Nothing else about
them changed, and a setting saved before keeps them.
Fixed
What a program prints as it ends in a session's terminal is no longer lost. On a Mac, the
last lines of one that printed and ended at once could go missing.
What sessions cost is no longer counted many times over. Claude Code reports the
conversation's running total after every turn and keeps it when a session is resumed, but
the costs in Settings, the turn statistics and the context card's "spent here" started it
over at every turn. So they added each turn's whole running total again, and a session that
had spent $1.09 could show $6.47. A total that goes down, as after /clear, still counts whole.
A task whose removal failed halfway can be removed. "Remove anyway" now deletes what is
left of its worktree, where it used to fail every time once git had lost track of it.
Removing a task ends what still runs in its worktree, such as a stack started by hand in
its terminal, before deleting it. Such a stack used to keep running, recreating files as they
were deleted, which made the removal fail.
The button that takes a cloud task off the list shows on hover and asks first. It used to
be invisible, and one click took the task off at once.
A usage warning from Claude Code no longer reads as a limit reached. A window filling up
is said as a warning, with how much of it is used, once rather than after every turn. When a
window resets on another day, the day is given as well as the time.
A stack that would not end when Swarmed quits is found again by the next one, as it
already was after stopping a single stack.