Pie Link is in public beta. It connects the context in your current page and conversation to your computer — macOS and Windows. With your approval, Pie can create local files, use existing skills, or send work to Claude Code, Codex, Cursor, and other local AI tools.
Pie still handles work in the browser. Pie Link connects that context to your local environment so the task can continue without a manual handoff.
| Step in the workflow | Pie only | With Pie Link |
|---|---|---|
| Understand the current webpage, PDF, and conversation | ✓ | ✓ |
| Carry webpage and conversation context into a local task | ✗ | ✓ |
| Save results as local files | ✗ | ✓ |
| Use skills and scripts already on this computer | ✗ | ✓ |
| Send work to a local AI tool you select | ✗ | ✓ |
| Return completed work to the current conversation | ✗ | ✓ |
| Keep the full context in a local workspace for continued work | ✗ | ✓ |
Pie already understands the page and conversation where a task begins. Pie Link carries that context into the local workflow, so you do not have to reconstruct it in another tool.
Scope: the current task context · the working directory you select · the local tool you explicitly choose
Some tasks need a clear result; others need your continued involvement. Pie Link delivers the work to the place that fits.
Pie Link sends the task, relevant context, and working directory to the local AI tool you select. When it finishes, the result returns to this conversation so Pie can continue from it.
Best forPie Link organizes the material, files, and findings from the conversation in a local workspace, then opens the tool you select. You continue in the editor or terminal with the full context available.
Best forNeed the result? Return it to Pie. Need to take over? Continue locally.
You always choose the target tool and working directory. On macOS this includes Claude Code, Codex, Cursor, OpenCode, and Pi, including desktop-app handoff. The Windows public beta includes the terminal forms of Claude Code, Codex, Cursor, and OpenCode.
Pie Link does not turn a conversation into unrestricted access to your computer. The action, target tool, working directory, and permissions are explicitly constrained.
Windows public beta does not include the SRT sandbox declared for macOS. Skill scripts still require approval and are written to the on-device audit log, but they are not isolated the same way. Shell scripts are macOS-only. Install, uninstall, and the status icon also differ — see the FAQ.
Pie Link is in public beta. macOS 13 or later is available now as one universal package for Apple Silicon and Intel; the connection appears in the menu bar. A Windows build — Windows 10 22H2+ / Windows 11, x64, including ARM PCs via the system’s x64 emulation — is available now; the connection appears in the system tray. Both work with the Pie extension in Chrome.
macOS uses a .pkg; Windows uses pie-link-setup.exe. Running the latest installer replaces the installed version. The Pie extension indicates when an update is required.
Download the latest .pkg and run it. It installs over the previous version.
Download the latest pie-link-setup.exe from GitHub Releases.
Run it. Windows SmartScreen may warn that the publisher is unrecognized — the public-beta installer is unsigned. Choose More info, then Run anyway.
Approve the single User Account Control prompt. When the tray icon appears, Pie Link is ready and the extension connects automatically.
If the panel says connected but nothing works, run this in a terminal:
"%ProgramFiles%\Pie Link\pie.exe" doctorYes. Every in-browser Pie feature works without Pie Link. Installing it only adds the local connection described on this page.
macOS and Windows remove Pie Link in different ways. The steps below clear the program files; the data directory is optional and listed last.
Quit Pie Link from the menu bar: click the Pie icon and choose Quit.
Unload and remove the two launch entries:
launchctl unload ~/Library/LaunchAgents/ai.wiseria.pie.plist ~/Library/LaunchAgents/ai.wiseria.pie.menubar.plist
rm ~/Library/LaunchAgents/ai.wiseria.pie.plist ~/Library/LaunchAgents/ai.wiseria.pie.menubar.plist
Remove the menu bar application:
sudo rm -rf "/Applications/Pie Link.app"
Remove the command-line binaries:
sudo rm /usr/local/bin/pie /usr/local/bin/pie-host
Remove the Chrome native messaging manifest:
rm "$HOME/Library/Application Support/Google/Chrome/NativeMessagingHosts/ai.wiseria.pie.json"
Remove Pie Link’s data directory. It contains local skills, session workspaces, and permission records; back up anything you want to keep:
rm -rf ~/.pie
Quit Pie Link from the system tray: right-click the Pie icon and choose Quit.
Open Settings → Apps → Installed apps, find Pie Link, and choose Uninstall. You can also run unins000.exe in C:\Program Files\Pie Link. This removes the program, native-messaging keys, and startup entry.
To also remove local skills, session workspaces, and permission records, delete the data directory after backing up anything you want to keep:
rmdir /s "%USERPROFILE%\.pie"
No. On macOS, skill scripts run in an OS-level SRT sandbox: no network unless the skill declares specific domains, writes only inside the session workspace, and cannot read sensitive folders. The Windows public beta does not include this SRT sandbox declaration. Approval cards, scoped permissions, and the on-device audit log still apply on both platforms.
macOS supports Claude Code, Codex, Cursor, OpenCode, and Pi, including desktop-app handoff when the app is installed. The Windows public beta supports the terminal forms of Claude Code, Codex, Cursor, and OpenCode. Pi and desktop-app handoff are not included in this Windows beta.
TypeScript and JavaScript run on both platforms — Pie ships its own runtime. On Windows, Python runs only if a machine-wide Python is installed; per-user and Microsoft Store Python are ignored. Shell scripts (.sh) are macOS-only. For a skill that should work on both, use a .ts script.
Install Pie Link so webpage and conversation context can move into local files, skills, and AI tools—with your approval.