Start with a bounded task
Describe the application, target, approved information and intended outcome. A task can involve reading, typing, navigating or submitting; these actions do not carry identical permissions. Select the least access that supports the workflow.
Use current observations
Browser and desktop interfaces change while an assistant works. The selected window, page state and intended control must still match the approved action. If the context changes, stop or obtain a current decision instead of reusing a stale observation.
Approve consequential steps
Agree which actions need human approval, who may grant it and what the approval covers. A demonstration or explanation is not authority to make a real business change. Account and company policy continue to apply after approval.
Handle stopping and uncertain effects
Stopping a workflow, revoking access and proving an external process stopped are different events. A lost response after submission may leave the action completed, failed or unknown. Preserve that uncertainty and reconcile the outcome before repeating it.
Distinguish browser from desktop coverage
Deploy’s isolated-browser foundation and Sidekick’s desktop tooling are separate foundations. Full application coverage, company integration and installed workflow acceptance remain unqualified. Scope your pilot to named applications and tasks.
Define the capture boundary
Record the instruction, approved observation, action decision, attempt and outcome for supported activity. Set exclusions for sensitive content and define who can inspect retained evidence. The record is not a blanket screen recording service.