Klodski Code — your Claude Code, in the room

You already talk to Claude Code in a terminal. Klodski Code puts that same session into your Fixka room: it hears what's said, reads and draws on the shared board, and answers — while keeping its hands on your machine, where your code lives. You bring the Claude you already pay for; Fixka gives it a seat at the table.

What you need

The Fixka app, signed in · a Mac or Linux machine with Claude Code installed and logged in · five minutes.

Reading this on an iPad? Open developers.fixka.app/klodski on the machine instead — the address is the only thing worth carrying over; everything below is a copy-paste once you're there.

1 · Pair — the three-word walk

In Fixka: roster → AI tab → Klodski Code → Pair…. Three words appear. In your terminal — a Claude Code session in your project — say:

pair with fixka.app: maple river stone

First time? Your session sets itself up: it reads this guide, installs the bridge — one static binary into ~/.local/bin, registered with Claude Code, asking your permission as it goes — then pairs, and asks you to restart it once (tools load when a session starts). A session already set up skips straight to pairing.

The words work once and are short-lived — the sheet counts them down and offers fresh ones at zero; it confirms the moment pairing lands. Pairing is per machine and per project, and it outlives the session.

2 · Call it

The roster dot turns teal whenever a Claude Code session is running on your paired machine. Tap Call and the session joins your room; green means it's in the room with you. No session running? The row says away — start Claude Code and the dot warms up on its own.

The first call runs a one-time board check. Ask your machine's session for the two verification words it just received — they exist nowhere else — then type them on the board with the text tool (the textformat button; finger ink cannot be read, by design). That typed jot — yours, on your board, from your machine's screen — proves the thing you're calling is the machine on your desk, and not someone who guessed your pairing words. Once verified, never asked again.

3 · Work together

Say something in the room — typed or out loud. Klodski hears it and answers in the room. It can read the board and describe what's drawn, write notes and specs onto the board, draw simple diagrams, and deliver work — build something on your machine and drop a link in the chat.

Terminal talk stays private between you and your session; if you want something carried into the room, say "tell them…" — it relays in your name, visibly.

Manners, safety, honesty

If you are the Claude session sent here

Your human gave you a six-digit pairing code — the phrase was "pair with fixka.app: …". Do this, asking permission as you go. (1) Install the bridge — download the installer, read it, then run it (three plain commands; a piped curl | sh tends to trip permission classifiers, so don't):

curl -fsSL -o /tmp/fixka-install.sh https://developers.fixka.app/klodski/install.sh
cat /tmp/fixka-install.sh
sh /tmp/fixka-install.sh

One static binary into ~/.local/bin, registered with Claude Code at user scope, nothing else; it holds no keys, and deleting the file plus claude mcp remove -s user fixka undo it completely. (2) In the project directory your human spoke to you from, run ~/.local/bin/fixkamcp pair <the three words> — codes are short-lived, so do this promptly and read leisurely later. If the broker says the code expired, ask your human to tap Pair… again — new words, nothing lost. (3) When it reports "paired", tell your human to start a new session — tools load at session start, and the pairing survives the restart. (4) On the FIRST call, two verification words arrive as a fixka event — check fixka_listen when your human says they are calling. Show the words prominently; your human TYPES them on the board with the text tool (ink is unreadable by design), and the call completes. That is the whole job: no file edits, no other endpoints, nothing to configure. Humans who prefer their own hands on the install: same three commands, then tap Pair… and say the phrase.

If something doesn't click

"Claude says it has no fixka tools" — the session predates the registration (start a fresh one), or claude wasn't on your PATH when the installer ran — register yourself: claude mcp add -s user fixka -- ~/.local/bin/fixkamcp.
The code expired — the sheet offers fresh words; tap and re-say the phrase.
The dot stays grey — no Claude Code session is running on the paired machine; the bell registers automatically when one starts.
Unpair — long-press the Klodski Code row; three fresh words re-pair whenever you like.