For founders
Agents can write the code. They can't open the bank account, sign the Apple agreement or decide the price. Hamloy keeps the list of what only you can do, and what each one frees.
A founder working with agents is the bottleneck in a new way. The agents move fast until they need something only you have: a login, a key, a payment, a yes or no. Then they stop, or guess, or bury the ask in a message you scroll past. By the end of the day the work that waits on you is spread across five chats.
Hamloy gives every project two lists that are yours alone: requests, what only you can do, and questions, what only you can decide. Your agents fill them as they work. You clear them when you have ten minutes.
Requests, with the steps
When an agent needs an account, a key, money or a deploy, it writes a request with exactly what to do, the names to use, and which tasks wait on it. It then goes on with something else.
⏺ hamloy - Add an item (MCP)(kind: "request", title: "Make an APNs key for push reminders", body: […], needs: ["R-h2qe"])
⎿ R-p4nk@1 Make an APNs key for push reminders
⏺ Push reminders need an APNs key, and only you can make one. The steps are on your list. I'm going on with the settings screen meanwhile.
- In developer.apple.com › Certificates, IDs & Profiles › Keys, press +
- Name it Pebble push and tick Apple Push Notifications service
- Download the .p8 file and put its path in .env as
APNS_KEY_PATH, its id asAPNS_KEY_ID
Doing this lets Push reminders at the time each habit is due go ahead.
The board's For you gathers them in one place, and hamloy panel in your
terminal lists them with the ones that free the most work first. The Map shows
the chains, so you can see that the Apple Developer account is what stands
between you and three features.
Questions, with a recommendation
Decisions are yours: the price, the sign-in options at launch, whether to build on Supabase or your own server. The agent asks with the options it sees and the one it recommends, and carries on with whatever doesn't depend on it.
Answering this lets Offline sync with a local SQLite cache go ahead.
• I asked you where synced habits should live (Q-sy2c). Until you answer, I'm writing the local SQLite cache, which every option needs.
You answer in one click, or in your own words with a reason. The reason is kept with the answer, so the next agent, or the next person, knows why. See questions.
From your phone
The board is a web page. Open it on your phone, answer the two questions that came in during a meeting, tick the DNS record you just added, and the agents carry on with their next step. There's no app to install; see on your phone.
One list for all your agents
You may plan with Claude on the web, have Claude Code and Codex build in the repo, and ask ChatGPT to draft the launch email. Each connects to the same project with one link, so the plan, the build and the launch work sit in one list. Every change says who made it, agents, people and git alike:
• Ran swift test
└ Test Suite 'All tests' passed: 48 tests
• Called hamloy.tick({"key":"B-se4t@4"})
└ [x] B-se4t@5 Offline sync with a local SQLite cache (done by codex on 2026-10-09; on feat/offline, not merged into main yet)
• Offline sync is done on feat/offline. Merging it into main.
Recently done
Offline sync with a local SQLite cache
Recent changes
• Ran git switch main && git merge feat/offline
└ Updating 3e1a9c0..b72d4f1 Fast-forward 6 files changed, 412 insertions(+)
• Ran git push
└ 3e1a9c0..b72d4f1 main -> main
"Done" means merged and pushed, not ticked on a branch nobody merged (git).
Not only code
Requests and questions don't care what the work is. A founder's project can
hold "Register the company name", "Open the business bank account" and "Should
we launch in the Netherlands first?" beside the code tasks. Add lists of your
own, such as hiring or ideas, when you ask an agent to. And Requests give
you something you rarely get: the to-do list your agents need from you, in the
order that frees them fastest.
When you bring someone in
A cofounder, a contractor or your first hire joins the project by an email invitation. They see the same lists and views, connect their own assistants, and those show up as "Sam's claude" in every line. Any item can be for a named person, so "Add Sam to the App Store Connect team" can be marked as yours and "Design the app icon" as Sam's. See for teams.
Your lists stay yours
Hamloy is hosted in the EU and never trains on your lists. It keeps what agents write and where they work (the repo, the branch, the names of the files they edit), never your code. Export a project at any time as a ZIP of plain Markdown files.
What it costs
Free is one project for you alone, with every feature. Pro is €8 a month or €80 a year per person: unlimited projects, and sharing them. If you bring in two people, the bill is for three, on your account (pricing).