Read your assistant's night shift, and put back what it deleted

Letting an assistant work while you sleep is only comfortable if you can read the night back in the morning, and undo what you wouldn't have done. Hamloy keeps every change to your lists: who made it, when, and what it was. Now you can read all of it in one place, and bring back anything that was deleted.

Ravi's night, on the board

Ravi let Claude work on their habit app alone overnight. In the morning they opened History, under Overview on the board. It shows every change by everyone, day by day, with the time of each, the latest first:

TODAY
07:14  git merged the work of Streak counter on the home screen
07:12  claude finished Streak counter on the home screen
06:40  claude renamed Weekly summary email (was “Weekly digest”)
05:21  claude added a note to Haptic tap on check-off: Light tap, not medium
03:58  claude deleted Widget for the home screen · Bring back

A rename shows the name it had, so nothing changes under you unnoticed. Git's line says the work landed, not only the tick: Claude built the streak counter on its own branch, and History shows the moment it reached main. See How Hamloy follows git.

Scroll down and the earlier days load as you reach them.

Claude had deleted "Widget for the home screen", which Ravi still wanted. They pressed Bring back beside that line, and the board said:

“Widget for the home screen” is back.

The task was back where it was, with its notes, fields and history. Bring back is there for as long as the item is gone, whoever deleted it. Recent changes on the board has it too, and its See all leads to History.

Or ask your assistant

You don't have to open the board. Ask Claude or Codex "what did Claude do overnight? It deleted something it shouldn't have, put it back", and the list tool reads the history in one call:

list(history: true, limit: 5)

Pebble · changes, the latest first (UTC)
2026-10-11
  05:14 B-u5oh "Streak counter on the home screen": git merged feat-streaks into main
  05:12 B-u5oh "Streak counter on the home screen": claude ticked it
  04:40 B-w2kd "Weekly summary email": claude renamed it (was "Weekly digest")
  03:21 B-x060 "Haptic tap on check-off": claude added a note to it
  01:58 B-txqk "Widget for the home screen": claude deleted it
Older ones: from 5.
A deleted item comes back with edit's restore.

and puts it back with one more:

edit(key: "B-txqk", restore: true)

brought back B-txqk@3  Widget for the home screen

With find, the history narrows to one item, under any title it had. Reading or tidying the lists like this needs no task of its own, so your assistant just answers. See History and undo and the list tool.

Also new

• A whole task in two calls. Claude was asked to make the week view start on Monday. It claimed the task straight from what its session started with, and the claim brought the notes the last session had left. It changed the code and ticked the task with a full note of what it did and how it checked. Hamloy took two calls and about 550 tokens. See Claims.
• Two assistants add the same thing at once. Four Claude sessions were each asked to add the same three tasks at the same moment. Each add said which open item looked like the one just made, with that item's summary, and each session deleted only its own copies. The list ended with one of each.
• Codex finds the project from the folder. Connected once for all nine of its person's projects, Codex was asked about the planner without being told which project. The hamloy program had said which folder the conversation was in, so the list went straight to the planner.
• A tick you type waits for its merge. hamloy tick on a side branch now waits for the merge, as an agent's tick does, and a branch deleted without merging leaves it for you to call done anyway or open again. See How Hamloy follows git.
• Due dates from a calendar. On the board, a due date is picked from a calendar and shown in words: "due 20 Oct". See Fields.