Skip to main content
Thirty-three commands across thirteen areas. All of them assume you have run squad auth login and squad workspace select. See Squad CLI for setup.
squad --help also lists squad research list and squad research create. They call operations this platform does not serve and return an error. They are left out of the reference below for that reason.

Display IDs

Most commands take a short display ID instead of a UUID. UUIDs work everywhere a display ID does.

The commands

squad workspace update takes --name, --description, --mission-statement and --logo-url.Use squad workspace members to find the user ID you need for squad action update --assignee.
Raw feedback. See Signals for what they are and where they come from.squad signal list flags: --source, --type, --sentiment, --cluster <uuid>, --since <iso>, --until <iso>, --include-dismissed, --limit, --offset.squad signal similar takes --limit (default 5, max 20).squad signal ingest takes either a single item or a file:
--file points at a JSON array of 1 to 50 signal objects. Other flags: --title, --occurred-at <iso>. Content is deduplicated server-side, then clustered and distilled asynchronously.
squad signal dismiss deletes the signal. It cannot be recovered. --reason records why in the command output.
Recurring themes across signals. See Signal clusters.squad cluster list flags: --type, --include-unlabeled, --limit, --offset.
squad insight list flags: --goal <goalId>, --category, --min-score, --status, --limit, --offset.squad insight update flags: --category, --status, --link-goal, --unlink-goal. Titles and descriptions come from the pipeline and are not editable.
squad action list flags: --statuses <suggested,in_progress,completed,dismissed>, --assignee <userId|me>, --insight <insightId>, --priority <P0,P1,P2>, --include-snoozed, --limit, --offset.squad action status takes start, complete, dismiss or snooze, plus --note to append a line to the action’s notes.
squad action update flags: --priority, --effort <low|medium|high>, --category <comms|operational|product|strategic|workspace>, --notes (replaces the field), --assignee <userId|me|none>, --link-insight, --link-one-pager.
squad action context is the one to reach for before writing code against an action. It returns the customer quotes and source links behind the work in a single call.
squad goal list flags: --min-importance, --limit, --offset.squad goal create requires --title and --description, and accepts --importance (1 to 5, default 3).squad goal update flags: --title, --description, --importance.
See Knowledge documents.squad document list flags: --tag, --limit, --offset.squad document create requires --title and --markdown, and accepts --directory and --tags (comma separated). A near-identical title returns the existing document rather than creating a duplicate.squad document update flags: --markdown, --title, --add-tags, --remove-tags.
One-pagers. See One-pagers.squad brief list flags: --status <building,draft,in_review,finalised,failed>, --type <decision|prd>, --source-insight, --limit, --offset.squad brief generate takes --action <AC-N>, --insight <IN-N> or --retry <OP-N>, plus --type <decision|prd>. Generation is asynchronous, so poll the returned OP- ID with squad get.
squad brief status accepts draft, in_review or finalised. The building and failed states belong to generation and cannot be set by hand.
Connect and configure sources in the app. See Integrations.
squad activity flags: --entity-types <list>, --actor-type <human\|agent>, --agent-id, --limit, --after <cursor>. See Activity.squad search flags: --types <signal,insight,action,goal,document,cluster>, --limit. Matching is on title and content, so pick real keywords.squad get accepts --include evidence on insights to pull the supporting signals with their source links. Documents come back as markdown.