Tutorial · Task guide

Run Agent Tasks Safely: References, Approvals, Results, and Rollback

Updated · 2026-08-10Public document
Direct answer: Open Quick Dock, describe one concrete outcome, and attach the exact book/card with @. Keep approvals on for writes or external effects until you trust the plan. Read each tool card before approving; after completion, open the changed item and verify it. Use Roll back this change on supported Agent write cards when the result is wrong—rollback is not a universal undo for provider charges or external actions.

Before you start

  • A configured tool-capable text model with available quota/credits.
  • A specific target book, card, note, or workspace file; avoid broad ‘clean everything’ requests.
  • A backup/export for irreplaceable data before a large multi-file task.

Where to find it

  • Quick Dock
  • Agent workbench
  • Input > @ reference
  • Write tool card > Roll back this change

Step-by-step

  1. Open Quick Dock in the right context

    Open the floating Quick Dock from the page that owns the content. Start a new task when the old conversation has unrelated instructions.

  2. State outcome, scope, and stop condition

    Say what should exist when done, which item may change, what must not change, and what needs your approval. Use @ to attach the exact book/card instead of relying on a similar name.

  3. Review the plan and approvals

    Keep the conservative approval mode for writes, commands, purchases, publishing, or external effects. Read the proposed target and action; reject or edit the instruction when the target is ambiguous.

  4. Follow tool cards, not just the prose

    Expand read/write/command cards to see which files or records were touched. Stop the run if it drifts, repeats calls, or requests authority outside the task.

  5. Verify and, if needed, roll back

    Open the actual book/card/note and confirm the content and location. For supported Agent file mutations, use Roll back this change and verify again. Export the corrected result when it matters.

How to know it worked

  • The task names one exact target and expected deliverable.
  • Every approved write/command points to the intended item.
  • The result is visible in the owning feature, not only claimed in Agent prose.
  • Rollback either restores the previous content or clearly reports that the operation is not rollback-capable.

Cost, data, and irreversible-risk notes

  • Agent runs can make multiple model calls. A short-looking task may use several reasoning/tool steps, each billable through official credits or BYOK.
  • Stopping a run prevents future steps but does not refund completed provider calls. Rollback reverses supported data changes, not AI charges.
  • External publishing, purchases, account changes, and third-party side effects require explicit authority and may not be reversible. Do not approve them from a vague prompt.
  • References can expose the selected local content to the chosen model provider. Attach only what the task needs.

Troubleshooting

Agent asks to modify the wrong book/card

Likely cause: The target name is ambiguous or no exact @ reference was attached.

What to do: Reject the step, stop if necessary, start a scoped instruction with the exact @ item and state that all other items are read-only.

Approval keeps reappearing

Likely cause: The task contains several distinct writes/commands, or the prior action failed and was proposed again.

What to do: Expand the tool card and compare target/action. Approve only new intended steps; if it is looping, stop and ask for a no-write diagnosis.

Rollback is missing

Likely cause: The card is read-only, the action was external, the mutation did not capture a reversible snapshot, or the retention window is gone.

What to do: Check the owning feature's history/export/branch controls. Restore from an export when available; do not assume rerunning the Agent reconstructs the exact old bytes.

Task stops with model/tool unavailable

Likely cause: Selected model lacks tool calling, provider failed, permission was denied, or the referenced item is no longer accessible.

What to do: Choose a tool-capable enabled model, reopen the exact item, grant only the required approval, and resume or restart with the preserved task context.

Frequently asked questions

Should I turn on full automatic approval?

Use it only for a narrowly scoped, reversible task you understand. Keep confirmation for money, publishing, account changes, commands, and broad writes.

Does Stop undo what already happened?

No. Stop prevents later steps. Verify completed tool cards and use supported rollback/history/export controls for changes already made.

Can Agent rollback an AI charge?

No. A content rollback does not reverse a provider request or official credit charge that already completed.

Sources and verification

  1. Agent and Companion guide · Foreverse · Verified

Coverage and verification

PlatformAndroid Agent Quick Dock
App versionv76+
Path verified

Tutorials & Help