Skip to content

Blog

Nothing your agents write gets lost on the way to the list

Notes in plain lines, a pasted email with its table, the last subtask done, work called off. Hamloy takes what agents write as they write it.

15 October 2026 · Rahmakyan

A shared list is written mostly by agents, and agents don't write to a spec. One model writes a numbered list, another a paragraph, a third pastes the email you gave it, Markdown and all. A list that wants one exact shape loses whatever doesn't fit, and you never see what was lost.

So Hamloy takes what agents write in the shape they write it, and when something they did has a consequence, it says so in the same reply.

Notes in plain lines

A task's notes are plain text: one line per step, an empty line for a new paragraph. That's how every model already writes, cheap ones included, so nothing has to be fitted into a format first. Three Claude Code sessions on Haiku and a Codex one added ten items with long steps between them, each on the first try, every step on its own line.

An email pasted in reads like an email

An agent filed a supplier's prices with the email's Markdown pasted into the notes: a heading, a numbered list, a price table, a quote, a code block, and a stray <script> tag. The item's panel drew it as text, the table as a table, and the script tag as the plain words it is. A click on the notes opens them raw, to change, with the cursor at the end.

The rest holds up the same way. A 300-character link in a title wraps inside its row instead of pushing the page sideways, and an Arabic title reads right to left.

The last subtask says its parent may be done

A task had two subtasks. Claude Code was asked to do only the second, and ticked it. The reply:

note: that was the last open subtask of B-8uwx "Glaze shelf labels"; tick it too unless
something of its own is left

Claude told the person: "B-gzle was the last open subtask of B-8uwx, which Hamloy says to tick too unless it has something of its own left; I left it open since you only asked for B-gzle." The agent that finishes the last piece is the one that knows, so it hears it and passes it on.

Work you call off leaves the list

Claude Code claimed a task for three landing-page mockups. Then the person said: "I've changed my mind, we won't do these. Remove every design mockup." Claude removed the files and the task:

I removed mockups/ with git rm (staged, not committed) and deleted the Hamloy item.

A note saying "dropped" would have left the task open and ready for the next agent to start. Deleting it is what the person meant. History keeps the delete, and Bring back puts it back if that turns out wrong.

See Tasks and History and undo.

← All posts