Review and approve Sidekick actions
Inspect a proposed project change, satisfy confirmations and URL authority attestation, then approve or reject it.
3 min read
- Project
- Sidekick panel
- Review
When Sidekick proposes a change, inspect the action preview in its panel and explicitly select Approve or Reject. Strong approvals require the displayed confirmation phrase.
Review exactly what Sidekick intends to change before it can run. A proposal is never an executed change, and approval is tied to its project, arguments, and safeguards.
- Finish with
- One explicitly reviewed proposal, or a clear rejection
Review a proposal
Ask for a concrete proposalExample: create a draft assistant from two named sources.
Writes also require Sidekick actions to be enabled and included in the project plan.Inspect every argumentCheck targets, source IDs or URLs, scope, settings, and capability.
A proposal should match the intended project exactly.Reject or approveSatisfy every displayed confirmation before approval.
Sidekick resumes only after decisions are recorded in order.Verify in the dashboardWatch the streamed result, then check the relevant configuration.
The lifecycle is awaiting approval, approved, executing, then a terminal outcome.
- Type the displayed phrase for sensitive URL operations or source deletion
- Attest that you control or may use a proposed URL
- Prepare a new proposal when the old one expires, conflicts, or fails
- Never treat an approval as proof that the change is desirable
The action lifecycle is explicit: awaiting approval, approved, executing, then succeeded, failed, or conflict. A rejected, expired, cancelled, failed, or conflicted action is terminal; prepare a fresh proposal rather than treating it as completed.
Extra safeguards
Some actions require more than the normal review button:
- Strong approval: type the exact confirmation phrase displayed in the preview. This applies to sensitive URL operations and source deletion.
- URL authority attestation: check the statement confirming that you control, or are authorized to use, the proposed domain or URL. URL-source creation, URL changes, start, and re-sync can require this attestation.
- Persona freshness: when applying a persona, Sidekick binds the reviewed proposal to that active persona's current identity and revision. If it changes before execution, the approval will no longer match.
Sidekick proposes only these write categories: project settings and business-context regeneration; agent creation, configuration, persona application, activation, deactivation, and publishing; and data-source creation, configuration, URL changes, start, re-sync, cancellation, or deletion. Text-source content is bounded to 1–12,000 characters. URL changes use their own proposal rather than a generic source update.
Safety boundaries
Sidekick cannot delete a project or an agent. It does not execute a change from conversational text alone, reuse an expired approval, reorder a batch of actions, or substitute a different project. Approval is not proof that the change is desirable; verify the before-and-after configuration yourself.
Last updated on