Help and FAQ

Sands is an AI agent: an AI model that plans and takes the steps a request needs using your connected tools. It works like a teammate, but it is not a person, and it can get things wrong. Every reply shows its steps so you can check them.

No. Sands acts when you ask, in a chat or in Slack. It does not run on a schedule or start work by itself.

No. You can draft and edit plans, research and ask questions without a connection. Sands asks you to connect when a request needs your tool.

Jira, Linear, Asana and Slack today. See Integrations.

Each chat keeps its own thread, including the plan you are working on. Sands also remembers which tool and project you work in. A new chat starts a new thread.

Yes. Ask it to research something and it answers with sources. See Web research.

Only what you ask for, and your approval mode decides when it checks with you first. By default, ordinary changes run and riskier ones, like new projects, sending a plan or messaging several channels, wait for your OK. See Approvals.

Ask Sands to change it back, or change it in the tool. Sands cannot unsend a Slack message. Changes to a plan in Sands can be undone with Undo last Sands edit.

No. Each change runs once, and re-sending a plan skips what it already created.

They are what Sands could not know from your brief. Answer them in chat and Sands updates the plan, or edit the plan yourself.

Sands only assigns people you named. Name the team with roles in your request, or assign tickets in the table.

Sending is a one-time handoff. Ask Sands to update the tickets in your tool, or send the new parts.

Use Undo right away, or Restore on the plan's card in the chat within 30 days.

What its work took, so it varies. Typically a reply in conversation uses about 3 to 10, a lookup in a connected tool about 20 to 30 (up to about 65 when it is the first in an hour), and building a plan about 60. These are estimates, not prices, and no single task uses more than 200. See Credits and plans.

Nothing breaks and nothing is charged. Upgrade to Pro from the card in the chat, or wait for your Pro credits to refresh.

The tool expired Sands' access. Click Reconnect; the request picks up where it stopped.

Your browser blocked the pop-up. Allow pop-ups for Sands and try again.

Check the project name, and that the account you connected can see it. For Jira, the project must be on the site you granted. Sands lists the closest matches it found.

Make sure Sands is in the channel (/invite @Sands) and that you linked your Slack account in Settings → Apps → Slack.

Your edit is still on screen. Click Retry. If it keeps failing, reload the page; saved edits are kept.

Use the megaphone button at the bottom of the sidebar with the chat open. The run attached to it shows us what happened.