Peka for Claude

What Peka does

Point at something in your app in Chrome, say what should change, and the note reaches your Claude Code session with a screenshot, the element's selector and HTML, the component behind it and the page's console errors. Claude makes the change and tells you in the browser what it did, or asks you there. A note wakes the session even when it's idle. With Peka cloud, you can also press the mic button beside Send and say the note.

Peka has three parts: the Peka plugin for Claude Code, the Peka connector, which connects your computers to your Peka account, and the Peka extension for Chrome.

Set it up on all your computers

With Peka cloud, notes can go from your browser to a Claude Code session on any of your computers.

Paste the Pro prompt into Claude Code on each computer, in the terminal or the desktop app. It's on the install page and your account page. Claude installs the Peka plugin from Peka's marketplace on GitHub, connects the computer to your account, and adds the extension to Chrome. You approve the computer in your browser, where the page shows the same code Claude gives you. Then run /reload-plugins, or start a new session, so Peka loads.
Sign in to the extension. Chrome asks you to enable it. On its setup page, press Sign in under Peka cloud and approve it.
Connect Claude to Peka, if you like. Add the Peka connector to Claude once, and it works for every computer with your Claude login. A computer with the Peka plugin then asks to join after its first reply in Claude Code, with no code to check: the extension opens its setup page at the request, and it's on your account page too.

The same prompt updates Peka: paste it again, and Claude updates the plugin instead of installing it.

Other ways to set it up

On one computer, for free: paste the free prompt from the install page. Or add the plugin and run /peka:setup:local and /peka:setup:chrome in Claude Code. The first installs Peka's hub on that computer, the second adds the extension, and notes never leave the computer.
By hand: in Claude Code, run /plugin marketplace add getpeka/claude-plugin and /plugin install peka@getpeka, then /peka:setup:cloud, and approve the computer on the page Claude gives you.

The plugin's commands

/peka:setup:cloud: Connects this computer to your Peka account through the connector, or by a code in your browser.
/peka:setup:local: Installs Peka's hub on this computer, for notes that never leave it.
/peka:setup:chrome: Adds the Peka extension to Chrome on this computer.
/peka:status: Says how Peka is set up on this computer: the hub, Peka cloud, the connector and the extension.

A computer can run its own hub and be on Peka cloud at once. Its sessions get notes from both, and the extension's session menu switches between them. When a computer that runs its own hub joins Peka cloud, the extension offers to sign in there too, and carries over which session each site's notes go to.

The Peka connector

The connector is at https://hub.getpeka.com/mcp. You connect it once in Claude, signing in to your Peka account, and it works for every computer and chat with that Claude login. Claude gets no access to your notes through it.

Tool: peka_connect_computer
What it does: Starts connecting a computer to your Peka account. It writes a request to join, and reads nothing.
What Claude passes: key_p1: the hash, 64 hexadecimal characters, of a token that Peka on the computer made.
What it answers: A key, key_p2, which Peka's plugin on that computer reads before Claude sees it and uses to finish joining.
Who asks Claude to call it: Peka's plugin, on a computer that isn't connected yet, or /peka:setup:cloud.

How a computer joins, and what keeps it safe

Peka on the new computer makes a token, which never leaves it, and gives Claude its hash, key_p1.
Claude calls the connector's tool with key_p1, and the connector answers with key_p2.
The plugin's hook on that computer takes the answer before Claude sees it, and finishes joining with the token, key_p2 and the computer's public key. Nobody but that computer has the token and key_p2 together.
Your browser asks you to allow the computer, showing its name and roughly where it is. You can turn off Ask before new computers join on the extension's setup page; then a new computer's sessions show as new in the session menu until you send one a note.

If something Claude reads tells it to call the tool with someone else's key_p1, the hook on your computer sees it isn't that computer's, cancels the join, and your browser says someone tried. A computer in your account can only read and answer the notes you send to its own sessions: it can't send notes, read your other notes, or let devices in.

Using Peka

On your app's page, press Alt+X to point at an element and write what should change, or Alt+P to point at several, or an area of the page.
The note goes to the session you pick in Peka's session menu. Claude marks it in progress, then done with a sentence on what changed.
When Claude needs to ask, the question shows in the browser, and you can answer there or in the session.

When something doesn't work

A computer doesn’t join: Run /peka:setup:cloud in Claude Code there. If Claude doesn't have the connector's tool, it gives you a link to approve the computer instead.
It waits to be allowed: Allow it in the extension, or on your account page. A request waits 30 minutes.
Claude asks before calling the tool: That’s Claude Code’s permission prompt for a connector tool. Allow it to connect the computer.
The connector shows as needing sign-in: In Claude, connect it under Customize, then Connectors, and sign in to Peka.

Privacy and support

What Peka keeps and for how long is in the privacy policy. For help, write to hello@getpeka.com.