RADARFOX

    For developers who run more than one Claude Code session

    Three sessions running.
    Which one is waiting for you?

    One finished twenty minutes ago and you never noticed. Another has been stuck on a permission prompt, in a tab you haven't opened since lunch. The third hit an error and is just sitting there. So you flick through windows to find out, and lose the thread of what you were doing.

    ~/billingwaiting for you 18:00
    > Run the billing tests
    ? Allow Bash to run npm test?
    ~/shop-apiwaiting for you 23:00
    ● Edit src/routes/login.ts
    ✓ Opened PR #128
    Done. Nobody looked.
    ~/docswaiting for you 9:00
    > Rebuild the API reference
    ✗ API error 529 · stopped

    The cost

    Your sessions don't stop because they're done. They stop to wait for you.

    Claude Code doesn't get tired. It gets stuck: on a permission it needs, a question it asked, an error it can't get past. Every minute it waits for you is a minute it isn't working, and you only find out when you happen to look.

    shop-api
    billing
    docs
    13:0014:0015:0016:0017:00
    workingwaiting for youAn example afternoon with three sessions.

    On this afternoon, the three sessions spent 4 h 19 min waiting for someone who was looking at another window.

    billing · 14:02 → 14:31

    The prompt nobody saw

    It asked to run the tests at 14:02. You were in the other window. It waited half an hour for one click.

    shop-api · 15:40 → 16:30

    The job that finished alone

    It was done before you finished your coffee. You only noticed when you went back to check, fifty minutes later.

    docs · 14:00 → 15:10

    The error that stood still

    One failed call and the session stopped. Nothing blinks, nothing pings. It just sits there until someone looks.

    At a glance

    One look tells you what's going on.

    With several sessions open, Pix shows the most urgent one, so you only switch windows when it's worth it.

    Working

    Typing on his laptop while Claude works, with the tool it's using in his thought bubble.

    Needs you

    Waving, with a "!", when a session asks you something or is waiting for your reply.

    Asking to approve

    Pointing, with a "?", when Claude wants permission to use a tool. Allow or deny from his popout.

    Something failed

    Dizzy, with stars, when a call to the API fails, so a stuck session never goes unnoticed.

    Done

    A fist in the air and a thumbs up when a session finishes.

    Nothing to do

    Meditating, when no session is running.

    The thought bubble

    He knows what Claude is doing.

    While a session works, the prop in Pix's thought bubble follows the tool it's using.

    Pencil
    Edit · Write
    Magnifying glass
    Read · Grep · Glob
    Globe
    Web search and fetch
    Little Pixes
    Subagents
    Hourglass
    A long command
    Rocket
    git · gh

    Getting in

    Three steps, and he's on your screen.

    1. 01

      Ask for an invite

      Leave your name and email above. We invite testers in small groups.

    2. 02

      Install and paste your key

      The invite brings the download and your key. Drag Pix into Applications, open him and paste it.

    3. 03

      Turn on the hooks and work

      One click lets Pix follow your Claude Code sessions. From then on, he shows you which one needs you.

    Pix · closed beta for macOS

    Get Pix on your screen.

    Pix sits on top of your windows and acts out what your sessions are doing: typing while they work, waving when one needs you, celebrating when one finishes. Click him to approve permissions and answer questions without hunting for the right window.

    • Every state at a glance: working, waiting for you, asking to approve, failed, done.
    • Allow, deny or answer straight from his popout. Claude keeps its own prompt too; whichever answers first wins.
    • Everything stays on your Mac. No account, no analytics.

    Free during the beta. We invite testers in small groups.

    Pix is the mascot of Radarfox, which matches developers with vetted companies, anonymously until both say yes. See how Radarfox works

    Request an invite

    Profile
    System

    We use your email to send the invite. Your key works on one Mac, and Pix checks in with Radarfox every few hours to keep your beta access valid; it never sends anything about your sessions.

    Questions

    Before you ask.

    Is it free?

    Free during the beta. Testers will be the first to hear what comes after it.

    Does Pix see my code or my sessions?

    Pix reads your Claude Code sessions on your Mac to know their state, and keeps it there. Every few hours it checks in with Radarfox with your licence key, a device code and its version, to keep your access valid. It never sends anything about your sessions or your code.

    Which Macs does it run on?

    macOS 14 Sonoma or later, on a Mac with Apple silicon (M1 or newer).

    What do I need?

    Claude Code. Pix follows its sessions through Claude Code's own hooks, which it sets up for you in one click, and shows titles and pull requests when you use Claude Desktop too.

    Can I use my key on two Macs?

    Each key works on one Mac. If you change computers, write to us and we'll move it.

    What's Radarfox?

    Radarfox matches developers with vetted companies, anonymously until both say yes. Pix is its mascot.

    Want him on your screen?

    The beta is closed and free. Ask for an invite and we'll send it as soon as a spot opens.

    Request an invite