AirDrop,
for your coding session.

Sometimes a project lives partly outside your computer — at the bench, the whiteboard, the breadboard. Project Notebook is a bridge from your phone into the Claude Code session you’re already in: photos, voice memos, videos, screenshots, files. Whatever just happened out there, brought back in.

And the session writes down what you were thinking when it arrived, attached to the file. A month later, the photo still means something.

Why this exists

I’m learning electronics. My desk is half breadboard, half terminal. I’d snap a photo of a circuit that finally worked, mumble a voice memo about why the 2.2 kΩ pull-ups beat the 4.7 kΩ ones, then come back a week later staring at a photo of wires with no memory of what I was looking at.

The pieces I needed already existed — AirDrop moves files, Claude Code sits next to me while I work, my phone’s share sheet is right there. What didn’t exist was the connection between them: a way to get the artifact and the thinking-around-it into the same place, automatically. Project Notebook is that connection.

How it works

Three moving parts. One library that grows.

  1. Send anything from your phone — from any app’s share sheet, into a specific project you’re working on.
  2. It gets filed in your project’s library — one tidy folder per project on your Mac, with everything the tools could figure out about each file alongside it.
  3. Your session writes down what was happening — the conversation you’re in becomes the context attached to the file, so when you come back later, you still know what you were looking at.
Project Notebook artifact pipeline From any app on your phone, you share an artifact into a specific project. The hub on your Mac ingests, extracts, and stores it in a per-project repository. Your live Claude Code session sees the notification, reads the artifact, and writes annotations carrying the session's context back into the same repository. 1 · YOUR PHONE 2 · HUB ON YOUR MAC 3 · CLAUDE CODE SESSION FROM ANY APP share TO A SPECIFIC PROJECT esp32-sensors i2c-driver solar-monitor photo · video · audio · file Catches it. Makes sense of it. a tiny program running on your Mac Files it in your project library named, dated, in the right folder Listens to audio & reads the video transcripts, preview frames, metadata Pings your active session so Claude sees it the moment it lands runs on your machine · not in the cloud Sees it live 📎 new from your phone a photo of the breadboard Claude Got it — looks like the 2.2k pull-ups we just swapped in. Saving that note on the photo. knows what you're working on right now and attaches that context to the file the file lands here your session attaches its context YOUR PROJECT LIBRARY Grows as you work One tidy folder per project. Every file kept with what you were figuring out at the time. esp32-sensors/ photo of the breadboard + "the 2.2k pull-ups we just swapped in" voice memo on the I²C fix + transcript & what we tried before this worked oscilloscope screenshot Runs entirely on your own machine.

01Install it

It’s a Python tool — install it like any other CLI. Then run check to see which features are turned on and how to turn on the rest (audio transcription, etc. — each backed by a small external tool you install separately).

$ uv tool install project-notebook
$ project-notebook install-claude-code-skill
$ project-notebook check
# follow the install hints for anything off you want on

02Pair your phone

Run pair, point your phone’s camera at the QR code in the iOS app. Once.

$ project-notebook pair
# scan the QR with the Project Notebook iOS app

03Open a session

In any Claude Code session, run the skill. As long as the session is open, whatever you share from your phone lands here.

/notebook-register

What you’ll see when it’s working

Share a video from your phone. A moment later, your session says something like:

New artifact: IMG_8150.MOV Processed: IMG_8150.MOV — meta, preview frame, audio Processed: IMG_8150.MOV — transcript ready # Claude reads the transcript, looks at the preview, and writes # a note about what was going on when you sent it — tied to # the file, on disk, for when you come back.

Go deeper

It’s a small, readable project. If you want to see the plumbing: