Squad for Mac has the same History and Activity. On the Mac, also open them with Go > History or Go > Activity in the menu bar, and History with History in the menu bar panel’s ⋯ menu. Where the Mac differs, see On Squad for Mac.
Fix work that did not finish
When a teammate’s work did not finish today, Today and Needs you show a card for it, at the top of Needs you. You see these cards if you are the owner or an Administrator.- Each card is for one teammate, however many of its runs failed. An app whose connection expired gets its own card.
- The card says what did not finish, for example “Mara’s reply in chat didn’t finish.” or “Otis’s work didn’t finish 3 times today.”, and why, for example “It ran out of time.” When the runs were one routine’s, the card names the routine. When they stopped for different reasons, it says “They stopped for different reasons.”
- A failed attempt that the teammate’s next attempt in the same turn finished, for example on a model under When it can’t answer, is not counted. See Limits and defaults.
- The sentence on Today counts these cards apart, for example “1 problem needs fixing”.
On Squad for Mac, Set this aside hides the failures on the card until something fails again, so a new failure of the same work can show the card again the same day. A problem that you set aside on the web still shows on the Mac, and the other way around.
When your Claude Code account is signed out, a card at the very top says “Claude Code is signed out, so your squad can’t work.”, with Reconnect and the account’s name. Everyone in your squad sees it. The owner and Administrators read “Reconnect it and your teammates pick up where they left off.” Other people read “[owner] can reconnect it in Settings → AI.” Only the owner and Administrators get Reconnect. The card goes away when the account works again.
When your AI provider limits your squad, the sentence on Today says “[provider] is limiting your squad right now.” See Rate limits and fallback. While the line “Claude Code has reached its usage limit.” shows above every screen, this sentence leaves Claude Code out. See Claude Code reached its usage limit.
Find a run
1
Open History
Press ⌘K, type History, and select it. Or press
R.2
Pick a view
Pick a view: Schedule, Day, Week, or Month. Schedule is the default. It shows the runs of the last 3 days, newest first. Day shows one day. Week shows 7 days. Month shows the current month up to today.
3
Set the filters
Open the Filters panel and choose what to show:
- Teammates: turn teammates on or off.
- Kind: Routines, Chats, Telegram and mentions, Emails, Research, Apps, Tools, Helpers, Triggers. Tools is off until you turn it on.
- Routines: All routines or one routine.
4
Move through the days
Use Earlier, Later, and Today to move through the days. In Week, they move 7 days at a time. Month always shows the current month. In Schedule, select Load older runs to go back further.
S, D, W, or M to change the view, T for today, and the arrow keys to move earlier or later.
Each row shows the time, the teammate, the title, a line about the run, the skills used, and the duration. A routine’s run has the routine’s name as its title. Research rows also show the credits used. See What Squad costs. A row that is not finished, or that did not end well, has a mark:
A run that finished has no mark.
When a day in the range has more runs than History can list for one day, History says “A day here has more runs than History can list for one day. Its newest runs show, and its earliest don’t.” See Limits and defaults.
Read a run’s detail
Select a row. The detail panel shows:- The kind of run, and Finished or the run’s mark, with the duration
- Summary and, for research runs, Parameters and Result preview
- What it touched, and Request and Response where they apply
- Usage: Input tokens, Output tokens, Cache read tokens, and Cache write tokens
- Skills used
- View related task when the run belongs to a task
- Technical details, with the Model, Provider, Reasoning level, and Channel.
A routine’s run that fails before its teammate starts working, for example because no AI account can run its model, shows Didn’t finish about a minute later, with the error from your cloud computer. Its time and duration are the run’s own, also when Squad learns of the end later. The cloud computer does not restart because of such a run. See Error texts in a run.
When a research or tool-call run failed because its tool was not working, its row says “The tool wasn’t working”, not the tool’s own error. When any run fails this way, its detail says that the teammate “couldn’t do this because a tool it uses isn’t working right now. That’s on Squad’s side, not anything you did.” The tool’s own error is under Technical details. Such a run never shows Ran out of time or Check the time limit, also when the tool timed out.
See helper runs
When a teammate hands part of a job to a helper, the helper’s run is its own row in History:- Its title is “Helper:” followed by the helper’s short name, for example “Helper: Review the docs sync PR”. When Squad has no name for it, or you cannot see the teammate that started it, the title is “Helper run”.
- It sits indented under the run that started it. When that run is on another day, the row says Started by and the teammate’s name.
- Its detail says who started it, for example “Mara started this helper.” When Squad has them, it also shows Open the run that started it and Open the chat. It does not show what the helper was asked. The run that started it must be in the days that you are viewing for Open the run that started it to show.
- The detail of a run that started helpers lists them under Subagents.
- The Helpers filter appears when the list has a helper run.
See trigger runs
A run that a trigger started is its own row in History:- Its title is “Webhook:” or “App event:” followed by the trigger’s name. The Triggers filter under Kind shows or hides these runs.
- One run can carry several events that arrived while the trigger’s last run was going.
- On the trigger’s page, Open in History on an event opens its run in History.
Stop a run
Stop a run when a teammate works on something that you did not mean to start, or takes a wrong turn. Before you start: you must be the owner or an Administrator. Collaborators and Viewers do not see Stop. An Administrator who is limited to some teammates cannot stop the runs of the other teammates. Stop is in three places:- In chat, under the teammate’s working message. See Stop a reply in progress.
- In History, on the row of a run that shows Running. Research and tool rows have no Stop.
- In the detail panel of a run that shows Running.
1
Select Stop
Select Stop. Its tooltip says “Stop [teammate]‘s run. Anything it already saved stays.”
2
Confirm
Select Stop the run. To let the run continue, select Keep going.
3
Wait for the run to end
Stopping… shows until the run ends.
- Your cloud computer stops the run and the helpers that it started. Work that the run already did stays. For example, a saved file, a sent email, or a created task is not undone.
- The run shows Stopped. Squad does not count it as a failure. You get no failure notification, Squad does not run it again, and it is not on Health or Today.
- A run that finished before the stop arrived stays finished.
- On a Claude Code account, Stop also ends a run that is still waiting for memory on your cloud computer. Squad does not run a stopped run again on a model under When it can’t answer. The teammate’s next run in that conversation starts only after every program of the stopped run has ended.
- The teammate keeps the conversation. With your next message, it knows that the last run was stopped.
When the stop does not go through
Check today’s problems on Health
The Health screen is for the owner and Administrators. It has no menu entry. Press ⌘K (Ctrl+K on Windows) and select Health, or open it from a teammate’s About page. When that teammate has a run today that Health lists, the page shows one of these lines:- “A run today didn’t finish.” or, for more than one, for example “2 runs today didn’t finish.”
- “Some runs today were cut short, and each one picked back up.” when no run failed and every run that was cut short continued.
- “Some runs today were cut short, and not every one ran again.” when no run failed and at least one run that was cut short did not run again.
- All clear: “No failed or interrupted runs today, and no provider limits in effect.” It does not show while the line “Claude Code has reached its usage limit.” is above the screen. When that line shows, no run failed or was interrupted today, and no provider is limiting your teammates, Health says “No failed or interrupted runs today. Only the usage limit above is holding your teammates up.”
- Provider status: an AI provider is rate-limiting your teammates. See Choose models and manage AI accounts.
- Needs a look: each failed run, with the teammate, the run, the time, what went wrong, Technical details when there is more detail, and View in History, which opens that teammate’s runs in History. A run that gave no reason says “Ran out of time.” or “Didn’t finish.”
- Routine interruptions: runs that maintenance, a restart, or a provider error interrupted, and failed attempts that the teammate is still trying again. A run that a newer run replaced, a run that was reported twice, and a run marked Picked up are not listed. Each row is tagged resumed or not run again. When every row is resumed, the section says “Routine events interrupted these runs, and each one resumed automatically, so nothing is needed from you.”
Know when Squad resumes a failed scheduled run
When a routine’s run fails because the AI provider had a temporary problem, Squad wakes the teammate once more, two minutes later. The teammate is told to check where it left off, finish the remaining work, and not redo steps that already succeeded.
A resumed run shows “The AI service hiccuped, and Squad picked this run back up.” in History and in its detail. A run that a restart cut off and that Squad gave back to the teammate shows “A restart cut this run short, and Squad picked it back up.” instead. See Interrupted runs. It is listed under Routine interruptions on Health.
Squad does not resume a run that failed with a rate-limit error. See Choose models and manage AI accounts.
Follow Activity
Activity lists what your squad does, newest first.- Items that are new since your last visit have a blue dot. Previously seen marks where your last visit ended.
- Select Filter to show one teammate (Teammate: Everyone or a name) or one kind (Kind: All activity, Tasks, Needs you, or Updates). Show everything clears the filter.
- Select an item to open its task. An item without a task opens its activity page, where you can read the detail and add a comment. Viewers cannot comment.
- Select Load older activity to see more.
- Select Every run, by day at the bottom to open History.
On Squad for Mac
Squad for Mac has the same History and Activity, with these differences. History- Under Teammates, a spinner shows a teammate that is running now. Otherwise the row shows when its next routine runs.
- Under the filters, a small calendar picks a day. Summary shows Total runs, Success rate, and Avg duration.
- In the detail of a failed run, the Mac adds one action. Reconnect and the app’s name shows when a connection expired, for everyone except a Viewer. Otherwise, Run it again shows on a routine’s run, for the owner or an Administrator.
- Esc, or a click outside, closes the detail.
- In Week, a busy day shows the runs that fit, then a link with the number and more that opens that day.
- Filter > Kind offers Everything instead of All activity.
- The Mac also hides older upkeep rows. The web keeps entries from before.
- Activity on the Mac does not list when someone takes over or hands back a teammate’s computer. See Hand back control.
Check that it works
- A run that you just started shows as Running in History. When it finishes, the mark goes away, and its detail says Finished.
- A run that you stopped shows Stopped.
- Health shows All clear when nothing failed today.
- Activity shows your teammates’ latest actions at the top.