Setup and account
| Item | Value | What happens at the limit | More |
|---|---|---|---|
| Password | At least 8 characters | A shorter password is refused. | Get started |
| Email verification code | 8 digits, valid for 15 minutes | An expired code does not work. Ask for a new one. | Get started |
| Build of your cloud computer | About 2 minutes, up to 3 attempts | A request to build the computer that gets no answer is sent again after 2, 5, and 10 seconds. If it still gets no answer, the next attempt starts about 45 seconds later. If all attempts fail, the setup screen shows an error. The last step, Final checks, also brings your cloud computer up to date, Claude Code included, before your squad opens. If that is not done 15 minutes after Final checks started, your squad opens anyway. | Fix setup problems |
| A build of your cloud computer with no progress | 30 minutes | Squad counts the build as stopped. The building screen gives way to the setup form, which says “Your squad’s setup stopped before it finished. Launch it again.” The page checks every 30 seconds while the building screen is open, and not in the first 2 minutes after the screen opened. A new launch can then take over the build. Squad for Mac goes back to its setup screen too. | Fix setup problems |
| Smallest context window of a model that Squad offers, in the Cloudflare Workers AI group | 128,000 tokens | A model with a smaller window is not offered in the model lists. Qwen3 30B (Workers AI) and Llama 3.3 70B (Workers AI) were removed. The next save in the dashboard removes them from AI your squad may use and from the fallbacks. A teammate set to one keeps it, shown as “not in your allowed models”. Squad for Mac does the same from version 1.0.98, and shows such a teammate’s model as “no longer offered”. Version 1.0.97 still lists them. | Choose models and manage AI accounts |
| Context window of Claude models on a Claude connection | 1,000,000 tokens for Claude Fable 5.2, Claude Fable 5.1, Claude Opus 5.5, Claude Sonnet 5.5, and Claude Haiku 5.5 | Squad sets this window for these models on your cloud computer. On Claude Code, Claude Code sets the windows itself. | Choose models and manage AI accounts |
| Model a new squad starts on | Set by the provider that you pick at setup. Claude Code: Claude Code Opus 5.5. ChatGPT · Codex: GPT-6.1 Sol. GitHub Copilot: Copilot Claude Sonnet 4.6. Claude: Claude Opus 5.5. MiniMax: MiniMax M2.7. Z.ai: GLM-5.3 Flash (Ox Alpha). Grok: Grok 4.6. Gemini: Gemini 3.8 Flash. Kimi: Kimi K3. OpenRouter: OpenRouter Claude Opus 5.5. Qwen Cloud: Qwen 3.8 Max. Cloudflare Workers AI: DeepSeek V4 Pro (Workers AI). OpenCode: GPT-5.6 Sol (OpenCode). | Change it in Thinks with on Settings > AI. Connecting another provider later does not change it. | Choose models and manage AI accounts |
| Check of the ChatGPT sign-in banner when you come back to the tab | At most once a minute | A return within the minute checks when the minute is up, if the tab is still in front. The banner also updates at once when your squad opens, when you open AI, and after you connect or disconnect an account. | An expired AI connection |
| Check for newer GitHub Copilot models after you connect Copilot | Every 20 seconds, for up to 15 minutes, while AI is open | The models show when your cloud computer has loaded them. That waits until no teammate is working. | Connect your AI subscription |
| Device code sign-in for an AI account | 5 minutes | The sign-in stops. In Settings > AI, the window shows “Authorization timed out. Please try again.” | Connect your AI subscription |
| New teammate ready for work | About 2 minutes after the chief of staff creates it | Until then, work sent to the new teammate can go to the chief of staff instead. | Add, change, and pause teammates |
| Your name in Settings > Squad > General | Up to 80 characters | A longer name is refused with “That name is too long. Please keep it under 80 characters.” An empty field is not saved. A name that a teammate already uses is refused. | Settings reference |
| Reason when you cancel your subscription | 20 to 5,000 characters | With fewer than 20 characters, the screen says “Please write at least 20 characters.” and the cancel button stays off. The field stops at 5,000 characters. | Manage your subscription |
| Failed renewal payment | Locks at once. If the card is not updated within 30 days of the failed payment, the subscription is canceled | The lock screen says “Your last payment didn’t go through” and names no date. Squad sends no email, but the billing portal can email the owner about the payment. Until the subscription is canceled, Squad keeps the squad, its data, and the email inboxes of your teammates, and a card update unlocks the squad when the payment goes through. After the subscription is canceled, the squad’s data can be deleted at any time. | If a payment fails |
| Deletion of a squad whose subscription ended | Any time after the end of the paid period | Squad gives no date and sends no email. An owner who got an email with a deletion date before November 15, 2026 keeps that date: the squad is not deleted before it. | What happens at the end date |
| Money-back guarantee on your first payment | 7 days after you subscribe | Email support@squad.so from your account email within 7 days. Renewals and credit purchases are not refundable. | Manage your subscription |
| Chief of staff per squad | 1 | A teammate cannot create a second chief of staff. | Add, change, and pause teammates |
| A workspace reset with no progress | 30 minutes | The checklist closes and says “The reset stopped before it finished.” Start the reset again to finish it. Until then, a new reset is refused. | Reset your workspace |
People
| Item | Value | What happens at the limit | More |
|---|---|---|---|
| Invite link | Works for 7 days, once, and only for the invited email address | The invite page says “This invite expired”. Invite the same address again. The new link replaces the old one. | Invite people to your squad |
| Seats in total | No limit | Not applicable. Buy more seats in another purchase. | What Squad costs |
| Seats bought in one purchase | 1 to 100 | − and + on Billing stop at 1 and at 100. | Invite people to your squad |
| Seats used | 1 for each person you invited and 1 for each open invite. The owner uses none. | With every seat in use, an Administrator cannot invite. The owner’s invite adds one seat with Invite and add a seat. If the seats filled up meanwhile: “Every seat is in use. Buy another seat first.” | Invite people to your squad |
| Release seats | Only seats that nobody uses and that no waiting invite was bought for, all at once | ”Those seats are in use. Remove people or revoke invites first.” | Invite people to your squad |
| Teammates a new person can use | Every teammate, including ones added later | Narrow the list with All teammates on the person’s row in Settings > People. | Invite people to your squad |
| Items in a person’s Activity | The newest 8 in each section: Questions they answered, Task comments, Squad chat | Older items do not show. | See what a person did |
Tasks and questions
| Item | Value | What happens at the limit | More |
|---|---|---|---|
| Files on one note on a task, or on a new task | 10 files | The note or the task is refused with “A note can carry at most 10 files.” | Tasks |
| Files with one answer to a question | 10 files | The card says “An answer can carry at most 10 files.” and adds none of the files you picked. | Send files with an answer |
| Files on one task, in total | No limit | A task holds every file given with it, in its notes, and with answers. | Tasks |
| Files in a task’s Files list | The newest 50 | Show more files shows 50 more each time. | Tasks |
| Stuck mark | More than 2 days with no update, on a teammate’s task in Working on it, or assigned in Not started | The card shows Stuck for N days · no progress. Tasks marked Ongoing never get this mark. A person’s own task never gets it. | Tasks |
| Stall detection, first step | 2 days with no update | Squad asks the owning teammate for progress. If the task is still quiet 2 days later, Squad asks you a question in Needs you. | Tasks |
| Stall detection, second step | 7 days with no status change | Squad asks you a question directly. | Tasks |
| Stall detection schedule | Once an hour | The check covers tasks that an AI teammate owns, in Not started (owned but not started) or Working on it, and not marked Ongoing. | Tasks |
| Comments shown when you open a task | The newest 50 | Show earlier comments shows 50 more each time, back to the first comment. A link to an older comment shows the earlier comments until it is on screen. | Tasks |
| Comments that say which teammates have not seen them | The newest 51 comments of a task, one more than the first page shows | An earlier comment shows no “hasn’t seen this yet” line, also after Show earlier comments. | Tasks |
| Cards per column on Tasks | 4 cards | The column shows Show all N. Show less folds it again. | Tasks |
| Questions and emails on Today | The first 3, urgent first, then newest | See all with the count opens the rest in Needs you. | Needs you |
| Over a day | A question or an email waiting more than 1 day (24 hours) | It shows Over a day and counts in the Over a day filter. The filters show only when at least one question or email is that old. | Needs you |
| Over 30 days | A question or an email waiting more than 30 days | Needs you shows a card with Review them and an Over 30 days filter. | Needs you |
| Just answered | Each answer for 45 seconds, in this browser tab only | The answer leaves the strip. Undo it from Show resolved instead. | Needs you |
| Resolved questions under Show resolved | The squad’s 30 newest resolved questions, whoever answered them, canceled ones included. A person limited to some teammates sees only the ones about those teammates. | Older resolved questions are not listed. | Needs you |
| Clear all in Needs you | Shows with 2 or more open questions that you did not set for later | In the ⋯ menu, as Clear all N questions…, for the owner and Administrators only. | Needs you |
| Later on a question, the time | At least 1 minute ahead, and at most 60 days ahead. In the dashboard, the Pick a time field takes a time from 2 minutes ahead to 60 days ahead less 1 hour. | Squad refuses another time with “Pick a time in the next 60 days.” In the dashboard, the field shows the same words and Set is off. | Needs you |
| The message after you pick Later, with Undo | 12 seconds | The message goes away. To bring the question back after that, select Bring back now on its row for later. | Needs you |
| Later, the choices | This evening: 6 PM, offered only before 5 PM. Tomorrow morning: 9 AM. Monday morning: 9 AM, not offered when Monday is tomorrow. In your browser’s time zone. | Pick a time takes any other time. | Needs you |
| Rows in Archived and Trash on Tasks | 100 at a time | Load older… loads 100 more. | Tasks |
| Steps of one task on the board | 50. Archived steps and steps in Trash do not count. | The 51st is refused with “That task already has 50 steps. Split the work into another task.” | Tasks |
| Steps of one task in all, archived and in Trash included | 100 | Another step is refused with “That task holds 100 steps, counting the archived ones. Delete some of those for good to add more.” | Tasks |
| Levels of steps | 1 | A step cannot have steps. A task that has steps cannot become a step: “This task has steps of its own, so it can’t be a step of another task.” | Tasks |
| Open asks on one question | 50 | A teammate’s 51st ask is refused, and the teammate is told to wait for answers or withdraw some. Undo on an answer is refused with “Can’t undo yet. This task already has 50 questions waiting on answers, so answer some first.” | Needs you |
| Size of one ask | 64 KB, its words and attachment together | A larger ask is refused, and the teammate is told to put the long part in a document and link it. | What teammates can do |
| A teammate’s @mention in a long run of teammates’ notes | Held when the newest 50 notes on a task’s or an activity’s thread, the new note included, are all teammates’ notes from the last 24 hours | The note posts, and the teammates that it names do not wake. They read it on their next run. A person named in it is still notified. A note from a person ends the run. When the notes in the run add up to more than 4 MB, mentions wake as usual. | Tasks |
Today
| Item | Value | What happens at the limit | More |
|---|---|---|---|
| Today so far | 5 lines, one for each teammate, with its latest work today | Other teammates are not listed. See all activity opens Activity. | What Squad is |
| Today’s routines | The first 5 of the day | A line says “One more runs today.” or “N more run today.” See all routines opens Routines. | Routines |
| Work that did not finish, set aside with the X | Until the end of the day on your device’s clock, in this browser | A problem that still fails the next day shows again. A different problem shows at once. | Fix work that did not finish |
Chat
| Item | Value | What happens at the limit | More |
|---|---|---|---|
| Files a teammate attaches to one chat message | 4 files | Files after the fourth are dropped. | Chat |
| Files from one chat message that a teammate on a Claude Code account gets | 8 files, each up to 25 MB, each downloaded within 20 seconds | Squad saves each file on your cloud computer for the teammate. Files after the eighth, larger files, and files that take longer to download are not saved. The teammate still gets your message. | Chat |
| Conversations in a teammate’s list | 40 at a time | Show older conversations loads 40 more. | Chat |
| Conversation name | 80 characters | The name field accepts no more text. | Chat |
| New replies before a conversation opens at the newest instead of at the first unread | More than 10 teammate replies that this browser has not seen | The conversation opens at the newest reply. | Chat |
| Your sent messages that ↑ can bring back in a conversation with a teammate | The last 50 | Older messages are not offered. In the Squad chat on the web, ↑ can reach every message you sent that the screen has loaded. Squad for Mac stops at 50 everywhere. | Chat |
| Group chats listed in the sidebar | 5, newest first | All group chats shows the rest, up to the newest 200 open group chats. Show fewer goes back to 5. Teammates’ own conversations do not count toward the 200 until a person posts in them. | Chat |
| Teammates’ conversations on the Squad chat screen | The newest 50 that no person posted in, plus the ones that a person posted in | Older ones are not listed. | Chat |
| Conversation reset | None | Conversations do not reset on their own. A long conversation is shortened in the teammate’s working memory. On a Claude Code account, Claude Code keeps each conversation for as long as Squad shows it, however long nobody writes in it. You cannot change this. | Chat |
| Messages in a conversation that you can fork or edit | 2,000 | ”This conversation is too long to fork or edit.” Start a new conversation. | Chat |
| Conversation so far that the teammate gets when it has no memory of the conversation, for example in a fork or a new version | Up to about half of the model’s context window, from the newest 1,500 messages at most | Messages before the newest 1,500 are left out, and the teammate is told that earlier messages were not read. Within those, a conversation that is still too long is cut in the middle: the teammate gets the oldest of them and the newest messages, and is told that some messages were left out. Files in earlier messages are named, not sent again. | Chat |
| History copied into a new group chat | Last 30 messages | When you @mention another teammate in a 1:1 conversation, the new group chat starts with the last 30 messages. | Chat |
| Wait for a reply | 15 minutes | The message fails, for example with “Otis stopped without replying. Retry to send your message again.” In a 1:1 conversation, the error has a Retry button. The check runs every 10 minutes, so the error can take up to about 25 minutes to appear. A message whose run is still working does not fail. A message that waits while your teammates are busy with other work does not fail either. | Chat |
| Time before the Squad chat says that your squad isn’t answering | More than 10 minutes without contact from your cloud computer | The Squad chat shows “Your squad isn’t answering right now, so new messages can’t reach your teammates. Try again in a few minutes.”, and messages to group chats are refused until the cloud computer contacts Squad again. It also shows while the cloud computer restarts, until it contacts Squad again. The group chats stay in the sidebar. While your teammates are busy, the cloud computer still contacts Squad every minute. This does not start a run. | Use the Squad chat |
| Wait for the chat after your cloud computer restarts | Up to 1 minute, checked every 5 seconds, while the restart is less than 3 minutes old and the chat has not reconnected | Squad sends the message another way. The teammate still gets it, but a card alone does not count as its reply there, so the chat can say that it finished without a reply. A conversation that was edited or forked does not switch: its message waits for the chat. | Retry a message that failed |
| Automatic resend | 2 tries, after 3 seconds and 8 seconds | Squad resends only when the message did not reach the teammate. For other failures, you see Retry. | Chat |
| Names that you turned down for one conversation | The last 10 are remembered | An older turned-down name can be suggested again. | Chat |
| Archived conversations listed for one teammate | 200, newest archived first | Older archived conversations are not listed. | Archive or delete a conversation |
| Conversations with one teammate checked for your new replies | Your newest 30 open conversations with that teammate, among its newest 150 open conversations | A reply in an older conversation shows no blue dot or new mark. Conversations that are not yours do not use up your 30. | Which replies are new for you |
| Helpers on one “Asked” line in a conversation | Each started within 15 minutes of the one before, by the same teammate. Up to 3 names. | A later helper starts a new line. Helpers whose names are not shown are counted, for example “and 2 more”. | See the helpers your teammates start |
| Short name of a helper in the conversation and in History | The first line of the name that the teammate gave it, at most 8 words. Whole words up to 80 characters show. | Words past 80 characters are cut. A name of more than 8 words shows no name. So does a name with a word that is not a plain word, for example a number of 3 or more digits, letters mixed with digits, an email address, or a path. A short version counts as a word, for example “4.5” or “1.0.62”. So does a GPT or GLM model name in capitals with a dash, for example “GPT-5.1” or “GPT-4o”, and a quarter or a half, such as “Q4” or “H1”. Other model names with a dash, such as “Claude-3.5” or “gpt-4o”, show no name. A name with a dotted number shows no name when it also says code, PIN, or OTP. A name that names a secret shows no name, for example one that mentions a password, a secret, a credential, or an API key. A name about signing in, for example “Fix the login page” or “Cookie banner copy”, shows, unless it also has ”:”, ”=”, or a digit. A bare “key”, “PIN”, or “code” counts only with a value after it, for example “the key is…” or “code 123456”. A name that only says what it is, for example “Helper” or “Subagent”, shows no name. A helper with no name is counted, not named. | See the helpers your teammates start |
| Emails waiting on you that a chat’s email card can check | 500 drafts and 500 escalated emails | When 500 or more of either kind wait, a card says nothing about an email that it does not find, instead of “No longer waiting on you.” | Email conversations in chat |
| People counted in one conversation | The first 20 people who write in it | A person who first writes after 20 others is not counted in that conversation, so its replies are not new for them. | Which replies are new for you |
Projects
| Item | Value | What happens at the limit | More |
|---|---|---|---|
| Project name | 80 characters | The name field accepts no more text. An empty name is refused with “Give the project a name.” | What Squad is |
| A project’s notes that every teammate reads first | 2,000 characters | The field accepts no more text. | What Squad is |
| Open projects in a squad | 200 | A new project is refused with “You have 200 open projects. Archive one before making another.” Bringing one back is refused with “You have 200 open projects. Archive one before bringing this one back.” | What Squad is |
| Projects in the sidebar | The 5 worked in most recently, plus the open one | All projects with the number of others shows the rest. Show fewer goes back. | What Squad is |
| Archived projects in the sidebar | 100 at a time, newest first | Show older loads the next 100. If they do not load, the sidebar says “Older ones didn’t load. Try again”. | What Squad is |
| Conversations on a project’s page | 200 direct conversations and 200 group chats | Older ones are not listed. When a list is full, Delete project… does not say how many conversations stay. | What Squad is |
Sidebar
| Item | Value | What happens at the limit | More |
|---|---|---|---|
| Pins | Saved to your account, up to 32,000 characters of saved pin data | Pins show on every device where you sign in. When the saved data would pass the limit, the new pin is not saved, and an alert at the bottom of the screen says “You have too many pins to add another. Unpin one first.” | Search and keyboard shortcuts |
| Pinned places | Email, Docs, and Contacts, until you change them | The other places are under More. More starts folded. | Pin a place to the sidebar |
| New on a place in the sidebar | 30 days after the place joined the sidebar, counted in your own time zone. Contacts and Wallet joined on October 14, 2026. | The mark goes away by itself, or when you open or pin the place. | Pin a place to the sidebar |
| Pinned places in the bar at the bottom of a phone | The first 2 | The other places are on More, the last tab. | On a phone or a narrow window |
| Sidebar width | 208 to 420 pixels, 252 by default | Drag the right edge of the sidebar to resize it. Double-click the edge to go back to the default. | What Squad is |
| Count on the bell | Up to 9 | Above 9, the bell shows 9+. | Choose your notifications |
Search
| Item | Value | What happens at the limit | More |
|---|---|---|---|
| Command palette with nothing typed | The first 5 open questions, then New task, New project, Pin a task, and Pin a doc | Type to search. | Search and keyboard shortcuts |
| Command palette results | 5 each for questions, places under Go to, People, Projects, Tasks, Documents, and Email. 4 each for workflows, apps, and help pages. Up to 8 contacts, after 2 or more characters. Teammates are not capped. 40 in all. | Type more words to narrow the results. | Search and keyboard shortcuts |
Docs
| Item | Value | What happens at the limit | More |
|---|---|---|---|
| Docs on one page of the Docs list | 24 docs | Load more shows the next 24. | Docs |
| Archived docs on Docs | 50 at a time | Load more shows 50 more. | Docs |
| Folder levels | 1 level | A folder cannot contain other folders. | Docs |
| Delete a folder | Empty folders only | A teammate that tries to delete a folder with docs in it gets “Cannot delete a folder that contains documents.” | Docs |
| Docs moved in one step by a teammate | 100 docs | The move is refused with “Cannot move more than 100 documents at once”. | Docs |
| Version history | None | An edit replaces the earlier text. | Docs |
| Item | Value | What happens at the limit | More |
|---|---|---|---|
| Emails per minute, per teammate | 10 | The send is refused. Scheduled sends due in the next minute also count. | |
| Different recipients in 5 minutes, per teammate | 20, across To, Cc, and Bcc | The send is refused. | |
| Daily send cap, per teammate | 100 in a rolling 24 hours (default) | The send is refused. You change the cap in Daily send cap in the teammate’s inbox settings, in Settings > Email > Inboxes and rules. A cap of 0 means no cap. | |
| Daily send cap that a teammate sets for you | 1 to 10,000 | Other values are refused. A teammate cannot set 0 (no cap). | Email settings |
| Squad daily cap | 500 in a rolling 24 hours | The send is refused with “This squad has reached its limit of [N] emails a day, counting scheduled sends. It frees up over the next 24 hours.” You cannot change this cap in the dashboard. | |
| Squad monthly cap | 10,000 in a rolling 30 days | The send is refused with “This squad has reached its limit of [N] emails in 30 days, counting scheduled sends. It frees up as older sends pass 30 days.” You cannot change this cap in the dashboard. | |
| Drafts waiting for approval | Do not count toward the caps | A pending draft uses no cap space. | |
| Scheduled send | At least 60 seconds in the future | An earlier send time is refused. | |
| A TXT record value at your DNS host | Squad offers a split value for a TXT value longer than 255 characters: quoted parts of up to 255 characters, on one line. A value of 255 characters or fewer is not split. | Paste the split value when your DNS host refuses the long one. | Give a teammate an email inbox |
| Moving rules after an address change | Squad tries a rule again after 30 seconds, then 1, 2, 4, 8, 15, and 30 minutes | A rule that still cannot move is listed under Didn’t carry over to the new address. A rule that the mail provider refuses outright is listed at once. | Give a teammate an email inbox |
| Rules that Identity names after an address change | 4 | Past 4, it names 3 and “[n] more”. | Give a teammate an email inbox |
| An inbox setup or an address change that stopped partway | Checked 11 minutes after it started, then every 5 minutes | A stopped setup removes the inbox and gives the seat back. A change stopped before the move keeps the old address. | Email troubleshooting |
| Scheduled send with attachments | Not supported | The scheduled send is refused. | |
| Handling instructions | 4,000 characters when a teammate saves them | Text after 4,000 characters is dropped. Squad sets no length limit when you type them yourself. | |
| Email signature | 1,000 characters when a teammate saves it | Text after 1,000 characters is dropped. Squad sets no length limit when you type it yourself. | |
| Address, part before the @ | 32 characters: lowercase letters, digits, and hyphens | Other characters become hyphens. Longer text is cut. | |
| Custom email domains | 1 per squad | A second domain is refused until you remove the first. | |
| DNS check after Verify now | Up to 4 checks, 45 seconds apart | The domain keeps its status. Squad also checks again on its own. | |
| Emails loaded on Email | Newest 100 | The count under the inbox name shows N+ when the list is full. | |
| Unread email on the Email badge and in Unread | 100 | The badge stops at 100. Unread lists the newest 100 unread received emails. | Give a teammate an email inbox |
| Search email | Asks the picked inbox, or each inbox in All inboxes, once you type 2 characters, about 0.3 seconds after you stop typing. Up to 25 results from each inbox. | With 1 character, it searches only the emails that are loaded. Type more words to narrow the results. | Give a teammate an email inbox |
When you click Approve & send, the email goes out at once and skips every send cap. The caps apply to email that teammates send on their own.
Runs
| Item | Value | What happens at the limit | More |
|---|---|---|---|
| No events from a chat or email run | 10 minutes | History marks the run Still finishing. If the run reports back later, the row corrects itself. | History |
| Signal from a run that is still working | Every 3 minutes, after the first 3 minutes | A run in one long step, such as a long command or a tool call, tells Squad that it is still working. It stays Running, and its chat message does not fail for want of a reply. A run that shows no sign of work sends no signal. On a Claude Code account, the signal goes on for as long as the teammate’s process runs, also when it hangs. | History |
| No events from a routine’s run or another run | 30 minutes | Same as above. | History |
| A chat message in the dashboard that a restart of your cloud computer interrupts | Continued up to 3 times. Another continue needs about 5 minutes of work since the last one. | The chat shows “Your cloud computer restarted again while your teammate was finishing this message, so it stopped partway.” Check what is done, then send the message again. | Chat |
| Other work that a restart of your cloud computer cuts off: work on a task, a request, a reply in a chat app, or a routine’s run | The teammate is woken once, about 2 minutes after the restart, to pick it back up. Restarts that cut off the same teammate are counted over 2 hours. | After a second restart within 2 hours, the teammate does not run the same heavy step again. It tells the person who asked what happened and asks how to go on. After a third, Squad does nothing more. | Other work that a restart cut off |
| Confirmation of a Stop | 90 seconds | With no word from your cloud computer, Stop says “Your cloud computer hasn’t confirmed the stop yet. If the run keeps going, press Stop again.” The run may still stop. When the cloud computer refuses the stop, Stop says “The stop didn’t go through, so the run is still going. Press Stop to try again.” | History |
| Check for silent runs | Every 5 minutes | A silent run can show Running for a few minutes after it stops. | History |
| No progress on your cloud computer | 15 minutes with no progress signal | The run is stopped. A run is not stopped while a tool call or a memory compaction is in progress, but a tool call with no progress is ended (next row). Runs on a Claude Code account are not stopped this way. | Fix a teammate that is stuck or failing |
| A tool call with no progress | 15 minutes with no sign of progress, checked every 30 seconds | The tool call is ended, and the run goes on. The teammate is told that the tool stopped making progress. A tool call that keeps making progress has no time limit. Also applies to Squad’s own tools in a run on a Claude Code account. | Fix a teammate that is stuck or failing |
| Teammate runs at once on your cloud computer | 16 | Further runs wait their turn. Runs on a Claude Code account are not counted here. | Fix a teammate that is stuck or failing |
| Helpers at once on your cloud computer | 16 | Further helpers wait their turn. Helpers of a teammate on a Claude Code account are not counted here. | See the helpers your teammates start |
| Free memory a run on a Claude Code account needs to start | 1,536 MB, plus 512 MB for each other Claude Code run that started less than 30 seconds ago. With no other Claude Code run working, the run starts at once. | The run waits and checks again every 5 seconds, with no time limit, and does not fail. After 15 seconds, the teammate’s line says “Waiting for memory to free up on the cloud computer”. There is no fixed number of Claude Code runs at once. | A teammate says “Waiting for memory to free up on the cloud computer” |
| Helpers that a teammate on a Claude Code account starts | No limit of their own | The teammate’s run stays open, and its reply waits, until its helpers finish. A new message in the same conversation waits until the teammate’s run ends, for up to 24 hours. If the earlier run is still going after 24 hours, the run for the new message fails. A run time limit from an earlier setting, or a routine’s time limit, still ends the run and its helpers. | See the helpers your teammates start |
| A new message to a teammate on a Claude Code account while it works in the same conversation | Waits for the run in progress | The run in progress is not ended. A message waiting in the dashboard waits as long as that run works. A message whose own run already started waits up to 24 hours for the earlier run, then its run fails. | Send a message while the teammate is busy |
| Run time limit | No limit | You cannot set a limit. Settings > AI > More > Run time limit shows No limit. | Fix a teammate that is stuck or failing |
| Workspace run time limit from an earlier setting | Shown on the Run time limit card, with a warning | Chat runs, also from Telegram, Discord, or Slack, that take longer than the limit are stopped. Routines use their own limit. A workspace with no saved value has a limit of 10 minutes. Click Remove the limit, then save. | Fix a teammate that is stuck or failing |
| Time limit of a new routine | 24 hours, for a routine that you create in the dashboard and for one that a teammate creates through Routines. A run also stops earlier after 15 minutes with no progress. | The routine editor has no time limit field. A teammate can set a limit from 60 seconds to 24 hours when you ask. A routine that a teammate created another way can have no limit saved. | Schedule recurring work with routines |
| Routine limit that is unset or shorter than 24 hours | Raised to 24 hours each time your cloud computer restarts | A short limit is left from an earlier setting. Until the next restart, a routine with no limit saved, for example one that a teammate created another way than through Routines, stops after 60 minutes. The routine editor shows the limit, a warning, and Raise to 24 hours. A limit of 0 (no limit) is left alone. | Schedule recurring work with routines |
| Automatic retry | 1 retry, 2 minutes later | Only for a routine’s run that fails with a temporary AI provider error. Rate-limit, quota, and login errors are not retried, except that a Claude Code run that hits its usage limit continues once on the next Claude Code account (see below). There is no retry if the teammate is paused, the routine was paused, a newer run started, or you messaged the teammate in the meantime. | History |
| Restart for new software on your cloud computer | Waits until no teammate is working, with no time limit. Runs on a Claude Code account count as work. | Only software that the cloud computer can load only when it starts needs a restart, once for each update. Settings changes, account changes, and most updates to the teammate software apply without one. | Interrupted runs |
| Notice “Saved. Applying changes in the background (usually a minute or two).” after a settings save | Up to 5 minutes | The notice goes away when your cloud computer has applied the change, or after 5 minutes. | Add, change, and pause teammates |
| Restart of your cloud computer to recover it | Immediate. Squad does this when the cloud computer stopped answering. | Runs in progress stop. History shows them as Interrupted. When it can, Squad gives a chat message in the dashboard that a restart interrupted back to the teammate, which continues it, up to 3 times. Work on a task, a request, a reply in a chat app, and a routine’s run are picked back up as in the next row. History then shows the cut-off run as picked back up. Squad does not start heartbeats, trigger runs, or helpers again, so check that work and ask again if it is not done. | History |
| Claude Code account that reaches its usage limit | Skipped until its limit resets. If the reset time is not known, 1 hour. At most 8 days. | Squad switches to the next Claude Code account in your order, and Settings > AI shows that account as In use. The run that hit the limit continues once on the new account, also when it had already done work. If every account is at its limit, Claude Code cannot serve runs until one resets, and runs move to the next model under When it can’t answer if you set one. Reconnecting the account with a new token clears the skip. | Connect your AI subscription |
| Reset time in “Claude Code has reached its usage limit.” | Shown when the reset that Claude Code reports is within 8 days | Otherwise the line says “when it resets”. The line goes away at the reset, or at the next Claude Code run that works. | Claude Code reached its usage limit |
| A failed attempt that the teammate’s next attempt finished | Not counted when the next attempt in the same turn starts at most 10 minutes after the failed one ended, and finishes or is still working | The failed run is not on Today or Needs you. History shows it as Picked up once the next attempt finished, and as Interrupted while it is still working. A run marked Picked up is not on Health. A failed run that Squad cannot match to a turn, for example one from before this rule began on November 1, 2026, still counts. | Read a run’s detail |
| Rate limit on Today | 3 or more rate-limit failures in a row from one provider, the latest within 6 hours | The sentence on Today ends with the provider’s name and “is limiting your squad right now.” Health shows Provider status. Settings > AI shows Hit its limit, cooling down after one recent failure. | Choose models and manage AI accounts |
| Runs listed for one day in History | 2,000, counted over every teammate | The newest 2,000 runs that started that day are shown, and the earlier ones are not. History says “A day here has more runs than History can list for one day. Its newest runs show, and its earliest don’t.” | History |
| How far back History goes | Today and the 30 days before it | Day shows 1 day, Schedule 3 days, Week 7 days, and Month the current month up to today. Load older runs in Schedule moves back 3 days. Older runs are not shown. | History |
Routines
| Item | Value | What happens at the limit | More |
|---|---|---|---|
| Up next on Routines | The next 4 runs | Later runs are not listed. | Routines |
| Search routines | Shows with more than 8 routines | With 8 or fewer, there is no search box. | Routines |
| Wait for your cloud computer before a routine change | Up to 42 seconds, then the command once, with 10 seconds for the computer to answer | The change fails with the computer’s reason, or with “Squad lost touch with your cloud computer, so it cannot tell whether…” | Routines |
| Reason in a failed routine change | Up to 300 characters | A longer reason is cut. | Routines |
| Check of where a routine sends its result | When a teammate creates or changes a routine, then every 3 minutes, and a few seconds after a routine is written another way | A routine whose result could not be delivered because it names no chat or person that its app can send to is pointed at the conversation where it was asked for, or else at its teammate’s own chat in the dashboard. A routine that already ran is changed only after such a result. Other delivery failures do not change the routine. | Where a routine reports |
| Name of a routine that a teammate sets up | 120 characters | A longer name is refused. | What teammates can do |
| Repeat interval of a routine that a teammate sets up | 1 to 43,200 minutes (30 days) | Other values are refused. A time for a routine that runs once must be in the future. | What teammates can do |
| Routines that run at once on your cloud computer | 16, routines of teammates on a Claude Code account included | Routines that are due later wait until one ends. | Routines |
| A failed routine run that ended before its teammate started | Shows Didn’t finish about a minute after it failed | The run keeps the time that it really ended. | Error texts in a run |
Heartbeats
| Item | Value | What happens at the limit | More |
|---|---|---|---|
| Heartbeat state when created | Off | Teammates run on a timer only after you turn the heartbeat on. | Schedule recurring work with routines |
Chief of staff’s heartbeat, Lead heartbeat on Routines (lead-heartbeat) | Every 15 minutes | When it is on, that is about 96 runs a day on your AI account, even when nothing needs attention. | Schedule recurring work with routines |
| Other teammates’ heartbeats | Every hour, each at its own minute past the hour | Different start minutes keep the teammates from all running at once. | Schedule recurring work with routines |
Memory
| Item | Value | What happens at the limit | More |
|---|---|---|---|
| Load budget for About you, Notes, Personality, and Identity | 20,000 characters (default) | In a longer file, the teammate reads the first 70% of the budget from the start of the file and the last 20% from the end. With the default budget, that is the first 14,000 and the last 4,000 characters. The middle is skipped at every run. The editor shows this. | Memory |
| Company, Contacts, Glossary, Squad, Voice | No load budget | Teammates read these files when they need them. | Memory |
| Text shown in the file editor | First 400,000 characters | Saving writes what you see and removes the rest. | Memory |
| File size on save | 800,000 characters | The save is refused. | Memory |
| Results for a search in Memories | Up to 20 | Refine the search to see other memories. | Memory |
| Memories that a teammate gets before each request | Up to 10 that match the request. On a Claude Code account, the text is cut at a whole line under 9,000 characters. | Other memories are not given. The teammate can still search memory. A request of fewer than 5 characters gets no matches. | How your squad learns |
| Standing facts and recent context that a teammate gets | Up to 10 of each, on the first request of a conversation, then again every 50 requests | Between those requests, the teammate gets only the memories that match. | How your squad learns |
| Time to find memories before a request | 4 seconds | The teammate starts without memories for that request. | How your squad learns |
| Text that memory learns from in one turn | The first 8,000 characters of a request and the first 12,000 characters of a reply | Memory does not learn from the rest of a longer request or reply. | How your squad learns |
| Results for a memory search by a teammate | 5 by default, up to 20 | Not applicable. | What your teammates can do |
Skills and skill packs
| Item | Value | What happens at the limit | More |
|---|---|---|---|
| Skill tag | Lowercase letters, digits, and hyphens, up to 32 characters | Capitals become lowercase. Other characters and longer tags are refused. | Skills |
| Tags on one skill | 32 | More tags are refused. | Skills |
| Custom pack source | A public github.com repository, https://github.com/owner/repo, or a link to a folder in it on the repository’s main branch, https://github.com/owner/repo/tree/main/folder | Other addresses and file links are refused. A folder on another branch is refused with “That link is to a folder on another branch. Open the folder on the repository’s main branch and copy that link.” The folder in a link follows the same rule as Skills folder (optional). | Skills |
| Skills folder (optional) | Up to 200 characters and 4 levels deep | Longer or deeper paths are refused. | Skills |
| Same repository and folder twice | Not allowed | Remove the pack first, then add it again. | Skills |
| Repository that is already a curated pack | Not allowed as a custom pack | Turn on the curated pack instead. | Skills |
| Curated pack | Can be turned off, not removed | Remove pack shows only for custom packs. | Skills |
| Skill name clash when you turn on a pack | Allowed | The pack turns on, and each pack skill with a clashing name stays off. | Skills |
| MCP servers offered on one plugin pack’s page | 20 | More are not listed. | Connect a plugin’s MCP servers |
| One value of an offered MCP server: its address, command, an argument, an env value, or a header | 16,384 characters | A server with a longer value is not offered. | Connect a plugin’s MCP servers |
| Arguments, env values, and headers of an offered MCP server | 40 arguments, 30 env values, 16 headers | A server with more is not offered. | Connect a plugin’s MCP servers |
A plugin file that lists MCP servers (plugin.json, .mcp.json, mcp.json) | 256 KB each, 1 MB together | A larger file is not read. | Connect a plugin’s MCP servers |
| Name of an offered MCP server | 80 characters | A longer name is cut. | Connect a plugin’s MCP servers |
Backup
| Item | Value | What happens at the limit | More |
|---|---|---|---|
| How long a ready backup is kept | 7 days from when it is ready. After you cancel, until the end of your plan when that comes first. While the squad is locked, not at all | From that time, Download backup says “This backup is no longer kept. Prepare a new one.” Squad deletes the file within 15 minutes, and Backup shows Prepare backup again. When the squad locks, Squad deletes its ready backups within 15 minutes, and their download links stop working. | Back up your data |
| Backups at a time | One for each person in each squad | Asking while one is being prepared keeps that one. Prepare a new one deletes the earlier file. | Backup |
| Size of a backup | 200 MB | A larger backup fails with “Your squad holds more than one backup file can carry. Tell us, and we’ll help you get a copy.” | Back up your data |
| One file from your cloud computer | 32 MB | A larger file is left out and named under leftOut: “Files over 32 MB aren’t in the backup. It stays on your cloud computer.” | Back up your data |
| One memory | 32 MB | A larger memory is left out: “Memories over 32 MB aren’t in the backup. It stays in your squad’s memory.” | Back up your data |
| Files in one skill or teammate folder | 2,000 | More files are named under missing: “Only the first 2000 files are in the backup.” | Back up your data |
| Items in one list from your cloud computer: routines, skills, skill packs, teammates, and secret names | 2,000 | More items: “Only the first N of M are in the backup.” | Back up your data |
| Attachments listed for one email | 100 names | More are not listed. | Back up your data |
| A backup that stops making progress | Tried again after 15 minutes, up to 2 times in a row. A step that finishes starts the count again. | Then it fails with “The backup stopped partway and couldn’t carry on. Prepare it again, and if it stops again, tell us.” | Back up your data |
Integrations and channels
| Item | Value | What happens at the limit | More |
|---|---|---|---|
| Account name for a connected app | 80 characters | Longer names are cut. | Connect apps |
| App sign-in in your browser, from Settings > Apps or a connect card in chat | Checked 3 seconds after you come back to Squad. A connect card also says so 10 minutes after you started the sign-in, wherever you started it. | The Apps window says the app “hasn’t confirmed this sign-in.”, with Try again. The card says Not connected yet, with Start the sign-in again. A sign-in that lands later still updates both by itself. On Squad for Mac, a connect card for a sign-in started in the app while it stayed open keeps waiting after 10 minutes. The 10-minute notice shows there for a sign-in started before the app restarted or on another device. | Connect apps |
| What a server said when it turned down its credential | Up to 200 characters, shown to the owner only | Longer words are cut and end with ”…”. | Add an MCP server or an API key |
| Asking a custom MCP server for its tools when you save it | Up to 45 seconds | The save still works. The tools, or the server’s refusal, show after a teammate next works. | Add an MCP server or an API key |
| A chat bot that you just saved and that is not answering yet | The channel page reads the bots again every 30 seconds, for up to 30 minutes. A bot counts as starting for 2 minutes after it starts. | The page stops checking. Open the page again to read the bots again. | Channels |
| Owner’s Telegram user ID | 1 to 20 digits, greater than 0. Leading zeros are dropped. | Text with spaces, letters, or other characters is refused with “A Telegram user ID is a number, like 726882145.” | Telegram |
| Custom integrations before Find an integration shows | 7 | With fewer, there is no search box. | Add an MCP server or an API key |
| MCP server URL | Must start with https:// | Other URLs are refused. | Add an MCP server or an API key |
| An MCP server that runs a command | A command of up to 256 characters on one line, up to 64 arguments of up to 1,024 characters each. Env and header names start with a letter and have up to 64 characters: letters, digits, and _, or - in a header name. | The Add MCP server window says what is wrong and does not save. | Add an MCP server or an API key |
| MCP server name, when you rename it in Edit | 80 characters | A longer name is refused with “Keep the name under 80 characters.” An empty name is refused with “Give the server a name.” | Add an MCP server or an API key |
| Headers on one MCP server | 16 | More headers are refused with “Too many MCP headers”. | Add an MCP server or an API key |
| Who can message it list on an extra Telegram bot, a Discord bot, or a Slack app | At most 50 people | A change that makes the list longer than 50 is refused with “A list can hold at most 50 people.” You can still remove people from a longer list. | Telegram, Discord, Slack |
| Telegram main bot | Only you | You cannot add people to the main bot. Connect another bot for other people. | Telegram |
| Discord or Slack Who can message it list | At least 1 person | You cannot remove the last person. An empty list would answer nobody. | Discord, Slack |
| Answer to a direct message from someone who is not on the list | Once for each sender on each bot, until the chat service on the cloud computer restarts. At most 20 answers in each clock hour, for all bots together. | Later messages from that sender get no answer. Past 20 in an hour, nobody gets the answer until the next hour starts. | Channels |
| Tools on one model request, on Grok | 350 tools (Grok’s own cap) | Turn off MCP servers or their tools that you do not use on their cards in Custom integrations, and research tools on Billing. | Add an MCP server or an API key |
| A settings change that a teammate makes while another settings change is saving on your cloud computer | Waits up to 20 seconds | A research tools or MCP server switch is then refused with “Another settings change is still saving on your cloud computer. Try again in a minute.” Nothing was changed. | Your squad’s settings |
| A settings change from a teammate that loads only when your cloud computer restarts | Waits until no teammate is working, usually a few minutes | The earlier settings apply until then. The teammate says “Saved. It takes effect once no teammate is working, usually within a few minutes.” | Your squad’s settings |
| Connect or switch the Telegram main bot | Waits until your squad finishes its current work. Nothing restarts. | The screen says “Your new bot is saved. Your squad is in the middle of work, so the new bot starts answering when it finishes. No need to rotate again.” | Connect Telegram |
Use Squad from other apps
| Item | Value | What happens at the limit | More |
|---|---|---|---|
| A sign-in request from an AI app on the Sign in with Squad page | Waits 10 minutes for your answer | The page says “This connection request has run out”. Start connecting again from the app. | Use Squad from Claude, ChatGPT, or Cursor |
| The app’s name on the Sign in with Squad page and on Apps signed in as you | 80 characters | A longer name is cut. An app that gives no name shows as “An app”. | Use Squad from Claude, ChatGPT, or Cursor |
message_teammate wait for the reply (wait_seconds) | 0 to 50 seconds. 0 when left out. | The tool returns without the reply and says that the teammate “hasn’t replied yet”. Read the reply later with read_conversation. | Squad’s tools for AI apps |
Messages that read_conversation returns (limit) | 1 to 100. 20 when left out or 0. | A number above 100 is read as 100. | Squad’s tools for AI apps |
Conversations that list_conversations returns | The latest 20 | Older conversations are not listed. | Squad’s tools for AI apps |
Comments that get_task returns | The latest 30, and one older comment when there are older ones | The other older comments are not returned. | Squad’s tools for AI apps |
Matches that find_dashboard_action returns | 12 | The best 12 matches show. Use other words to find others. | Squad’s tools for AI apps |
Contacts and pipelines
| Item | Value | What happens at the limit | More |
|---|---|---|---|
| Pipelines in a squad | 50, archived ones included | A new pipeline is refused with “A workspace can have at most 50 pipelines.” A second pipeline with the same name, in any case, is refused. | Work a pipeline |
| A pipeline’s name | 80 characters | Longer text is cut. | Create a pipeline |
| What a pipeline is for | 2,000 characters | The box accepts no more text. | Create a pipeline |
| Stages in a pipeline | 1 to 20, with at least one open stage | ”A pipeline needs at least one stage.”, “A pipeline can have at most 20 stages.”, or “A pipeline needs at least one open stage.” | Change the stages and fields |
| A stage’s name | 60 characters | Longer text is cut. | Change the stages and fields |
| Custom fields in a pipeline | 24 | ”A pipeline can have at most 24 fields.” | Change the stages and fields |
| Choices in a Choice field | 1 to 40, each up to 60 characters | ”A select field can have at most 40 options.” | Change the stages and fields |
| A value in a pipeline’s custom field | 500 characters | A longer value is refused. | Work a pipeline |
| Follow-up delay of a stage | 0 to 365 days | ”A follow-up delay must be between 0 and 365 days.” | Set a follow-up |
| Rules by kind of touch in a pipeline | 30 | ”A pipeline can have at most 30 rules by kind of touch.” Teammates set these rules. | Work a pipeline |
| A pipeline’s goal | 1 to 1,000,000 people | ”A goal is a number of people from 1 up.” | See your pipelines |
| People in a stage’s column on a pipeline’s page | The first 6 | A button with how many more opens People for that stage. | See your pipelines |
| Follow-up tasks for a teammate | One for each pipeline with follow-ups due, about once a day, and none while the last is open | No follow-up task before the pipeline’s start date or after its end date. | Set a follow-up |
| Emails on a contact | 20 | ”A contact can have at most 20 emails.” | Read a person |
| Projects a contact is in | 20 | ”A contact can be in at most 20 projects.” | Read a person |
| Tags on a contact | 40, each up to 60 characters | Extra tags, and longer tags, are dropped. | Read a person |
| Standing rules on a contact | 20 | ”A contact can have at most 20 rules.” | Read a person |
| Score | 0 to 100 | ”A score must be a number from 0 to 100.” | Read a person |
| Next step on a follow-up | 200 characters | The field accepts no more text. | Set a follow-up |
| Notes, and what your teammates found, on a contact | 2,000 characters each | In Notes, “Notes hold up to 2,000 characters.” with Add it to their history, which keeps the whole text as a dated note. | Notes |
| One entry in a contact’s history | 8,000 characters | ”Notes hold up to 2,000 characters, and one entry in their history 8,000. Split it, or save it as a doc and link it.” | Notes |
| ”What happened, in one line” when you log something | 300 characters | The box accepts no more text. | Log a call, meeting, or note |
| A contact’s history | 20 entries at first | Show older loads 20 more, up to 250. Past 250, the page says “Older history isn’t shown here.” | Read a person |
| Possible duplicates on a person’s page | 5 | The others show in Review. | Merge two contacts |
| Contacts that a teammate imports in one call | 1 to 100 | The teammate is told “Send at most 100 contacts in one call.” and splits a larger set into calls of 100. | What your teammates do with contacts |
| Merge two contacts | Together at most 20 emails, 20 projects, 12 channels, 40 tags, and 20 rules | The merge is refused, for example with “Together they have more than 20 emails. Remove some first.” A person cannot merge with a company. | Merge two contacts |
| Undo a merge | 30 days | ”A merge can be undone for 30 days, and this one is older.” After 30 days, Squad deletes the merged record for good. | Merge two contacts |
| Search in Contacts | The first 50 matches | Type more of the name. | Open Contacts |
| Rows on People, in each Review list, and on the deals List | 50 at a time | Show more loads 50 more. | People |
| Tags in the Tag filter on People | Your 40 most used tags | Find a tag finds the rest. | Find someone |
| A count, or a change to many records | Exact up to about 160,000 records | Past it, a count says “or more”, and a change to many does not run (“More than [n] records match, too many to count before changing them. Narrow the filter to change them.”). | People |
| A spreadsheet | Every record the tab and filters match, up to what one export can read | A larger one is refused with “This filter reads more records than one spreadsheet can. Narrow it, by a tag or a pipeline, and try again.” | Export a spreadsheet |
| Names in the count before a change to many | The first 5 | ”and more” | Change everyone a filter matches |
| Spreadsheet link | A day | The file is deleted, and the link stops working. | Export a spreadsheet |
| A deal’s goal | 200 characters | A longer goal is refused: “A deal’s goal is one sentence of at most 200 characters. Shorten it and save again.” A goal that Squad makes from a pipeline’s or a playbook’s name is cut and ends with …. | Open a deal |
| Where a deal stands, as a teammate writes it | 300 characters | Longer text is cut. | Read a deal |
| Steps on a deal | 200, each up to 300 characters | ”A deal can have at most 200 steps.” A longer step is refused with “A step holds up to 300 characters: one sentence.” | Change a step |
| Why a step moved or ended | 500 characters | The box accepts no more text. | Change a step |
| Why a deal closed | 2,000 characters | The box accepts no more text. | Close, open again, or delete a deal |
| People on a deal | 50 | ”A deal can have at most 50 people.” | Read a deal |
| Rules on a deal | 20, each up to 300 characters | ”A deal can have at most 20 rules.” | Read a deal |
| Documents on a deal | 100, each with up to 20 dates | ”A deal can have at most 100 documents.” | Read a deal |
| A deal’s amount | 0 to 1,000,000,000,000 | ”An amount can’t be below zero.” or “That amount is more than a deal can hold.” | Open a deal |
| Playbooks in use | 100 | ”A squad can have at most 100 playbooks in use. Archive one it no longer uses first.” | Open a deal |
| Steps in a playbook | 60, each due 0 to 365 days after the deal opens | A longer playbook is refused. | Open a deal |
| Deals in a column of Whose move | 60, fewer when the deals are large | A button with how many more opens List, for example “12 more”, or “At least 12 more” when Squad stopped counting. | Find a deal |
| Open deals counted on Whose move | 511 on each side | Past it, the counts say “or more” and the column totals hide. | Find a deal |
| A deal’s history on its page | The newest 200 lines, and up to 100 decisions | ”Some of this deal’s documents and history are too large to show here.” | Read a deal |
| Promises, Decided, and Documents on a deal | The first 5 each | All and the number shows the rest. | Read a deal |
| A long history line | 400 characters or 6 lines | Read it all opens the whole entry. | Read a deal |
| Marks on a deal’s bar on Whose move | 40 | Past 40, each mark stands for several steps. | Find a deal |
| Deals on a person’s page | The newest 100 | Older deals are only on Deals. | Read a person |
| A nudge for the other side’s late step | One, a day after the step’s day | The deal’s teammate gets a task to draft it. Only when a teammate looks after the deal. Never to someone marked do not contact. A new day can bring a new nudge. | What your squad does with deals by itself |
| A renewal step | 30 days before a document’s renewal date, or at once when the date is closer | The step goes to the deal’s teammate, else the person in your squad who looks after the deal, else the owner. | What your squad does with deals by itself |
| Squad checks for steps, nudges, renewals, and follow-ups | Every 10 minutes, up to 100 steps at a time | A backlog goes on at once. Each teammate is woken once with everything due. | What your squad does with deals by itself |
| A step moved or added on the web | Due at 9:00 on the day that you pick, in your browser’s time. The deal’s history names that day. | Not applicable. | Work a step |
| Counts on Home | Exact up to 1,000 | Past 1,000, the count says “1,000 or more”. | Home: what’s next |
| A deal gone quiet | 14 days with no touch from its people | It shows under Waiting on them on Home, the 10 quietest. “And [n] more deals have gone quiet.” says the rest. | Home: what’s next |
| Your steps on Home | Up to 20 | ”And [n] more of yours after these.” | Home: what’s next |
| A teammate’s steps under Your squad is on it | 3 due today, for each teammate | ”[name] has [n] more steps due today.” | Home: what’s next |
| Teammates named in Home’s sentence | The first 2 | Not applicable. | Home: what’s next |
| A renewal in Home’s sentence | The next one within 60 days | Not applicable. | Home: what’s next |
| This week on Home | The 7 days after today, up to 8 rows | ”And more this week.” | Home: what’s next |
| Since you last looked on Home | The newest 5 | A visit within 30 minutes of the last counts as the same visit. | Home: what’s next |
| Your due steps in Needs you | The first 50 | Show all and the number steps of yours lists up to 500. Past 500, a line says how many more are due. | Your steps in Needs you and Today |
| Your due steps on Today | The first 3 | See all and the count opens Needs you. | Your steps in Needs you and Today |
Payment cards
| Item | Value | What happens at the limit | More |
|---|---|---|---|
| Approval of a purchase | The card vault’s own deadline, which the bell states in minutes (“Approve or decline within N minutes”). 15 minutes when the vault sets none, and the bell then says “Approve or decline it.” | The purchase shows Not approved in time: “Nobody approved it in time, so nothing was paid.” | Let your teammates pay with your card |
| Checkout window of a purchase | 45 minutes from the start | Closed before approval: Not approved in time. Closed after approval: Payment not confirmed, or Not confirmed for a checkout that charges nothing. | Let your teammates pay with your card |
| A teammate’s request that you add a card | Open for 7 days. Each teammate has at most one open request to each person, and asking again restarts the 7 days. | A card added later does not wake the teammate. | Let your teammates pay with your card |
| Cards that can pay | Visa, Mastercard, American Express, Discover, and JCB | Other cards are listed but cannot pay. | Let your teammates pay with your card |
| Open purchases for each teammate | 1 | The teammate’s next purchase is refused until it finishes or cancels the open one. | Let your teammates pay with your card |
| A later charge that a teammate names for a purchase | 160 characters | Longer text is cut at 160 characters. | Free trials and checkouts that charge nothing |
| A purchase whose result is not known | Blocks a new purchase by that teammate for 24 hours after its checkout window closed | The teammate is told when a new purchase is possible. | Let your teammates pay with your card |
| Purchases listed in the Wallet | The newest 50 | Older purchases are not listed. | Let your teammates pay with your card |
Form cards
| Item | Value | What happens at the limit | More |
|---|---|---|---|
| Fields on one form card | 1 to 40 | The card is refused, and the teammate is told why. | Fill a form that a teammate sends you |
| Time to fill a form card | 30 minutes | The card shows Expired: “This form request lapsed. Ask your teammate to send it again.” | Fill a form that a teammate sends you |
| Text in one field | 4,096 characters | Longer text is cut. | Fill a form that a teammate sends you |
| Form cards that wait at once on your cloud computer | 20 | The teammate’s next form card is refused until one of them is filled, declined, or expired. | Fill a form that a teammate sends you |
Squad for Mac
These are the numbers that the app uses, and the limits on what teammates can ask for on your Mac. See Get started with Squad for Mac.The app and navigation
| Item | Value | What happens at the limit | More |
|---|---|---|---|
| Mac that Squad for Mac runs on | macOS 14.0 or later, with Apple silicon | The app does not run on an older macOS or on a Mac with an Intel processor. | Get started with Squad for Mac |
| How long the web dashboard counts you as a person who uses Squad for Mac | 30 days after the app last reported that it opened on your account. The app reports each time it starts, and when you sign in, from version 1.0.76. Squad records a report from the same version at most once every 12 hours. | After 30 days, a browser on a Mac offers you the app again, and dashboard links stay in the browser. | Squad for Mac on the web |
| Dashboard link from outside that opens in Squad for Mac | Only in the first 15 seconds after the page started to load | Later, the page stays in the browser. | Squad for Mac on the web |
| Link that opens another of your squads in Squad for Mac | Says “[squad] is taking a while to open. The link opens there once it does.” after 15 seconds | The link still opens when the squad opens. | Troubleshoot Squad for Mac |
| Pins shown in the sidebar | The first 3 | Show all with the count shows the rest. Show fewer goes back. Squad remembers the choice. | Pin items to the sidebar |
| Saved pins | 32,000 characters of saved pin data | Squad says “You have too many pins to save. Unpin a few first.” | Pin items to the sidebar |
| Places that Back remembers | 100 | The oldest places are dropped. | Keyboard shortcuts |
| Text size | 7 steps, from 85% to 145%. The default is 100%. | Bigger or Smaller is off at the largest or smallest size. | Keyboard shortcuts |
| Command palette with nothing typed | The first 3 questions from Needs you | Type to search, or open Needs you. | Search and keyboard shortcuts |
| Command palette results | 5 each for Go to, Needs you, People, Projects, Tasks, Docs, and Email. 4 each for Help and ideas and Apps. 40 in all. The palette searches the first 20 questions, 400 tasks (open ones first), 300 docs, and the 100 most recent emails. | Type more words to narrow the results. | Search and keyboard shortcuts |
| Check for updates | Every hour, with Check for updates automatically on | Not applicable. To check now, choose Check for Updates…. | Settings, notifications, and updates |
| Crash and freeze reports kept on the Mac | The newest 20. A report is dropped after 3 failed sends. | When a new report comes in, the oldest is dropped. With Share usage and crash reports off, none are kept. | Settings, notifications, and updates |
| Freeze that counts as “stopped responding” | More than 3 seconds | If Squad is closed while it is frozen this long, a notice says “Squad stopped responding last time, sorry about that.” the next time Squad opens and you are signed in. A freeze that ends by itself shows no notice. | Troubleshoot Squad for Mac |
Today and Needs you
| Item | Value | What happens at the limit | More |
|---|---|---|---|
| Items that need you on Today, including email drafts and escalations | The first 3 | What only you can fix, and suggested triggers, show in full above them. The link under them opens Needs you. | Today |
| Undo after you answer on Today | The 2 most recent answers, each for 45 seconds | The Undo button goes away. | Today |
| Low disk card, set aside with the X | 24 hours, on this Mac | The card shows again. A full disk shows at once and cannot be set aside. | Today |
| Memory card, set aside with the X | 24 hours, on this Mac | The card shows again while teammates still keep waiting. | Today |
| Assigned to you on Today | The 5 open tasks assigned to you that changed most recently | Open Tasks for the rest. | Today |
| Today so far or Yesterday on Today | 6 teammates, read from the latest 50 activity items | Other teammates are not listed. See all activity opens Activity. | Today |
| Routines in Today’s routines on Today | The first 5 | A line says “One more runs today.” or how many more run today. See all routines opens Routines. | Today |
| Ideas for your squad on Today | The first 14 days of a squad | After that, the ideas show only when nothing waits for you and nobody is working. | Today |
| Answers under Just answered in Needs you | The 2 most recent, each for 45 seconds | The answer leaves the strip. Undo it from Show resolved instead. | Answer what needs you |
| Over a day filter in Needs you | Questions open for more than 24 hours | The filters show only when at least one question is that old. | Answer what needs you |
| Over 30 days filter in Needs you | Questions open for more than 30 days | Shows only when such questions exist, with a card that suggests Review them. | Answer what needs you |
| Clear all for questions in Needs you | Shows with 2 or more open questions that you did not set for later | For the owner and Administrators only, in the ⋯ menu. | Answer what needs you |
| Your due steps in Contacts in Needs you | The first 50 | Show all and the number lists up to 500. Past that, a line says how many more are due. | Answer what needs you |
| Your due steps in Contacts on Today | The first 3, after the questions | See all and the count opens Needs you. | Use Today |
| Later on a question, Pick a time… | From 2 minutes ahead to 1 hour less than 60 days ahead, starting at tomorrow at 9 AM | The picker offers no time outside this range. | Set a question for later on the Mac |
Chat and projects
| Item | Value | What happens at the limit | More |
|---|---|---|---|
| Conversations in a teammate’s list | 40 at a time | Show older conversations loads 40 more. | Chat with your teammates |
| Messages in a conversation with one teammate | 200 at a time | Show earlier replies loads 200 more. | Chat with your teammates |
| New replies before a conversation opens at the newest instead of at the first unread | More than 10 | The conversation, in the main window or the notch, opens at the newest reply. | Chat with your teammates |
| Messages in a group chat | The latest 200. The Squad chat shows the latest 100. | Older messages are not shown. | Chat with your teammates |
| Group chats in the sidebar | The first 5 | All group chats with the number of others shows the rest. Show fewer goes back. The open group chat always keeps its row. | Chat with your teammates |
| Between teammates in the sidebar | 8 when you open it. The count stops at 50 and then shows “50+”. | Show with the number more shows the rest. | Chat with your teammates |
| Your sent messages that ↑ can bring back in the composer | The last 50 in any conversation, the Squad chat included | Older messages are not offered. | Chat with your teammates |
| Conversation name in the header | 80 characters | Longer names are cut to 80 characters when you save. | Chat with your teammates |
| Helpers that join one “Asked” line | Each asked within 15 minutes of the one before, by the same teammate, with nothing between them. The teammate is the one that asked the helper. | A later helper, or one after a message, starts a new line. | Chat with your teammates |
| Helper names on one “Asked” line | Up to 3 different names, each once | Helpers whose names are not shown are counted, for example “and 2 more”. A helper with no name is always counted, never named. A helper with the same name as a shown one is not counted again. | Chat with your teammates |
| Unsent drafts in the composer | 30 days after you last typed in it, and at most 200 drafts per squad on this Mac | Older drafts are dropped. Past 200, the oldest drafts are dropped. All drafts are dropped when you sign out. | Chat with your teammates |
| Project name | 80 characters | Squad refuses a longer name: “A project’s name can be at most 80 characters.” | Group conversations into projects |
| A project’s notes that every teammate reads first | 2,000 characters | Squad refuses longer text: “What a project is about can be at most 2000 characters.” | Group conversations into projects |
| Open projects in a workspace | 200 | Squad says “You have 200 open projects. Archive one before making another.” Bring Back is refused with “You have 200 open projects. Archive one before bringing this one back.” | Group conversations into projects |
| Projects in the sidebar before All projects | 5, plus the open one | All projects shows the rest. | Group conversations into projects |
| Archived projects in the sidebar | 100 at a time | Show older loads the next 100. | Group conversations into projects |
| Conversations on a project’s page | 200 direct conversations and 200 group chats | Older ones are not listed. | Group conversations into projects |
Tasks, email, docs, and contacts
| Item | Value | What happens at the limit | More |
|---|---|---|---|
| Cards in a column on Tasks | The first 12, or 5 when the columns stack | Show all with the count shows the rest. | Track work on Tasks |
| Finished tasks in Done on Tasks | 200 at a time | Load older finished tasks loads 200 more. | Track work on Tasks |
| No progress for mark on a task card | A task in Working on it, not ongoing, with no update for more than 2 days | The card shows No progress for and the number of days. | Track work on Tasks |
| Rows in Archived and Trash on Tasks | 100 at a time | Show older tasks loads 100 more. | Track work on Tasks |
| Steps of tasks | From version 1.0.96 | An older version shows each step as a card of its own, with no Steps list. | On Squad for Mac |
| Count of the questions that stay after a clear | Waits up to 4 seconds | The message after the clear leaves out the questions that someone else set for later. | Needs you |
| Notes shown on a task’s page | The newest 50 | Show earlier notes shows 50 more each time, back to the first note. The line about who has not seen a note shows only on the newest 51 notes. | A task’s page on the Mac |
| Emails in the list on Email | The newest 100, plus every draft and escalation that waits for review, every scheduled send, and the newest 100 unread emails | Older emails are not listed. The unread count, and the unread emails that the list adds, stop at 100. | Give a teammate an email inbox |
| Docs on Docs | 24 at first | Show more docs shows 24 more. | Find and manage your squad’s docs |
| Archived docs on Docs | 50 at a time | Load more shows 50 more. | Find and manage your squad’s docs |
| Search docs on Docs | The first 140 characters of a doc’s text, with Markdown marks removed, plus the title, the kind, and the author | Words later in the doc do not match. Search for words in the title instead. | Find and manage your squad’s docs |
| Rows on People, in each Review list, and on the deals List and Closed in Contacts | 50 at first | Show more shows 50 more. | Contacts on Squad for Mac |
| Deals in a column of By whose move in Contacts | The first 12 | A button with how many more opens List. The columns sit side by side when the deals area is about 900 points wide or more. | Contacts on Squad for Mac |
| People in a stage’s column on a pipeline’s page in Contacts | The first 6 | A button with how many more opens People for that stage. | Contacts on Squad for Mac |
| Pipelines on Home in Contacts | 8 | All and the number pipelines opens Pipelines. | Contacts on Squad for Mac |
| Results of Search people and companies | 30, after 2 or more characters | More matches are not listed. Type more of the name. | Contacts on Squad for Mac |
| Entries in History on a contact’s page | The newest 20 | Show earlier shows 30 more. | Contacts on Squad for Mac |
| A follow-up or a step’s date set on the Mac | 9:00 on the day that you pick, in your Mac’s time | Not applicable. | Contacts on Squad for Mac |
Routines, history, and activity
| Item | Value | What happens at the limit | More |
|---|---|---|---|
| Up next on Routines | The next 4 runs | Not applicable. | Schedule recurring work with routines |
| Search routines on Routines | Shows when routines and triggers number more than 12 | Not applicable. | Schedule recurring work with routines |
| Routines in the Runs continuously row of Routines > Week | The first 30 | A link with the number and more switches Routines to List. | Schedule recurring work with routines |
| How far back History goes | 31 days | Older runs are not shown. | See what your squad did |
| Schedule view in History | The last 3 days at a time | Load older runs moves back 3 days, within the 31 days. | See what your squad did |
| Runs that History lists for one day | 2,000 | The earliest runs of that day are not shown, and a notice says so. | See what your squad did |
| Activity on Activity | 50 at a time | Load older activity loads 50 more. | See what your squad did |
| New rows on Activity on the first visit | What happened in the last 4 hours | After that, rows are new since your last visit. | See what your squad did |
Teammates and notifications
| Item | Value | What happens at the limit | More |
|---|---|---|---|
| Sections on a teammate’s About | Lately: 6 lines. Waiting on: 4. Tasks: 5 open tasks. Routines: 6. | See all tasks and See all routines open the full lists. | Add, change, and pause teammates |
| How often for Check-ins on a timer | The interval already set for the teammate. With none set, the squad’s default check-in interval, or else 30 minutes (1 hour when the squad’s Claude account is connected by sign-in). After check-ins were turned off on the Mac, Every 15 minutes. | Pick another interval in How often. | Add, change, and pause teammates |
| Deliver the summary at | 9 AM, 12 PM, 4 PM, or 6 PM. The default is 4 PM. | Held questions arrive as one summary at that time. | Settings, notifications, and updates |
| Friday recap | Friday at 5 PM, in your Mac’s time | Not applicable. | Settings, notifications, and updates |
The notch, the menu bar, and voice
| Item | Value | What happens at the limit | More |
|---|---|---|---|
| Other squads that the notch counts | 10 | Squads past the first 10 are not counted in the notch, the menu bar, the Dock, or the squad switcher. | Use the notch and the menu bar, The Dock badge |
| Other squads in the notch’s peek | 2 | At most 2 other squads with something for you show in the peek. The others still count in the notch. | Use the notch and the menu bar |
| Asks in the menu bar | The first 4 | Open Needs you for the rest. | Use the notch and the menu bar |
| Snooze until tomorrow | Until 8:00 the next morning, in your Mac’s time | The notch turns back on. | Use the notch and the menu bar |
| Question card that the notch opens | Closes after 9 seconds, or 4 seconds after the pointer leaves | The question still waits in Needs you. | Use the notch and the menu bar |
| Reply card that the notch opens | Closes after 7 seconds. A late spoken answer, with Play, stays 45 seconds, only while the notch is on. Pointing at the card keeps it open. | The reply stays in the chat. A late spoken answer also stays in its notification. | Use the notch and the menu bar, Delegate, talk, and use Siri |
| Options as buttons on a notch question card | Up to 3 | A decision with more options shows Open in Squad, then Later when you can set it for later, or else Not now. | Use the notch and the menu bar |
| Question cards that wait for the notch | 5 | The oldest waiting card drops out of the queue. In a meeting or a snooze, later ones are only counted. The questions still wait in Needs you. | Use the notch and the menu bar |
| Listening after ⌃⌥Space | Stops by itself after 60 seconds | What you said so far is sent. | Delegate, talk, and use Siri |
| Today’s voice conversation | Turns over at 4 AM. A voice conversation used in the last hour continues. | A new voice conversation starts. | Delegate, talk, and use Siri |
| Spoken answer that is read aloud | Arrives within 15 minutes of your question | A later answer is not read aloud. It waits for you to select Play. | Delegate, talk, and use Siri |
| Spoken question that waits for its answer | 3 hours | After that, the app stops waiting. The answer is still in the chat. | Delegate, talk, and use Siri |
Mac access
| Item | Value | What happens at the limit | More |
|---|---|---|---|
| Request that you do not answer | Expires 10 minutes after the teammate asks | The teammate is told that you did not answer, and continues without it. | Let your teammates use your Mac |
| Mac access request at the top of the screen that you do not answer | 40 seconds, or 20 seconds after your pointer leaves it | The request moves to a notification. | Let your teammates use your Mac |
| Approved request that your Mac does not finish | Fails 20 minutes after the teammate asked | The request fails, and the teammate is told that your Mac did not finish it. | Let your teammates use your Mac |
| Requests from one teammate | 30 in any 60 minutes | Further requests from that teammate are refused until fewer than 30 of its requests fall in the last 60 minutes. | Let your teammates use your Mac |
| Requests waiting for your answer | 20 per workspace | Further requests are refused until you answer some. The teammate is told to wait for those to be answered. | Let your teammates use your Mac |
| File that a teammate reads | 19 MB | A larger file is not sent, and the teammate is told that the file is over the limit. | Let your teammates use your Mac |
| Text file that a teammate writes | 256 KB, counted in UTF-8 bytes | Longer text is refused before it reaches your Mac. The teammate is told to split it into smaller files or share it as a doc. | Let your teammates use your Mac |
| Screenshot of your screen | 10 MB | A larger screenshot is not sent. | Let your teammates use your Mac |
| Text that comes back in the reply | Up to 256 KB of UTF-8 text | A larger file, or a file that is not text, is saved as a file in the teammate’s workspace. | Let your teammates use your Mac |
| Folder listing | 200 entries | The listing stops at 200 entries. | Let your teammates use your Mac |
| Macs per workspace | 10 | Another Mac is refused until you remove one. | Let your teammates use your Mac |
| Shared folders per Mac in one squad | 100 | Another shared folder is refused until you stop sharing one. | Let your teammates use your Mac |
| Mac counts as connected | Seen by Squad in the last 2 minutes, with Let your squad use this Mac on | Teammates usually do not get the Mac request tools until the Mac is connected again, or a request says that your Mac is not connected. | Let your teammates use your Mac |
| Results of a request | Removed 24 hours after the request finishes | Squad keeps the request’s reason and outcome. A file that the teammate saved in its workspace stays there. | Let your teammates use your Mac |
| Recent requests on the Mac access page | The newest 20 | Older requests are not listed. | Let your teammates use your Mac |
Research tools
These caps protect you from a teammate that repeats research calls in a loop. For what each research tool does and costs, see Research tools reference.| Item | Value | What happens at the limit | More |
|---|---|---|---|
| Research calls in one teammate session | 25 in 10 minutes | Further calls are refused until the window moves on. | Research tools |
| Research calls in the squad | 60 per minute | Further calls are refused until the minute moves on. | Research tools |
| Time for one call to a research tool with a time limit | 120 seconds. Reddit Subreddit and Search calls with a time window: 180 seconds for the first try, and 270 seconds in all with a second try. Product Hunt: Launches: 180 seconds. Reddit Post comments: 110 seconds. | A call that found results by then returns them, and you pay for those results. A call that found nothing fails and costs 0 credits. A Reddit Subreddit or Search call with a time window that ran out of time with nothing found in its first try runs once more with the time left, if at least 60 seconds are left. | When a call fails |
| Items in one research result | 50 by default, 500 at most | Some tools set their own default. A teammate can ask for more items, up to 500. Product Hunt: Launches returns at most 25, whatever the teammate asks for. | Research tools |
Triggers
| Item | Value | What happens at the limit | More |
|---|---|---|---|
| Size of one webhook request | 256 KB | The request is refused and not stored. The sender gets “The body is larger than 256 KB.” | Triggers |
| Events for one trigger | 60 a minute, with bursts of up to 120 | Requests past the limit are refused. The sender gets “Too many events. Slow down and retry.” and a time to wait. The trigger’s page counts the refused requests of the day. | Triggers |
| Events for all triggers in a workspace | 300 a minute | Same as above. | Triggers |
| Most runs per day | 100 by default. You can set 1 to 1,000. Counted per day in UTC. | Later events of the day are kept as “Not run: the daily limit was reached”. Run now, Retry, and Send test event still run. | Triggers |
| Runs of one trigger at the same time | 1 | Events that arrive during a run wait for the next run. | Triggers |
| Events in one run | Up to 25 events. A run takes more events only while their payloads stay within 48,000 bytes in total. | The other waiting events go in the next run. A single event larger than 48,000 bytes runs alone. | Triggers |
| Payload that the teammate gets in the run, for each event | 48,000 characters divided by the number of events in the run, and at least 2,000 | A longer payload is cut, and the teammate is told how to read the rest. | Triggers |
| Tries to wake the teammate | 6, after waits of 1, 5, 15, 30, and 60 minutes | The event shows “Could not wake the teammate” with Retry. | Triggers |
| Wake with no run | 30 minutes | When the teammate was woken but no run started, the event shows “Teammate woken, no run started” with Retry. | Triggers |
| Event history and payloads | 30 days | Older events and their payloads are deleted, and they no longer show on the trigger’s page. | Triggers |
| Events listed under Latest events | The newest 50 | Older events are not listed. | Triggers |
| Age of a signature (Stripe, Standard Webhooks) | 5 minutes | The request is refused with “The signature timestamp is too old.” | Triggers |
| ”Squad refused a request” note on the trigger’s page | Shown for 1 day after the last refusal | Refusals are noted at most once a minute. | Triggers |
| Name | 80 characters | The field accepts no more text. | Triggers |
| What the teammate does with each event | 8,000 characters | The field accepts no more text. | Triggers |
| Only send these fields (optional) | 20 paths, up to 200 characters each | ”Pick at most 20 fields.” | Triggers |
| Pasted signing secret | 500 characters | ”That secret is too long.” | Triggers |
| Settings of an app event | 8,000 characters | ”The event settings are too large.” | Triggers |
| Send the result to a URL (optional) | 2,048 characters, https://, a public host name | ”The URL is longer than 2,048 characters.” Other addresses are refused with a reason, for example “The URL must start with https://.” | Triggers |
result in the callback body | A summary of the teammate’s final reply, up to 2,000 characters | A longer reply is cut. | Triggers |
| Tries to send the result to your URL | 3, after waits of 1 and 5 minutes. Each try waits up to 10 seconds for an answer. | The event says “The result was not delivered to your callback URL” and the reason. | Triggers |
| Suggestions from teammates that wait for approval | 20 in a squad | Teammates cannot suggest more until the owner or an Administrator turns some on with Turn it on, or dismisses them with Dismiss. | Triggers |
| An app’s event setup that fails because the app did not answer | 3 more tries, after 1, 5, and 30 minutes | The trigger pauses and says why. Turn it on again to retry. | Triggers |
Cloud computer disk
| Item | Value | What happens at the limit | More |
|---|---|---|---|
| Disk check | About every 30 minutes, when no teammate is in the middle of a reply | A busy computer is checked later. | Your cloud computer’s disk is low or full |
| Low disk | Less than 5 GB free | An amber banner says how much space is left, for example “Your cloud computer has 4 GB of space left.”, and the owner gets a bell notification. The banner goes away when at least 6 GB is free. | Your cloud computer’s disk is low or full |
| Full disk | Less than 1 GB free | A red banner says that the computer is out of space, and the owner gets a bell notification and an email. It stops counting as full when at least 1.5 GB is free. It then counts as low, or as fine when at least 6 GB is free. | Your cloud computer’s disk is low or full |
| Hide for a day | 1 day, in one browser | The low-disk banner shows again at the first new disk reading after the day, within about 6 hours. A full disk cannot be hidden. | Your cloud computer’s disk is low or full |
Cloud computer memory
| Item | Value | What happens at the limit | More |
|---|---|---|---|
| Memory check | With the disk check, about every 30 minutes | Squad reads how often teammates waited for memory before their runs started. | Your cloud computer keeps running low on memory |
| Memory banner | At least 1 wait in the last 6 hours, and 1 wait of 2 minutes or more in the last day. The number of waits does not count. | An amber banner says how many times teammates waited for memory in the last day, and how long the longest wait took. It goes away when the waits no longer meet this rule, or 12 hours after the last check. Squad for Mac shows its card by the same rule. | Your cloud computer keeps running low on memory |
| Why teammates waited, on the memory banner | A wait counts as short on memory when it began with less than 2,048 MB free. When fewer than half of the day’s waits did, the banner says that most waits came when many teammates started at once. Otherwise it treats the computer as short on memory. | The words after the banner’s sentence and its Ask button follow the cause. | Your cloud computer keeps running low on memory |
| Waits that Squad counts | The last 500 waits on your cloud computer | When all 500 are from the last day, the banner says “500 or more times”. | Your cloud computer keeps running low on memory |
| Hide for a day on the memory banner | 1 day, in one browser, for one squad | The banner shows again at the first reading after the day. With no new waits, that can take up to 6 hours more. | Your cloud computer keeps running low on memory |
Notifications
| Item | Value | What happens at the limit | More |
|---|---|---|---|
| Notification emails | 1 per 60 seconds for each person | An email that comes less than 60 seconds after the last one waits and is sent later. After 10 waits, it is not sent. The notification still shows in the bell. | Choose your notifications |
| Squad name at the start of a notification email’s subject | The first 40 characters, on one line | A longer name is cut after 40 characters, with no mark. Line breaks in the name become spaces. | Choose your notifications |
| Weekly email | Mondays at 14:00 UTC | Sent only when the Email switch of Your week, every Monday is on. | Choose your notifications |
| Notifications in the bell | Newest 8 | The owner’s bell lists unread notifications only. Other people’s bells also list read ones. View all opens Activity, with the count when more than 8 are loaded. | Choose your notifications |
| Activity on Activity | 50 at a time | Load older activity loads 50 more. | See what your squad did |
| New rows on Activity on your first visit in a browser | What happened in the last 4 hours | After that, rows are new since your last visit. | See what your squad did |
| Message shown in a mention notification | At most 140 characters, on one line | A longer message is cut and ends with …. | Mentions |
| Email about a mention that you have not seen | 10 minutes after the mention | One email per mention notification, only if you have not opened the place or read the notification by then. There is no setting. | Mentions |
| Teammates going back and forth in the owner’s bell | One row for each task while an earlier row about that task is unread. After you read it, a new row comes at the earliest 24 hours after the last one. | Opening the row, Mark all read, or opening the task marks it read. | Choose your notifications |
| Updates in What’s new that count as unread the first time you open Squad | The last 14 days | Older updates count as read. This applies only when your account has no saved reads and the browser has none. | Get help |