Run work and approve it

Chat, send a mission, schedule a routine, and approve or reject anything that would write.

Work, Routines, Runs, Review queue and Tool approvals are the operational half of Shelly. The snail can draft and recommend freely. A write waits.

Chat

Chat is the interactive session. Choose a scope — personal, workspace or client — and a model. Attach capabilities with +. Send the message. Use Chat when you want an answer now. Use Work when you want a crew to carry a brief through tools, with an approval trail.

Send work

  1. Open Work and press Deploy mission Write the brief and assign the snail. A mission is work that did not start from a Tides card.
  2. Or start from Tides A card in Agent Inbox, or any task linked to a crew, becomes the job. The assignment stays tied to that task so you do not get two active jobs for the same card and crew.
  3. Watch it under Runs A run moves through queued, planning, working, and sometimes awaiting approval, then completed, failed, cancelled or blocked. Open a run for the result, the tool calls, the cost and the timeline. Admins can cancel or retry.

Routines

A routine runs a snail without someone pressing a button. Create one with New deployment. Give it a schedule, how many runs may overlap, and the instructions for that trigger. You can also run it now, or call its trigger link from another system. Treat the link as a secret. Regenerate it if it leaks. Pause a routine when it should stay defined but not fire. Members can read routines. Admins create, edit, pause and regenerate them.

Approve the writes

  • Review queue is the decision list. A waiting change shows the action and the reasoning. Approve it, or reject it with a reason. Waiting approvals expire.
  • Tool approvals is the same class of write in raw form, including every call to an attached integration. Approve or reject there when you need the tool payload rather than the summary.
  • A finished run can also propose memory or behaviour changes. Apply or reject those proposals. They are not applied quietly.

Source watches

A source watch checks a public URL or a connected read-only source on an interval. Ask Shelly to watch something, then manage the watch here: pause it, read the last check, and see if it is queued. Watches observe. They do not skip the approval step when a later run wants to write.

From the other apps

Every product has a Shelly panel. Open it from the sidebar. It knows which app and page you are on. Presets such as a handover on a board, a delivery note on a document, or an explanation of effort on the timer start from that context. If the answer lives in another app, the panel can open it. Credits for these runs come from the organisation pool you manage under ShellStack → Billing.

Activity

Activity inside Shelly is the crew’s own history. ShellStack → Activity is the suite-wide feed. Use the one that matches the question: what did this snail do, or what changed anywhere.