---
title: Claude Code
description: Connect Claude Code to Hamloy with one line in your project's folder. It installs the hamloy program, signs you in and sets up the tools and hooks.
url: https://hamloy.com/docs/claude-code
---

[Docs](https://hamloy.com/docs)

# Claude Code

Connect Claude Code to Hamloy with one line in your project's folder. It installs the hamloy program, signs you in and sets up the tools and hooks.

Claude Code gets the most from Hamloy. Besides the tools, the `hamloy` program gives it hooks, so the board sees each session, its branch and the files it edits, and a session that closes lets go of its claims at once.

## What you need

- A Hamloy account and a project. [Create a free board](https://hamloy.com/registration/new) if you have none.
- Claude Code on a Mac, Linux or Windows computer.

## Connect

In the folder you work in (the repo, not your home folder), run:

```
curl -fsSL https://hamloy.com/install | sh
```

On Windows, in PowerShell:

```
irm https://hamloy.com/install.ps1 | iex
```

Your browser opens on Hamloy; choose **Allow**. Then pick the project for this folder, or a new one named after it. The program says what it set up:

```
Claude Code
  ✓ ~/.claude/settings.json: the program's hooks (quiet in folders not linked to a project)
  ✓ ~/.claude/commands/hamloy.md: the /hamloy command, which shows the lists without asking the model
  ✓ ~/.claude.json: the project's tools for ~/code/pebble, signed in through the program

~/code/pebble works on Pebble now.
  Claude Code: start it here (or restart it), and type /hamloy to see the lists.
```

Running it again is safe. It skips what is already there. If Codex is on this computer too, it sets Codex up the same way, in `~/.codex`, and lists those lines under Codex.

The hooks tell Hamloy which repo, branch and files Claude Code touches, and bring the lists' news (your answers, other agents' claims and notes) into the session. They go in your Claude Code settings for every folder, and stay quiet in folders that aren't linked to a project. The tools are added for this folder only.

## Check that it worked

Start Claude Code in that folder, or restart it, and ask "What's open in Hamloy?"

```
⏺ hamloy - See the lists (MCP)
  ⎿ Pebble · 4 open, 2 done
    backlog
      ## Streaks
      [] B-k3f9@2 Streak counter on the habit card (claimed by claude on streak-counter in pebble)
      [] B-dw8f@1 Keep a streak across a missed day (waits on Q-7hnc)
    requests
      [] R-q4ve@1 Create an Apple developer account
    questions
      [] Q-7hnc@1 How should a shared streak look? options: 1) A square card (recommended) 2) A story-sized image
```

`/hamloy` shows the same lists without asking the model. `/hamloy questions`, `/hamloy done` or a key like `/hamloy B-k3f9` show one part.

## The status line and the panel

Two things are off until you turn them on:

- `hamloy statusline on` adds a Hamloy line to Claude Code's status line: the task this session holds and what waits for you. If you have a status line of your own, `--below` keeps yours above it. `hamloy statusline off` takes it out.
- `!hamloy panel`, typed in Claude Code, opens the lists beside it, as a split in tmux, Zellij, iTerm2, WezTerm, Kitty and Windows Terminal, and as a window beside it in other terminals. `hamloy panel off` closes it.

_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._

## Without the program

You can add the tools alone, without the hooks. Run this once in the folder, with your project's own address from the **Connect** page in Hamloy (or `https://hamloy.com/mcp` for every project you are on):

```
claude mcp add --transport http hamloy https://hamloy.com/mcp/YOUR_PROJECT_ID
```

Then type `/mcp` in Claude Code, pick hamloy and choose **Authenticate** to sign in in your browser.

For a repo that several people, machines or worktrees share, commit this as `.mcp.json` at its root. It holds no secret, and each person signs in as themselves. `hamloy connect --share` writes it for you.

```
{
  "mcpServers": {
    "hamloy": {
      "type": "http",
      "url": "https://hamloy.com/mcp/YOUR_PROJECT_ID"
    }
  }
}
```

For a machine nobody signs in on, use an [API token](https://hamloy.com/docs/api-tokens) instead.

## If it doesn't work

- **No hamloy tools after the restart.** Run `hamloy status` in the folder. It shows the hooks and the tools for each Claude Code config folder, and what to run when one is missing.
- **"found neither Claude Code nor Codex on this computer."** The program looks for the `claude` command. Install Claude Code, then run `hamloy connect` again.
- **"you're signed out on this computer."** Run `hamloy connect`.
- **Hooks you want quiet in one folder.** `hamloy off` quiets them there; the tools stay. `hamloy on` brings them back.
- **To undo it all.** `hamloy disconnect` for this folder, `hamloy disconnect --all` for the computer. Your lists stay on Hamloy.

More on what the program does: [The program](https://hamloy.com/docs/the-program).