Pie Link

Connect Pie to your computer.

Pie Link is the local bridge between the Pie extension and this computer. Once it’s installed, Pie can run local skills with real scripts, reuse the skills you keep for other AI tools, and put Claude Code, Codex, or Cursor to work — right from your chat.

Skills you built in other AI tools work in Pie, unchanged.

Download for macOS (.pkg) Download for Windows Coming soon

macOS 13+ · Apple Silicon & Intel · Free · Open source · Notarized

With vs. without

What changes when you install it.

Pie is complete without Pie Link — everything in the browser keeps working. Pie Link adds exactly one thing: this computer.

Without Pie Link

The full browser assistant, nothing missing:

Read pages, operate websites, extract and export data — every in-browser capability
Read local files and save results as files, through standard browser mechanisms
Pure-computation skill scripts still run, inside the extension’s own sandbox
Recording and replay, schedules, BYOK and Membership — all unchanged

What stays out of reach:

Skill scripts that need file or network access can’t actually execute
Skills in the shared local skill folder are invisible to Pie
No delegating a task to local Claude Code and getting the result back
No handing work off to the AI coding tools installed on this machine
The “Local bridge” section in Settings stays disconnected

With Pie Link

Everything on the left, plus this computer:

Skill scripts run as real local processes, inside an OS-level sandbox
The shared skill folder plugs in — skills written in other AI tools just work
Delegate: local Claude Code runs a bounded task and the result returns to your chat
Hand off: Pie packages the context and passes it to Claude Code, Codex, Cursor, and more
A per-session workspace on disk — script outputs flow back into the conversation
A menu bar icon with live connection status and one-click diagnostics

One skill ecosystem

Build a skill once. Use it everywhere.

A skill is just a folder with a SKILL.md file — an open format shared across AI tools. Pie Link connects Pie to both skill folders on your machine, so your skills stop being tied to a single product.

~/.pie/skills Pie’s own skills

Skills that Pie records and saves for you live here. Read-write: Pie can create them, update them, and run them.

~/.agents/skills The shared folder

The cross-tool folder where Claude Code and other AI tools keep their skills. Pie reads it as-is — nothing to copy, convert, or re-import.

No rewritingA skill you refined in another tool is ready in Pie the moment it lands in the shared folder — type / and run it.

Aligned with the ecosystemSKILL.md is the open convention AI tools are converging on. Skills stay portable — yours, not any single product’s.

Scripts really runSkills that ship scripts truly execute — TypeScript, Python, or shell — sandboxed, with outputs returned to the conversation.

Two ways to use local tools

Delegate a task, or hand it off.

With Pie Link, Pie can put the AI coding tools on this machine to work. There are two modes, and the difference is simple: where does the work end up?

Run — delegate, get the result back

You say“Fix the bug from this issue page in my local repo, then tell me what changed.”

Pie sends one bounded task to local Claude Code, waits while it works unattended, and brings the outcome back into the same conversation. Before anything starts, you see the exact prompt and working directory on the approval card.

Best for

Bounded jobs with a clear finish line — fix a bug, run a script, query a repo
Work where the conversation should continue in Pie once the result is back
Tasks that need no steering while they run

Handoff — pass the baton, continue there

You say“Solid research. Package it up and hand it to Claude Code — I’ll take it from there.”

Pie writes everything it gathered — context, files, findings — into a fresh local folder and opens the tool you choose. The task leaves the browser; you and that tool carry it forward.

Best for

Open-ended, long-running work — a big refactor, a writing project, a deep dive
Tasks you want to steer interactively as they unfold
Work that belongs in an editor or a terminal, not a browser panel

Rule of thumb: if the result should come back to this conversation, Run. If you’ll keep working on it locally, Handoff.

Run currently targets Claude Code. Handoff supports Claude Code, Codex, Cursor, OpenCode, and Pi — and the recipient is always chosen by you on the approval card, never by the model.

Security model

Local power, on your terms.

Pie Link touches your computer, so it has to earn it: every local action is approved by you, sandboxed by the OS, and logged on disk. Here is the actual model.

You approve every actionEach local action shows an approval card first. Delegations display the exact prompt and working directory — verbatim, never paraphrased by the model — and ask again every time.

A revocable grant ledgerApproved skill permissions live in a ledger on your machine, revocable in Settings. If a skill’s code or permission claims change at all, the old grant is void — it asks again.

OS-level sandboxingSkill scripts get no network unless the skill declares specific domains, write only inside their session workspace, and can’t read sensitive folders like your SSH keys.

No code over the wireWhich apps launch and which scripts run comes from a fixed local list. The model passes only IDs and arguments — never shell commands, never code.

An audit trail on diskEvery local action is appended to a local audit log — what ran, with which permissions, how it exited. The log stays on your machine.

Open source, signed, notarizedPie Link ships in the same Apache-2.0 repository as the extension. The installer is Developer ID signed and notarized by Apple. Read the code before you trust it.

Install

Three steps, no configuration.

Requires macOS 13 or later · one universal package for Apple Silicon and Intel · works with Chrome

Download

Grab the latest pie-link.pkg. The link always points to the newest release.
Download for macOS (.pkg)
Run the installer

Double-click the .pkg and follow the prompts. The package is signed and notarized, so macOS installs it without warnings.
Look at the menu bar

A Pie icon appears in the menu bar — that’s success. Back in the Pie extension, the “Local bridge” section in Settings connects automatically.

FAQ

Good to know.

Which systems does it support?

macOS 13 or later today, as one universal package for Apple Silicon and Intel, working with Chrome. A Windows version is on the way.

How do I update Pie Link?

Download the latest .pkg and run it — it installs right over the old version. The Pie extension will let you know when an update is required.

Does Pie still work without it?

Fully. Everything in the browser is unaffected — Pie Link only adds the local capabilities described above, and you can uninstall it at any time.

How do I uninstall it completely?

Pie Link installs a handful of well-known files and nothing else. These steps remove every one of them.

Quit Pie Link from the menu bar: click the Pie icon, then Quit.

Unload and delete the two startup 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

Delete the menu bar app:

sudo rm -rf "/Applications/Pie Link.app"

Delete the command-line binaries:

sudo rm /usr/local/bin/pie /usr/local/bin/pie-host

Delete the Chrome native messaging manifest:

rm "$HOME/Library/Application Support/Google/Chrome/NativeMessagingHosts/ai.wiseria.pie.json"

Delete Pie Link’s data folder. It holds your local skills, session workspaces, and grant records — back up anything you want to keep first:

rm -rf ~/.pie