Stuck? Let's get you unstuck.
Quick answers to the questions early-access teams actually ask, and a straight line to the people building the product when the answer is not here.
Exactly as much as its autonomy level allows: observe, suggest or act, set per workflow and changeable any time. Anything irreversible, customer-facing or outside a guardrail always waits for a human, whatever the dial says. How operators and playbooks work
Anything that can be undone, yes, in one click from the activity record, which shows what was done, by which operator and why. The actions that cannot be rolled back are exactly the ones an operator never takes without your approval first. See the control surface
The autonomy dial lives on each operator, per workflow. Turn it down and the operator goes back to suggesting; turn it up and routine corrections run on their own, inside the guardrails you set. Meet the operators
Any gap between how your operation is meant to run and what is actually happening: a stale doc, a ticket pointing at last week's plan, a sync quietly falling behind. The genome scores each gap by impact and momentum. How detection works
Usually the connection's credentials or scopes: re-authenticate in a click from the integration's page, or widen the scope if the tool's API changed. The genome flags a connection the moment it falls behind, so check the deviation it raised, which names the cause. Integration setup and scopes
Open its entry in the activity record: every action links the playbook it followed and the deviation that triggered it. Roll the action back if it was wrong, then decline that play. The operator lowers its confidence on similar calls and asks first next time. The audit trail, in detail
The score is computed from open deviations, weighted by impact and momentum, and it never moves without a reason you can read. The score's breakdown lists exactly which deviations moved it and by how much. How the loop computes it
Supasprinkles is in early access. The demo workspace is open to everyone right now; joining the early-access list from there puts your workspace in the queue. The changelog shows what is shipping in the meantime.
Only what you grant, per integration: you choose the data, workflows and events it may observe, and whether it is read-only or action-enabled. Scopes are revocable in a click, and every read is logged. Security & trust
Talk to the people building it
Early access means support is the team itself, no tiers, no bots. We answer as fast as we can.