---
title: Plan in Claude, build in Claude Code
description: Talk the plan through in Claude or ChatGPT, on the web or your phone. It lands in Hamloy as tasks, and Claude Code or Codex builds from the same lists.
url: https://hamloy.com/use-cases/plan-and-build
---

[Use case](https://hamloy.com/use-cases)

# Plan in Claude, build in Claude Code

The thinking happens in a chat, the building in a terminal. Hamloy is the list between them, so nothing is copied across and nothing is lost when the chat ends.

Many people plan in one place and build in another. You talk a feature through with Claude on the web or the phone, or with ChatGPT, until the plan is good. Then you open a terminal, start Claude Code, and paste the plan in, or summarise it from memory. The chat that made the plan knows nothing of what got built. The next chat starts from scratch.

With Hamloy both ends call the same lists. The chat writes the plan as tasks, questions and requests. The agent in your terminal reads them, claims a task and builds. The chat can look again later and see what is done.

## Connect both ends once

- **Claude** (web, desktop, phone): Customize › Connectors › + Add › Add custom connector, name it Hamloy, give it `https://hamloy.com/mcp`, and sign in. One connection works on every device. See [Claude](https://hamloy.com/docs/claude).
- **ChatGPT** (on the web): Plugins › + › Add custom MCP server, with the same address. See [ChatGPT](https://hamloy.com/for/chatgpt).
- **Claude Code and Codex** : the one paste in your repo's folder, which installs the `hamloy` program and connects the folder ([Claude Code](https://hamloy.com/docs/claude-code), [Codex](https://hamloy.com/docs/codex)).

The address `https://hamloy.com/mcp` reaches every project you are on, so the chat names the project in each call. Claude Code, connected to the folder, is on that folder's project already.

## Plan in the chat

Say what you want in plain words: "Plan sync between devices for Pebble. Put it in Hamloy." Claude writes the plan where Claude Code will find it, with the pieces as subtasks and the open decision as a question:

```
hamloy - Add an item (project: "Pebble", kind: "question", title: "Where should
synced habits live?", options: [...], recommended: 1)
  Q-is21@1 Where should synced habits live? options: 1) Supabase: Postgres with
  auth and row-level security built in (recommended) 2) Our own Postgres on
  Fly.io 3) iCloud only, no server

hamloy - Add an item (project: "Pebble", title: "Sync habits between devices",
section: "Next", needs: ["Q-is21"], subtasks: [...])
  B-1nw7@1 Sync habits between devices (0 of 3 subtasks done; waits on Q-is21)
    B-ssbf@1 Local SQLite cache (subtask of B-1nw7)
    B-v7c6@1 Upload changes when online (subtask of B-1nw7)
    B-x51r@1 Resolve two edits of one habit (subtask of B-1nw7)
```

A plan written this way keeps its reasons. The notes under a task hold the detail, a one-line summary says what it is, and the question holds the options you weighed. If something needs you (an account, a key, a payment), the chat adds it as a request with the steps.

## Decide on the way

You can answer the question in the same chat, or later on the board. On the board it looks like this, with the option Claude recommends marked:

Answering it frees the task that waits on it. If you're not sure yet, leave it open: Claude Code will do the parts that don't depend on it first.

## Build in the terminal

Start Claude Code in the repo. A session starts by hearing the lists and its next task, so "carry on with the plan" is enough. It reads what is ready, claims a task and works:

```
⏺ hamloy - Claim an item (MCP)(key: "B-1nw7")
  ⎿ B-1nw7@1 "Sync habits between devices" claimed by this session
    note: it still waits on Q-is21 "Where should synced habits live?"; do only
    what doesn't depend on that, or assume an answer and go on
```

As it learns things it adds notes under the task, not in a new file. When a subtask is done it ticks it, and Hamloy follows the commit through git until it is merged ([git](https://hamloy.com/docs/git)).

## Look back from the chat

A week later, on your phone, ask Claude "what's left on sync for Pebble?". It lists the project and answers from what is there: which subtasks are done, which are done on a branch but not merged yet, and what still waits on you. You don't have to paste a status report anywhere.

## Codex, Cursor, and the other way round

The same works with any pair. Plan in ChatGPT and build in Codex. Plan in Claude Code itself and have Claude on the phone answer the questions. Or a second Claude Code session reviews what the first built, from the notes it left. Each client is one connection to the same lists; see [everywhere Hamloy runs](https://hamloy.com/get).

## What it costs

Free covers one project for you alone, with every app connected ([pricing](https://hamloy.com/pricing)).