Requests for what only you can do

Some steps an agent can't take. It can't enrol in the Apple Developer Program, pay for a domain, make a key in a dashboard it can't sign in to, or deploy where only you hold the password. Without Hamloy, it says so once, somewhere in a long run of output, and moves on. The step that was yours scrolls away, and you find out a week later when push reminders don't work.

With Hamloy, the agent puts it on the project's Requests list. A request says exactly what to do, which names and env vars to use, and what it frees once it's done.

What an agent writes

A request is added with the add tool, with the steps as its body. Here Claude, building push reminders for Pebble, a habit tracker, needs a key only the account holder can make. The key also needs the developer account to exist first, so the request waits on another one:

⏺ hamloy - Add an item (MCP)(kind: "request", title: "Make an APNs key for push reminders",
    summary: "A key only the account holder can make", body: [
      "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 as APNS_KEY_ID"],
    needs: ["R-h2qe"])
  ⎿ R-p4nk@1   Make an APNs key for push reminders  (waits on R-h2qe)
        A key only the account holder can make

The task that needs the key waits on the request:

⏺ hamloy - Add an item (MCP)(title: "Push reminders at the time each habit is due",
    section: "Next", needs: ["R-p4nk"], subtasks: ["Schedule a reminder per habit",
    "Open the habit from the notification"])
  ⎿ B-r5ne@1   Push reminders at the time each habit is due  (0 of 2 subtasks done; waits on R-p4nk)
      B-8kz9@1   Schedule a reminder per habit  (subtask of B-r5ne)
      B-bytp@1   Open the habit from the notification  (subtask of B-r5ne)

Then the agent tells you in one line and goes on with something that doesn't wait: "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."

The rules every agent gets with its first reply ask for exactly this: requests are what only the human can do (accounts, keys, money, deploys), with exact steps.

Where you find them

On the board, under For you, with your questions. They're in order of what they free: a request three tasks wait on comes before one that frees nothing. Each says what doing it lets go ahead, such as "Doing this lets Push reminders at the time each habit is due go ahead."

The Map draws the chain: the developer account first, then the key, then push reminders.

Claude Code's status line shows the count of what waits for you under every prompt, and hamloy panel lists it beside your agent. On the train, open your board on your phone and read the steps there.

When you've done it

Tick it on the board. Every agent on the project hears it under its next tool reply, and the work that waited is ready:

Hamloy news (what changed since you last looked):
- The human ticked R-h2qe "Create the Apple Developer account" (done)

An agent reading the key's request now sees the account as done, and what the key itself frees:

○ R-p4nk@1  request
Make an APNs key for push reminders
Waiting for you · added by claude

Waits on
  ✓ R-h2qe Create the Apple Developer account

Unblocks
  ⊘ B-r5ne Push reminders at the time each habit is due  0 of 2 subtasks done · waits on R-p4nk

You can also tell the agent in the chat that it's done; it ticks the request for you.

Your own work, too

Not everything for you is a request. When you say a task is yours, like recording the App Store preview video, the agent keeps it a task and marks it for you, and other agents leave it alone:

⏺ hamloy - Add an item (MCP)(title: "Record the App Store preview video", section: "Next",
    fields: {"for": "you"})
  ⎿ B-eo9w@2   Record the App Store preview video  (for the human, not for agents)

It shows under For you with your requests and questions.

Secrets stay out

A request names the env var, never the value. You make the key and put it in .env yourself; the list only says where it goes. Nothing secret needs to pass through Hamloy.

More in the docs: Requests. The decisions that are yours are Questions.