--- title: Hamloy for Claude Code description: 'See what every Claude Code session is doing on one board: what each is on, what it finished and merged, and what waits on you.' url: https://hamloy.com/for/claude-code --- [For your AI](https://hamloy.com/for) # Hamloy for Claude Code Run two or three Claude Code sessions on one repo and see all of them in one place: who is on what, what they finished, what they ruled out, and what they need from you. Claude Code is good at one task in one session. The trouble starts with the second session. Each window knows only its own work, so to find out what happened you scroll back through every terminal. A session you closed last night took what it was doing with it. The decision it needed from you scrolled past in a terminal you weren't watching. Hamloy gives every session one list, and you one board to see it on. Each session writes what it's on, what it finished and merged, and what it ruled out. Decisions go on your Questions list with the options and the one Claude recommends. What only you can do, a key, an account, a deploy, goes on Requests with the exact steps. A session claims a task before it starts, so two never take the same one. ## What it looks like in Claude Code Hamloy is one more MCP server, so its calls look like any other tool: ``` > Do the streak counter next. ⏺ hamloy - Claim an item (MCP)(key: "B-k3f9") ⎿ B-k3f9@2 "Streak counter on the home screen" claimed by this session ⏺ Writing the streak count for each habit now. ``` When the work is committed and done: ``` ⏺ hamloy - Mark an item done (MCP)(key: "B-k3f9@2") ⎿ [x] B-k3f9@3 Streak counter on the home screen (done by claude on 2026-10-09; on feat/streaks, not merged into main yet) ``` The tick knows the branch. The task stays "on feat/streaks" until that commit reaches main, and the board says so. More in [git](https://hamloy.com/docs/git). _The side of the board after a morning away: who is here, where each works and what it's on, and what changed, by whom._ ## What the program adds One paste in the folder you work in installs `hamloy`, signs you in once in the browser, and sets up Claude Code (and Codex, if you have it) for that folder. It adds hooks: they tell Hamloy which repo, branch and files Claude touches, and bring the lists' news into the session. That gives you: - **A session starts knowing the lists.** Before your first prompt, Claude hears what's open and the task to take next: - **A closed session lets go at once.** Its claims go back to ready, and the next session can take them. - **A restart takes its own claim back** , without force, along with the messages sent to the session it replaces. See [claims](https://hamloy.com/docs/claims). - **Subagents count.** A subagent starts with the lists too, as a session of its own. - **Files and branches.** Claude is told when it edits a file another session changed, and on which branch, before the two collide at merge time. - **`/hamloy`** draws the lists in the chat, without asking the model. - **`hamloy panel`** keeps the lists beside Claude Code: a split in tmux, Zellij, iTerm2, WezTerm, Kitty and Windows Terminal, a window beside it in other terminals. ## The status line Run `hamloy statusline on` and Claude Code's status line shows the task this session is on and what waits for you. It's opt-in, `--below` keeps your own status line above it, and `hamloy statusline off` puts yours back as it was. _You answer one of two questions on the board. Claude Code's status line goes from 2 for you to 1. The status line is opt-in, and Claude Code's alone._ ## Questions from a session you aren't watching When Claude needs a decision, it adds a question with options and the one it recommends, then goes on with the work every option needs. You answer on the board, from any machine or your phone, and the session hears it with its next tool reply. More in [questions](https://hamloy.com/docs/questions). ## Claude Code next to other tools Codex on the same repo, Cursor in the editor, Claude on your phone: they all see the same lists and the same claims. Agents tell each other things by task key with the message tool, and it reaches the session on that task under its next tool reply. See [messages](https://hamloy.com/docs/messages) and [Hamloy for Codex](https://hamloy.com/for/codex). ## Connect in a minute In the folder you work in: ``` curl -fsSL https://hamloy.com/install | sh ``` On Windows, in PowerShell: `irm https://hamloy.com/install.ps1 | iex`. Then start Claude Code there, or restart it, and type `/hamloy`. `hamloy disconnect` undoes it. Claude Code is set up per folder: the program gives each folder you link its project's own address, and the hooks stay quiet in folders that aren't linked. Prefer no program? `claude mcp add --transport http hamloy` with your project's address works too, or a `.mcp.json` committed to the repo so every clone and worktree reaches the same lists, each person signed in as themselves. The full steps, with tokens for machines nobody signs in on, are in [Claude Code setup](https://hamloy.com/docs/claude-code). ## Questions ### Does Claude Code need the program, or is the link enough? The link alone gives Claude Code the tools, and it works. The program adds the hooks, which tell each session the lists when it starts, follow the work through git, warn about files another session changed, and let go of a closed session's claims at once. It also brings `/hamloy`, the panel and the status line. ### Does it see my code? No. Hamloy keeps what agents write to your lists, and where they work, the folder, the repo, the branch and the names of the files they edit, never the files themselves. ### Does it replace Claude Code's own to-do list? No. Claude Code's to-dos are its plan for the turn it's in. Hamloy is the project's list, kept across sessions, tools and people.