Resources

Glossary

The words these docs use, in plain terms.

Terms

TermMeaning
AI agentAn AI model that decides the steps a request needs and takes them with tools. Sands is an AI agent.
AI teammateHow Sands works with you: you delegate work in plain language and it reports back with results and evidence.
Approval modeYour setting for when Sands asks before changing your tools: Manually approve, Automatically approve or Skip all approvals.
Approval cardThe card in the chat that shows a change before it runs, with Approve and Decline.
ArtifactSomething a conversation produces that you keep using: a plan, a report, a file.
BriefWhat you hand Sands to plan from: a message, a client brief, a statement of work.
ConnectionSands' access to one of your tools, granted through the tool's sign-in.
CreditThe unit Sands uses to measure work. Each task uses the credits its work took.
Open questionSomething a plan needs that the brief did not say. Listed in the plan for you to answer.
PlanThe document Sands drafts from a brief: goal, capacity, tickets, risks, dates and open questions. Also called a spec.
RunThe steps Sands takes to answer one request, shown at the top of the reply.
SendCreating a plan's work in Jira, Linear or Asana. A one-time handoff.
StepOne unit of work in a run, like reading a project or creating a ticket, with what it found.
TicketOne piece of work in a plan. Becomes a story, issue or task when sent.
WorkstreamA group of related tickets in a plan. Becomes an epic, milestone or section when sent.