> ## Documentation Index > Fetch the complete documentation index at: https://docs.audimate.ai/llms.txt > Use this file to discover all available pages before exploring further. # Watch mode > Demonstrate work in your desktop apps, review the recording, and submit it to create a guide, a reusable playbook, and task inputs. Demonstrate a task in your real apps and turn it into a procedure you can reuse. Audimate is coming soon. Access to the web workspace and desktop downloads is limited to approved testers. Public signups and downloads are not open yet. The desktop app is for Windows. macOS is coming soon; Mac-specific guidance describes the upcoming release. Watch mode requires the [Audimate desktop app](/concepts/desktop-app) and works on every plan. See [Plan limits](/account/plan-limits) for recording and workflow limits. ## Start watching Hold your push-to-talk shortcut and say “watch me do this.” Audimate asks for recording consent when needed. Work in your apps. Explain your intent and decisions aloud when useful. The recording card shows elapsed time and captured moments. Click **Stop** on the recording card. The review editor opens with the captured video. Review the annotations, highlights, and trim range before submitting. See [Recordings](/concepts/recordings) for the editing controls. You can also start from **Record workflow** on the dynamic dock's **Home** tab. When choosing from several displays, the selected display is the one recorded. A red screen border, the recording indicator, and the dock card show that capture is active. The card provides **Pause**, **Stop**, and **Discard**. A recording stops after 30 minutes, or earlier if it reaches the capture size limit. The captured material remains available for review. Split longer procedures into separate recordings. ## What is captured, and what is not | Captured information | Purpose | | --------------------------------- | -------------------------------------------- | | Selected display video | Show the actions and their results | | Clicks, drags, and scrolling | Locate interactions in the procedure | | App, window, and dialog changes | Explain transitions between screens | | Page addresses and control values | Identify locations and selected information | | Copy and cut events | Record the action without clipboard contents | | Narration | Preserve spoken explanations | Audimate does not install a keyboard hook or read password fields. Visible typed values can still appear in the video and be read during processing. A control changed only through the keyboard may lack a separate value annotation. Page addresses captured automatically omit query strings. Copy events do not include copied text. ### Sensitive information Recording pauses when a configured sensitive app, such as a password manager, comes to the foreground. Sensitive-field protections also interrupt capture when required. The recording card shows the pause, and narration pauses with it. Review the video before submission. Use [Redact](/concepts/recordings#add-highlights) wherever information must remain concealed. On a Mac, Audimate windows you bring onto the recorded display can appear in the video. Keep them off that display when their contents should not be recorded. ### Unsaved recordings If you navigate away, choose **Review recording** in the dock to return to your draft. Stopping capture alone does not submit it. Signing out or switching workspace can discard an unsaved recording after confirmation. Submit it before changing workspace. Hands-free narration remains active while recording when **Recording narration** is enabled in microphone settings. ## Processing After submission, Audimate creates a guide and drafts the written procedure. Repeatable procedures also get an empty task board and intake form. The form asks for each task's inputs. Results stay off the form, and recorded example values do not become defaults. Generated playbooks use field @mentions to read that task's values and write its results. If details come from a document, the form asks for that source or its lookup information. Keep the desktop app running on the recording device until processing finishes. You can use other pages or close the window. Quitting pauses processing until you reopen the app and return to the same workspace. Submitted recordings survive restarts. Arro receives your reviewed annotations and requested images from the redacted video to interpret the procedure. The full video and redaction instructions stay on your device. Only images chosen for the finished guide are saved with it. All workflow tabs stay locked while processing. The illustration loops while Arro works, and stops if processing pauses or finishes. With reduced motion enabled, the artwork stays still. | Status | Action | | -------------------------------- | ------------------------------------------------------- | | Connection interrupted | **Retry connection** resumes communication | | Processing paused | **View details**, then **Retry processing** | | Continue on the recording device | Open Audimate on the device used to record | | Restart Audimate to continue | Fully quit and reopen Audimate | | Record this workflow again | **Cancel processing**, then capture a new demonstration | A missing video or missing or incompatible saved progress requires a new recording. Temporary connection problems can be retried without recording again. The submitted video and saved progress remain on your device for retries. Audimate deletes them when processing finishes or you choose **Cancel processing**. Permanent deletion of an accepted recording or its workflow also removes that video when the recording device reconnects to the same workspace. Playbooks use available connections where possible, and application or browser steps elsewhere. ## Usage Recording processing uses your [monthly usage](/account/plan-limits#monthly-usage). It follows your current model settings and plan limits, including when you resume a paused recording. Retrying can use more when additional interpretation is needed. Your Arro thinking setting affects the interpretation quality and usage. ## Related Edit annotations, highlights, and trim before submitting. Review the reusable instructions. Create tasks with the inputs the procedure needs.