Skip to main content
This page answers the questions that people ask before they buy Squad. Each answer is short and links to the page with the details. For more short answers, see Frequently asked questions.

Your AI accounts and Claude Code

Your teammates run on the AI accounts that you connect, and your provider bills you for model usage. Squad does not sell model usage. You can connect more than one provider, for example a flat-rate plan for most work and a pay-per-use key for smaller jobs. See Connect your AI subscription.

How your Claude Code setup token travels

Squad connects Claude Code with a setup token. This is the path of the token:
  1. You create it on your own computer. You run Claude Code’s setup-token command in a terminal, and you sign in to Claude in your own browser. Squad never sees your Claude password or your sign-in. Squad does not offer a Claude sign-in on your cloud computer.
  2. You paste it in Squad. You paste the token in the Add Claude Code token window, right after setup or on Settings > AI, and click Connect.
  3. It passes through Squad’s server. The token goes through Squad’s server on its way to your cloud computer, over encrypted connections. The server passes it on and keeps no copy. The token is not saved in Squad’s database, and Squad keeps it out of its logs.
  4. It is stored on your cloud computer only. Squad checks the token with a real test turn on your cloud computer, then stores it there: in Claude Code’s own credentials file, and in your squad’s list of Claude Code accounts on that computer. Squad uses that list to switch to your next Claude Code account when one reaches its usage limit.
  5. Disconnecting deletes it. When you disconnect a Claude Code account on Settings > AI, Squad deletes its token from your cloud computer. Squad does not let you disconnect the account that your teammates use now while you have other Claude Code accounts. Switch to another account first.
For the steps, see the Claude Code tab in Connect your AI subscription. To disconnect, see Replace or remove an account.

How Claude Code runs

Claude Code runs on your cloud computer as Anthropic ships it, unmodified. No other squad uses your cloud computer. Squad gives Claude Code its tools through Claude Code’s own options for tools and plugins, and keeps the installed Claude Code at or above the version that Squad’s models need. Claude Code runs on your Claude plan’s included limits and never bills extra usage. When every Claude Code account that you connected reaches its usage limit, Squad shows when your teammates pick up again. See Claude Code reached its usage limit.

Whose terms apply

Squad has no separate agreement with Anthropic for Claude Code. Claude Code runs with your own Claude plan. For what your plan allows, read Anthropic’s terms for your plan.

What Squad looks after, and what is left to you

What Squad does without you

  • Keeps your cloud computer running. Squad checks the cloud computer on a schedule and starts its services again when they stop. It keeps the computer up to date and applies security updates.
  • Watches for work that stops moving. When a task has no update for a long time, Squad first asks the teammate for progress. If the task still does not move, Squad asks you one question with three choices: nudge the teammate, park the task, or leave it as it is. See Answer a question about a stuck task and Stuck tasks.
  • Picks up work that a restart cut off. Some failed runs run again by themselves. See Which runs retry automatically.
  • Tells you when something needs a person:
    • When an app’s sign-in ends, its account on the Apps page shows Needs reconnecting, and the teammate names the account and who can reconnect it. See Connect apps.
    • When Claude Code is signed out, a banner shows on every screen, Today and Needs you show it first, and the owner gets one email. See An expired AI connection.
    • When every Claude Code account reaches its usage limit, a line on every screen says when your teammates pick up again.

What is left to you

  • Signing in again to your own accounts when an app or your AI provider asks for it. Only you can sign in to your accounts. Squad tells you which account it is and where to reconnect it.
  • Answering the questions and approvals that your teammates bring you. See Answer what needs you.
  • Your AI plans and their limits. For more room, connect another account or set models to try next. See Choose models and manage AI accounts.
For what to check when a teammate does not reply, see Fix a teammate that is stuck or failing and See what your squad did. If something breaks on Squad’s side, it is Squad’s to fix. Email support@squad.so. See Get help.

Approvals for actions in connected apps

Some of Squad’s own actions wait for you. A purchase with your card is not paid until you approve it. See Approve a purchase. An email reply that a teammate drafted for review waits until the owner or an Administrator sends it. See Review an email that waits for you. For approval by a Collaborator, have teammates ask a question instead, as below. When a person answers a question, the teammate carries on for that person, with that person’s access. So for a Collaborator who approves, share the connected app account that the teammate uses with them. An email from a teammate’s Squad inbox still needs the owner or an Administrator to send it. There is no switch that holds every action in a connected app or an MCP server for approval. These are the controls:
  • Access levels. For each account of an app from the catalog, you choose what teammates can do, for example Read-only. You can narrow or block one teammate. Squad checks every call against these levels. See Choose an access level and Limit a single teammate. Recommended apps, such as SiteGPT, have no access levels and no per-teammate limits. See Recommended apps.
  • MCP server switches. For an MCP server that you add, you turn the whole server or single tools on or off. These switches apply to the whole squad, not to one teammate. See Turn tools on or off.
  • Ask for approval first. Tell your teammates to ask before they act. A teammate can address the question to the person who approves, so only that person is told. See Questions for one person. The person answers on the web, in Squad for Mac, or in Squad for iPhone and iPad, where a notification about one yes-or-no question shows Approve and Deny. See Notifications on iPhone and iPad. The teammate carries on when the person answers.
Ask your chief of staff
Such an approval rule is an instruction that your teammates follow. The access levels are the limits that Squad enforces on every call. Telegram, Discord, and Slack do not show Squad’s questions or their buttons. A Telegram, Discord, or Slack bot does not know a person’s role in Squad, and the Telegram main bot answers only the owner. For an approval, the person answers in Squad: on the web, in Squad for Mac, or in Squad for iPhone and iPad. If someone answers a teammate in one of these chat apps instead, the teammate can close the ask and quote their exact words. See What teammates can do with questions and Channels.

Apps that are not in the catalog

You can add a service’s own hosted MCP server, with the service’s sign-in page or with a key from that service. Some services let only the apps that they approved sign in. For those, use an API key or an access token from the service. See Add an MCP server or an API key.

A partner who uses only a phone

Invite your partner to your squad as a Collaborator. A Collaborator chats with teammates, works on tasks and docs, and answers questions, including approvals. Seats for people are a paid add-on. See Choose a role and Seats for people. On a phone, your partner can use:

A private GitHub repository

Squad has no built-in sync with a private repository. Skill packs come only from public GitHub repositories. See Add a pack from GitHub. Your teammates can work with a private repository in two ways:
  • Connect GitHub on the Apps page. Teammates then work in your repositories through the GitHub app, at the access level that you choose. Read + write code lets them change code and branches. See the GitHub manual.
  • Store an access token as a custom integration. Your teammates can then clone the repository onto your cloud computer, pull it, and push changes with the token. To read only, give the token read access to that one repository. To save docs back to the repository, the token needs write access. See Add a custom integration with an API key.
To pull the repository every day, give a teammate a routine that does it. See Run work on a schedule. Squad does not load the files of a repository as your teammates’ instructions or skills by itself. Tell your teammates which rule files to follow, for example in the routine’s instructions. The keys that you save in custom integrations work for anyone in your squad. To keep a GitHub account to yourself, connect it on the Apps page and do not share it. See The computer is shared with your squad.

Where your data is

Your cloud computer and the dashboard’s database run in different regions:
  • Your cloud computer runs in the EU. It holds your teammates’ working files, your Claude Code token, and the values that you save for custom integrations. See Watch or take over a teammate’s computer.
  • The dashboard’s database runs in the US, in US East (N. Virginia). It holds your tasks, docs, chat, contacts and deals, run history, and settings.
Some features also use other services that keep their own copy of what they need, for example your squad’s memory and the apps that you connect.

Leaving and exporting

The owner and Administrators who work with every teammate can prepare a backup of your squad on Settings > Squad > Backup. Squad prepares it on its servers and emails you when you can download it, as one JSON file. It holds your conversations with teammates, email, questions, tasks, docs, runs, contacts, deals, pipelines, playbooks, projects, triggers, all activity and Squad chat, and, from your cloud computer, your routines, skills, memory, and each teammate’s files and settings. In the owner’s backup, saved secrets are named, never their values. It does not hold payment cards or the files of attachments. See Back up your data. A cancellation takes effect at the end of your billing period. After the end date, your squad is locked and scheduled for deletion, and your teammates stop working. Back up your data before then. See Cancel your subscription and What happens at the end date.

Demos and trying Squad

Squad has no demo calls and no booking link. To see whether Squad fits your work, sign up and try it with your own tasks. Your first payment has a 7-day money-back guarantee. See Get a refund. For the plan price, see What Squad costs. To start, follow Get started. For a question that the docs do not answer, email support@squad.so. A person on the Squad team answers. See Get help.