> ## Documentation Index > Fetch the complete documentation index at: https://docs.pinework.ai/llms.txt > Use this file to discover all available pages before exploring further. # Mac app > The Pinework Mac app is the full dashboard plus a built-in device manager, so agents can run on your Mac and you can open its files, a browser and a shell beside their work. The **Pinework Mac app** is the Pinework dashboard in a macOS window, with a device manager built in. The app loads the same dashboard you use on the web. It adds what needs your machine: local runs, and local files, a browser and a shell beside a conversation. ## Signing in turns your Mac into a device When you sign in, the app starts its device manager. Your Mac then appears in **Settings** under **Connected devices**. It takes runs for agents set to run on a device. The first device you connect becomes the workspace's default device. You can change that per device with **Set as default device**. The device manager checks which harnesses the Mac has: Claude Code, Codex, Cursor and OpenCode. The dashboard shows each one as **Ready**, **Needs attention** or **Not installed**. Runs on the Mac use the harnesses and logins already there. A run on your Mac works in a folder you register. See [Run agents on your Mac](/guides/run-on-your-mac) for the steps. ## The app keeps running from the menu bar Closing the window does not stop the app. It stays in the menu bar and keeps taking runs. The menu bar menu shows the device status, such as **Connected** or **2 agent(s) running**. From it you can start, stop or restart the device manager. You can also check for updates, send a test notification, log out or quit. Updates download in the background. When one is ready, the menu offers **Restart to update** with the new version number. ## Some panels beside a conversation need the app A conversation has a side panel with four surfaces: **Files**, **Browser**, **Review** and **Terminal**. **Review** shows every file the work changed, on the web and in the app. The other three need the Mac app. * **Files** browses the folder the work runs in on your Mac. * **Browser** opens a web page beside the work. Agents can drive the same browser. They open tabs, read the page, click and type. You can fill a login saved in Pinework into a page. * **Terminal** opens a shell in the folder the work runs in. Agents can also open terminals there and run commands. **Files** and **Terminal** need work that runs in a folder on your Mac. Work in the cloud has no local folder. On the web, these panels ask you to open Pinework Desktop. ## The app does a few more things the web cannot * **Folder picker.** Registering a folder opens a Finder dialog with **Choose folder…**. On the web you type the path. * **Import from your Mac.** The app reads your coding tool setup and brings it into the workspace. That covers plugins, MCP servers, skills and rules. See [Import your setup](/guides/import). * **The `pinework` command.** The app puts the Pinework CLI on your PATH, unless another copy is already there. * **macOS notifications.** Pinework notifications arrive as native macOS notifications. Each notification type has a **Desktop** toggle in **Settings** under **Notifications**. * **Local transcripts.** A conversation that runs on your Mac keeps its transcript on the Mac. Other devices read it from there while the Mac is online. ## The app needs macOS 13 on Apple silicon The app needs macOS 13.0 or later on Apple silicon (M1 or later). Windows and Linux have no app yet. On Linux, or a server with no desktop, install the Pinework CLI instead. Then run `pinework device connect` to start the device manager. ```text theme={null} Pinework ──run──▶ Mac app (device manager) ──▶ harness ──▶ your folder ▲ │ └───────────── results, approvals ─────────────┘ ``` Connect your Mac and point an agent at a folder. How Pinework decides where a run happens. Check on agents from your phone. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.