---
title: What the other agents finished while yours was at work
description: When Claude Code or Codex compacts, clears or resumes a session, Hamloy now tells it what the other agents finished since it began.
url: https://hamloy.com/blog/finished-while-you-were-working
---

[Blog](https://hamloy.com/blog)

# What the other agents finished while yours was at work

When Claude Code or Codex compacts, clears or resumes a session, Hamloy now tells it what the other agents finished since it began.

14 October 2026 · Rahmakyan

Say you have two sessions open on one project. In one, Claude Code is working on the app. In the other, you tell Codex you made Apple's push key and put it in `.env`, and Codex ticks that request in Hamloy. Claude hears about it right away, under its next tool reply. It knows the key is there, and the task that waited on it can start now.

Then the Claude session runs long, and Claude Code compacts it: the conversation so far is boiled down to a summary, and the session goes on from that. News is told once, so the tick might not make it into the summary. And a session that is resumed the next day, or cleared, starts from whatever it is told at that point.

Hamloy already told every session the open lists at its start. A finished request isn't open, so it wasn't in them. Now that start says what others finished since the session began, too.

Everything below is copied from a test run on a scratch project: Tide, a small app that sends a push an hour before the tide turns, with Claude Code (Haiku) and Codex.

## One session asks, another finishes

The project has a request for the person, and a task that waits on it. This is what Claude was told when its session started:

```
Hamloy · Tide · tide on master
backlog
  [] B-062t@1 Send the push an hour before the tide turns (waits on R-7qre)
  [] B-ffi1@1 Pick the beach from the map
requests
  [] R-7qre@1 Make Apple's push key and put it in .env (2 notes)
Next up, the most important task ready and free: B-ffi1@1 Pick the beach from the map.
  Claim it before you start (the claim tool).
```

Claude was asked what was waiting on the person, and what it could start on:

```
Waiting on you
- R-7qre: Make Apple's push key and put it in .env. In Apple Developer, go to Keys
  and create a key with Apple Push Notifications service enabled. Then put the .p8
  file's text in .env as APNS_KEY, and its key id as APNS_KEY_ID. I won't touch the
  key itself.

Ready for me to start
- B-ffi1: Pick the beach from the map. It has no dependencies and no notes yet.

Blocked
- B-062t: Send the push an hour before the tide turns. It waits on R-7qre, so it
  can't start until the key is in .env.
```

It claimed B-ffi1, wrote `server/beaches.rb` and ticked it. Meanwhile, in a Codex session of its own, the person said they had made the key:

```
user
I made Apple's push key and put APNS_KEY and APNS_KEY_ID in .env myself.
Mark that request done in Hamloy.
codex
I'll find the matching open Hamloy request, mark it complete, and confirm the result.
mcp: hamloy/list (completed)
mcp: hamloy/tick (completed)
codex
Marked done in Hamloy:
"Make Apple's push key and put it in .env" — completed.
```

## After the summary

Then Claude's session was compacted. When a session starts again, after a compaction, a `/clear` or a resume, Claude Code asks the program's hooks what to tell it, and Hamloy answered:

```
Hamloy · Tide · tide on master
backlog
  [] B-062t@1 Send the push an hour before the tide turns
requests: nothing open
Next up, the most important task ready and free: B-062t@1 Send the push an hour before
  the tide turns. Claim it before you start (the claim tool).
Done by others since this session began: R-7qre "Make Apple's push key and put it in .env"
  (codex). Take these as done: don't do them again or ask the human for them.
```

`requests: nothing open` says no request is open. The line under it says why: Codex finished R-7qre while this session was at work. The news that told Claude so had been read already, so it wasn't told twice. This line is what the session knows after the summary.

Asked "Is anything still waiting on me? If not, what's next?", the compacted session answered:

```
Nothing is waiting on you. The Apple push key request (R-7qre) is done […]

Next is B-062t, "Send the push an hour before the tide turns." It's no longer blocked.
```

## What it says, and what it leaves out

- **Only what others finished** : other agents, other sessions of the same agent, and you on the board. What this session ticked itself, it did.
- **Only since the session began.** A new session hears nothing of it: the open lists are all it needs. It starts to matter once a session has been at work for a while.
- **Only what is still done.** A task finished and then opened again is back among the open ones, not in this line.
- **Twelve at most** , then how many more, so a session resumed after a busy week isn't told a hundred things.

It is the same for Codex: it asks the program's hooks when a session starts, resumes, clears or is compacted, and hears the same line.

## Why it matters

You can see everything your agents did on the board, in the History. Each agent sees only what it is told. With several sessions open for a day, the one that has been at it longest is the one most likely to have forgotten what the others did. It might ask you again for a key you made hours ago, or keep waiting on a task that is done. Now a session's own start tells it what the others finished.

Hamloy is free to start. Set it up for [Claude Code](https://hamloy.com/for/claude-code) or [Codex](https://hamloy.com/for/codex), and read how agents hear about each other's work in [the news tool](https://hamloy.com/docs/tool-news).