Pi, in your Ardia's side panel.
A chat panel for the Ardia browser that runs your local Pi coding agent.
Ask about the page you're on, sort out your tabs, or have Pi click, type and read its way through the web.
Quick start · Make it yours · Contributing · MIT
- Now supports Chrome. The same Ardi panel, in the Chrome you already use. Works with your existing tabs and signed-in accounts. Get started →
- Works across your tabs. Ardi can list, read and open tabs, look at the images on them, and run anything else through
ardia exec. - Userscripts. Ask Ardi to change how a site looks or behaves on every visit: it writes a userscript, tests it on the real page and installs it once you're happy.
- Runs Ardia itself. Ask Ardi to split a pane, merge windows or switch to dark mode; to change a setting, shortcut or theme for good; to find something in your recent history; or to set up a hook that runs whenever a site opens. Ardia only.
- Mention tabs with @. Type
@to pick an open tab; it goes into your message as a chip, and Pi reads it. - Slash commands. Type
/to start a new chat (/new), free up context (/compact), or run one of your skills from~/.ardi/.agents/skills/.
side panel ⇄ background worker ⇄ native messaging ⇄ bridge (node) ⇄ pi --mode rpc
Extensions can't start local programs, so a small bridge runs Pi and streams its events back. Pi's session files under ~/.pi/agent/sessions are the record of each chat; the extension only keeps the chat list. One build puts all of it in dist/ardia/: the extension, the bridge and Pi's setup. Chrome gets its own copy in dist/chrome/.
You need Pi and the Node.js it runs on (22.19 or newer) on macOS or Linux; the Chrome version also runs on Windows. Building from source also needs Bun. In Ardia, turn on Settings → Advanced → Command Line → Let the ardia command control Ardia.
Download ardi-ardia-<version>.zip from Releases, extract it, and open a terminal in the extracted folder:
node install-host.mjs ardiaIn Ardia, open Settings → Extensions → Add extensions → Load unpacked extension, select the folder printed by the installer, and open Ardi from the extensions menu. You can delete the download afterwards. To upgrade, run the installer from the new release and reload the extension.
git clone https://github.com/YishenTu/ardi.git
cd ardi
bun install
bun run build
bun run host:install ardiaIn Ardia, open Settings → Extensions → Add extensions → Load unpacked extension, pick dist/ardia/, and open Ardi from the extensions menu. Keep the repository in place; this installation runs from its built files.
| What | Where |
|---|---|
| Prompt | src/agent/system-prompt.md is Pi's entire system prompt. |
| Tools | Ardia tools are in src/targets/ardia/agent/extension/; Chrome tools are in src/targets/chrome/agent/extension/. |
| Your instructions | Write them in ~/.ardi/AGENTS.md; they apply from your next new chat. |
| Skills | Drop them in ~/.ardi/.agents/skills/; they show up in your next new chat. |
| Which Pi | Set the Pi CLI path in Settings (the sliders button); leave it empty to use the Pi the installer found. |
Rebuild after editing the prompt or tools, then reload the extension.
Download and extract ardi-chrome-<version>.zip from Releases, then run node install-host.mjs chrome inside it. Requires Node and Pi, as above.
Open chrome://extensions, enable Developer mode, choose Load unpacked, and select the folder printed by the installer. For a source build, run bun run host:install chrome and load dist/chrome/ instead.
For Ardi to install userscripts, open Ardi's Details in chrome://extensions and turn on Allow User Scripts.
Contributor and agent guidelines are in AGENTS.md.