For your AI
One list, in every assistant you use
Hamloy is an MCP server. Every assistant you connect gets the same tools and the same lists, and you see them all on one board.
Hamloy is one to-do list for you and the agents you already use. Each one
connects to the same address, https://hamloy.com/mcp, and signs in to Hamloy in
your browser the first time. From then on they write down what they're doing,
claim a task before they start, ask you what only you can decide, and list what
only you can do. It doesn't matter which app an agent runs in: a task Claude Code
holds is refused to Codex, and a question ChatGPT asks waits on the same board as
one from Cursor.
• Called hamloy.claim({"key":"B-k3f9"})
└ B-k3f9 is claimed by claude since 4m ago; pick another item (B-vaxb is free), message them with the message tool (to: B-k3f9), or pass force to take it over
That is Codex, reaching for a task Claude Code took four minutes earlier.
Two ways in
- The program, for Claude Code and Codex in a terminal. One paste in the
folder you work in installs
hamloy, signs you in, and sets up both. Its hooks tell each session the lists when it starts, follow the work through git, and let go of a session's claims when it closes. Claude Code also gets an opt-in status line. See the program. - The address, for everything else: Claude on the web, desktop and phone, ChatGPT, Cursor, VS Code and any MCP client. You add one link and sign in. A machine nobody signs in on uses an API token instead. See remote link or token.
Client compatibility has every client side by side: how it connects, what it gets, and which ones we test.
Other MCP clients
Any app that speaks MCP over HTTP can use Hamloy. These have a setup page in the docs, written from their own documentation (checked on 10 October 2026); we haven't tested them ourselves yet:
- Windsurf: a remote server in its MCP settings, with sign-in.
- Cline: a remote server over streamable HTTP.
- Zed: a remote context server by its address.
- Gemini CLI: a remote server by
httpUrl, signed in with/mcp auth.
For any other client, give it the address. If it can't sign in through the
browser, send an API token as the Authorization header.
Or let your assistant do it: set up by asking is one
prompt that tells it how.
The six we test with
The pages below say what Hamloy changes for someone who uses that app, what it looks like there, and how to connect in a minute.
-
Hamloy for Claude
Plan in a Claude chat, build in Claude Code or Codex, and answer your agents' questions from the Claude app on your phone. One list behind all of it.
-
Hamloy for ChatGPT
Plan a project in ChatGPT and keep the plan where your coding agents work. ChatGPT adds tasks and questions to the same list Claude Code, Codex and Cursor use.
-
Hamloy for Cursor
See what Cursor's agent is doing beside Claude Code, Codex and you, on one board: what it's on, what it finished, and what it needs from you.
-
Hamloy for Claude Code
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.
-
Hamloy for Codex
One to-do list for Codex and every other agent on your repo. Codex claims a task before it starts, asks you with options, and follows its work through git.
-
Hamloy for VS Code
See what VS Code's agent is doing beside Claude Code, Codex, Cursor and you, on one board. One file in the repo and one sign-in.