> ## 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. # The dynamic dock > Follow everything Arro is doing from one surface at the top of your screen, and take control of any of it without leaving what you are working on. The dynamic dock is where [Arro](/concepts/arro) lives while you work. It hangs from the top center of your main screen and changes size and shape to match whatever is happening, so you can tell what Arro is doing at a glance. 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. With multiple monitors, the dock stays on your primary screen. Arro's cursor follows your mouse across screens. The dock is part of Arro in the Audimate desktop app. It stays available after you end a voice session, because your [background tasks](#background-tasks) keep running on their own. Choose **Replay tour** in your profile menu for Arro's optional spoken dock tour. It explains the dock's location, cards, and how to ask for something, advancing after each line. **Next**, **Back** and **Esc** work at any time. The first-visit spoken tutorial is covered in [Quickstart](/quickstart). | Context | What happens | | ---------------------------------------------------------- | ----------------------------------------------------------------------------- | | Arro is on and signed in | Arro speaks the dock tour | | Arro is off, signed out, starting, or an app is fullscreen | The sidebar tour runs instead, and **Replay tour** later plays the spoken one | ## Three shapes | Shape | When | What you see | | -------------- | ------------------ | --------------------------------- | | A small handle | Nothing is running | It sits quietly out of the way | | A status pill | Something is live | An indicator and a word | | A wide panel | You hover it | Tabs, with the detail behind them | The pill tells you what is live by color: a pulsing red dot for "Recording 2:15", violet for "Coaching 5:02", an amber countdown for "Timer 34:28", and sky for "Controlling 0:42". Arro thinking, listening, and speaking show here too. Move your cursor away from the panel and it collapses back. Drawing instructions, computer-control hints, and coaching's **I've done this** button share a consistent set of prompts. | Dock state | Control prompts | | ---------- | ------------------------------- | | Collapsed | Stacked below the dock | | Expanded | Hidden until the dock collapses | On a Mac with a notch, the dock lays itself out around it. The handle sits inside the notch, and the panel stays flush with the top edge with its content starting below, so nothing you need to read is ever hidden behind it. ## Tabs Your tasks live on the **Home** tab, which is also where you start a [screen recording](/concepts/watch-mode) with **Record workflow**. A live session gets a tab of its own: Control, Recording, Coaching, or Timer. The dock opens on that tab, so what you are in the middle of is what you see first. Switch back to **Home** at any time. **Plugins**, beside **Home**, lets you search the curated library and install plugins for Arro. See [plugins](/concepts/plugins) for setup, connections, and availability controls. ## Background tasks When a task starts, the dock shows its name with a spinner before returning to rest, and does the same when a task finishes or fails. Open the dock to see each task with what it is currently doing, a button to cancel one while it runs, and an **Open** button when it produced something worth looking at. A failed task shows **Retry**, which starts it again. The new attempt knows what went wrong before, so it checks how far the first one got instead of redoing finished work. Finished tasks stay in the list with their outcome until you dismiss them with the ×. When you have a lot of tasks, click the search icon at the top of the dock and type to narrow the list by name, by what a task is doing, or by status. Clear the box or press **Escape** to see everything again. A device runs at most **12** background tasks at once. Past that, starting another is refused, whether you ask Arro or use **Run again**, **Restart**, or **Resume**, and you are asked to stop one to free a slot. This is a limit on the device, not on your plan, so a second computer gets its own 12. A task [split across several agents](/concepts/work#several-agents-on-one-task) uses a slot for each of them, so one split task can hold up to five. Tasks working a [task board card](/data/boards#starting-agents) use these slots but are never refused outright: a card that cannot start keeps its place in the pick-up list and tries again a few minutes later. ### When a task needs you A background task cannot sign in, solve a CAPTCHA, or clear a two-factor prompt on its own. When it reaches one, it pauses, switches to a **Needs you** state, and the dock opens on its own so you do not miss it. The card explains what stopped it. For a browser blocker, the card offers **Take over**, which opens the task's live page for you to [work in yourself](/concepts/desktop-app#taking-over-the-browser). Sign in, solve the check or enter the code there, then press **Continue**. A sign-in you make there is kept for later tasks unless you untick the option in that window. A workflow you start yourself can also pause for a missing answer. Respond directly in its **Needs you** card. | Request | Your response | | -------------- | --------------------------------------------- | | Written answer | Type in the field, then click **Send answer** | | Choice | Click the button matching your answer | The task continues with your response. You can also answer from the task's detail page. ### When macOS needs permission On a Mac, the dock is also where Audimate asks for the permissions macOS keeps to itself. A card explains what is needed and why, with **Allow** and **Not now**, and Arro says it out loud, because a blocked screen capture or a blocked click otherwise fails silently. Pressing **Allow** raises macOS's own dialog. What each card asks for, and what happens if you decline, is in [macOS permissions](/concepts/desktop-app#macos-permissions). ### Hearing about tasks When a task finishes, fails, or needs you while you are working in another app, Audimate shows a system notification. Click it to open that task. Turn this off with **Notify me about background tasks** under **Arro → General** in settings. When a task finishes or fails, Arro can also say a one-sentence summary out loud, even if you have stopped talking to it. To turn this off, open the same page and switch off **Announce finished background tasks**. **Ask for approvals out loud** on the same page is off by default, and only matters in **Manually approve** mode, because in **Automatically approve** a task never waits on an approval. Switched on, Arro also asks when a task is waiting ("Sort downloads wants to modify your Downloads folder. Allow it for this task?"), so you can answer by voice. It waits until you are not mid-conversation, asks once per pause, and skips the ask if you answer on the card first. ### Approvals Configure browser and file access in [desktop settings](/concepts/desktop-app#browser-control). A task works inside an **Audimate** folder in your Documents and browses with your dedicated Audimate profile. If it needs a folder outside that, or a site that is not on your [Allowed sites](/concepts/desktop-app#allowed-sites) list, it pauses and asks. | Answer | How far it goes | | ---------------- | --------------------------------------------- | | **Allow** | The rest of that task | | **Always allow** | Permanent, until you change it | | **Deny** | The rest of that task, which is worked around | One answer settles it, so an allowed site does not ask again during the task. A task allowed to read a folder still asks before it changes anything in there. The same prompt appears before a task runs a [plugin](/concepts/plugins) tool set to **Needs approval**, and **Always allow** switches that tool over for good. You can answer by voice: tell Arro "allow it" or "deny that" while a task is waiting. A spoken answer only ever covers that one task, so making something permanent takes a click on **Always allow**. These cards appear only when your approval mode is **Manually approve**. The default is **Automatically approve**, where a [safety check](/concepts/desktop-app#approval-modes) decides instead: clearly safe actions run, and anything that looks unsafe is declined. After a task finishes, you can ask Arro to take it further, for example "now also email that report". It starts a fresh task building on what the finished one did, rather than starting over. ### Task history Open the **Tasks** view for everything Arro has run in the workspace you are in. Narrow the list by type, **Assistant** for one-off tasks and **Workflows** for runs of a saved workflow, and by date range. A status filter narrows to **Running**, **Completed**, **Failed**, **Cancelled**, **Paused**, or **Interrupted** tasks. Click any task to replay it step by step, with a screenshot for each action, and to **Open** what it made, **Run again** a finished task, or **Restart** one you cancelled. A finished task also lists **Outputs**: the files it made for you, with the main result pinned at the top and badged as such. Working files the task created for its own use, such as pages it downloaded to read, are not outputs and are cleared when it finishes. Each row opens the file or shows it in your file manager, and **See these in Creations** filters the [Creations](/concepts/creations) library down to that one task. A [workflow run over many tasks](/concepts/workflows#running-many-tasks-at-once) lists each task as its own entry rather than nesting them under the run, because each one is claimed straight off the task board's pick-up list. What a task did, its steps, its screenshots, and its summary are stored only on the device that ran it and are never uploaded. Audimate keeps a short record that the task ran: who started it, how long it took, and how it ended, never the contents. That record stays private to you, except for runs of a **saved workflow**, which admins and owners also see under [Organization → Runs](/account/organization#runs) because a workflow is a shared org resource. Each device keeps **90 days** of task history per workspace. ### Switching workspace or signing out Task history is per workspace as well as per device, so switching shows you that workspace's tasks. Arro's background tasks run on your machine for the workspace you are in, so switching pauses anything still running, and you can pick it up again from the **Tasks** view when you come back. Audimate asks first, and the confirmation names what it is about to stop. Everything else the dock is holding ends outright, because none of it has been saved anywhere to come back to. A screen recording in progress is discarded, a coaching session closes, a timer is cancelled, and Arro stops controlling your screen. Signing out does the same, and so does creating a workspace, since that switches you into the new one. ### If Audimate closes unexpectedly | How it closed | How the task comes back | | ---------------------------------- | --------------------------------------------------- | | Quit normally | **Paused**, with **Resume** | | Forced to close, progress saved | **Paused**, picking up where it left off | | Forced to close, nothing saved yet | **Interrupted**, where **Run again** starts it over | A task never sits stuck on **Running**. A task working a [task board card](/data/boards#starting-agents) needs no button at all: quitting hands its card back to the pick-up list, and Audimate picks it up again next time you open it. It is also the one kind of task where **Run again** is refused, because a card is started from the task board. Audimate tells you to put the card back in the task board's pick-up list. ## Coaching sessions While [Arro is coaching you](/concepts/guide#coaching), the dock gains a **Coaching** tab holding every step of the session, so you never have to ask it to repeat itself. Each step is a card showing what Arro was looking at with its highlight on it, plus what it told you to do. The newest step is marked **Current**, and that is the one **"I've done this"** always advances from, wherever you have scrolled to. | Control | What it does | | -------------------- | --------------------------------------------- | | Click any card | Shows that step's highlight again and says it | | **Replay** | Repeats the step you are looking at | | The violet checkmark | The same press as **"I've done this"** | | **X** | Ends the session | The most recent steps show a picture, and older cards keep their instructions without one. The session is held on your computer only and is discarded when it ends or you sign out. Nothing about it is uploaded. ## Control During [computer use](/concepts/computer-use), the dock gains a **Control** tab showing how far Arro has got. See [Pause or stop](/concepts/computer-use#pause-or-stop) for its controls and keyboard shortcuts. ## Timers Ask Arro for a timer the way you would ask a person: "set a timer for 10 minutes", "pause the timer", "cancel it". Arro only sets one when you ask. While a timer runs, the dock shows an amber countdown next to the word **Timer** and gains a **Timer** tab with a pause/resume button and an **X** to cancel. At zero, an alarm rings every few seconds and the pill reads **Time's up** until you stop it, from the tab or by saying so. The alarm rings even with Arro's [sound effects](/concepts/arro#personalize-arro) switched off, though it follows their volume setting. * **One timer at a time.** Ask for a second and Arro offers to replace the current one. * **Up to 24 hours.** Anything longer is better as a calendar reminder. * **It lives on this device.** The timer is not synced, and signing out clears it. ## Related The assistant that lives in the dock: how to talk to it and point at things. Background tasks and watch-once workflows that report here. Computer use, allowed sites and folders, and approval modes.