WOODPECKER OS
Drive Claude Code from a notepad.
You write a note by hand, circle it, and Claude Code picks it up on your own machine. No terminal, no tab juggling. The work runs where your files already are, and you stay on a surface that isn't competing for your attention.
No accountsEnd-to-end encryptedRuns on your machine
okay let's hook up the payments to our app
nice, add refunds too
WRITE · CIRCLE · DONE — CIRCLE THE REPLY TO GO AGAIN
HOW IT WORKS
How the work gets
from pen to code.
You circle a note. It's encrypted on the canvas, and only your machine holds the key to read it. Claude Code does the work right there on your computer, then writes the reply back the same way. Circle that reply with a follow-up note and the same session keeps going:
AES-256-GCM, encrypted in your browser, decrypted only on your computer. The relay forwards bytes it cannot read.
The key travels inside the QR link's #fragment, device to device. Browsers never send it over the network.
Nothing to sign up for, nothing stored remotely. Everything lives in ~/.woodpecker/ on your own computer.
WHY A PEN
The typing was never
the hard part.
Agents now write code faster than you can read it. So the real work isn't producing lines anymore — it's holding the shape of what you're building in your head. Writing by hand is slow on purpose. What you write down, you remember, and you stay the one who knows what's actually going on.
GET STARTED
Set it up once, in about a minute.
No account, no signup, no API key pasted into a website. It uses the Claude Code login already on your machine — Claude Pro/Max or your own key.
On your computer: npx @woodpeckeros/connect. It finds your existing Claude Code login and generates an encryption key that never leaves the machine.
It asks which folder Claude Code should work in, every time it starts. That folder is the agent's whole world: edits and writes are confined to it by the guardrails. Point it at a repo, a notes folder, whatever you're working on (or skip the prompt with --dir).
Point your iPad or e-ink browser at the code it prints. That's the pairing: the key travels inside the link fragment, device to device.
That's the whole interface. Your agent reads what's inside the circle, does the work, and writes back in ink.
$ npx @woodpeckeros/connect Which folder should Claude Code work in? ~/code/myapp ✓ Claude Code found · using your login ✓ guardrails on · edits stay inside ~/code/myapp ✓ key generated · never leaves this machine scan from your tablet to pair ↴
key travels in the #fragment, servers never see it
waiting for your canvas ▍