Install Pinar

Install Pinar from the Chrome Web Store.

• Pin the Pinar icon from Chrome’s extensions menu so it stays visible.
• Open the Chrome Web Store listing to add the official extension.

On macOS, the Pinar application lives in the menu bar. On Windows, it lives in the notification area. Open the Pinar application to start capturing. On Linux, install with the command below.

• Captures stay on this computer. Choose “Open Folder” to see them.
• On macOS and Windows, “Start at Login” keeps Pinar available after you sign in.
• If a capture has no image, open Pinar and try again.

Download the Pinar application from the links below, install it, and open it.

When Pinar is open, choose “Open Workspace”. If it shows “Local Server: Off”, choose “Start”. If pasted captures stop arriving, open Pinar again.

• macOS: download the Pinar application, open the disk image, and drag it into “Applications”.
• Windows: download the Pinar application, extract it, and run Pinar-Setup.exe next to the .installer folder. It appears in the notification area.
• Windows: the first run may show “Windows protected your PC”. Choose “More info”, then “Run anyway”.
• Linux: curl -fsSL https://pinar.dev/install.sh | sh

The Pinar menu looks for updates on its own and when you choose “Check for Updates…”. A newer version downloads in the background while the menu shows “Downloading {version}…”. Choose “Update to {version}” to apply the downloaded update: the app reopens at the new version, and the local server restarts with it. When there is nothing newer, the menu shows “You're updated” for a short while.

If a check fails, the app stays open and the menu shows “Update check failed”. Choose that item to run the check again. Read what each version changes on the “What’s new” page of the site, or open the “What’s new” link in Settings → About, which sits next to the version your build runs.

• A failed check only blocks the update itself: the running version, your captures, and the local server keep working.
• The desktop app checks for updates when it starts, so the menu usually shows the result without you asking.

Every supported agent registers a Pinar session hook. When you open a session in Claude Code, Codex, Cursor, Grok, Antigravity, Pi, or OMP, the hook opens Pinar and makes sure the local server is running before the agent starts working.

The Pinar desktop app registers these hooks when it starts, and the command-line installers register them while they install the helper, so there is nothing to set up per agent. The hook file each agent uses, and the first-time trust step an agent may ask for, are listed in the Session hooks section of the Pinar README.

• The hook only opens the app or starts the local server. It does not read your files or change what the agent does.
• Re-running the installer, or restarting the desktop app, re-registers the hooks if you cleared them or switched agents.

On Linux and Windows you can install Pinar's helper from the command line instead of the desktop app. The one-line installer downloads the helper into a folder in your user account, adds that folder to your PATH, and registers the agent session hooks, so a new terminal session finds the helper right away.

The helper is the same local Pinar service the desktop app runs: it stores the captures on this computer and serves the local workspace and viewer. The Install section of the Pinar README documents the command-line installers.

• Use the command line on machines without the desktop app, or when you manage Pinar from a remote terminal.
• Installing both the desktop app and the command-line helper is safe: they use the same local service and the same captures.