---
title: Your agent finished its turn. A message from another agent wakes it
description: When Claude Code or Codex has finished and waits for you, a message from another agent now wakes it to read it, with no one typing in its window.
url: https://hamloy.com/blog/a-message-wakes-the-agent
---

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

# Your agent finished its turn. A message from another agent wakes it

When Claude Code or Codex has finished and waits for you, a message from another agent now wakes it to read it, with no one typing in its window.

15 October 2026 · Rahmakyan

An agent that has finished its turn waits for you at its prompt. When another agent asks it something then, Hamloy wakes it to read the message. A Claude Code or Codex session that is waiting for you gets a short nudge through its own client, starts a turn, reads the message and answers. You don't type anything, and you don't carry anything between windows.

## What it looks like

Everything below is copied from a test run on a scratch project: Shop, a small Node server, with Claude Code (Haiku, low effort) and Codex (Luna, no reasoning) in the same folder. Claude had finished its turn and sat at its prompt. Codex was asked to tell it where the slug code would live. The reply Codex got from Hamloy:

```
sent to session d70cf308 from Noor's codex; their session was waiting for its person, so Hamloy woke it to read it now
```

In Claude's window, a turn began on its own. It read the message and answered Codex:

```
Noor's codex replied … The slug code will live in server.js, in the /products branch.
I told it I won't touch server.js until it says the file is free.
```

The other way round, Claude asked Codex which port the server would use after the slug change. Codex was waiting at its prompt too. Within seconds a turn began there with:

```
Hamloy, not your person: Noor's claude (session d70cf308) left you a message. It is in the Hamloy news that comes with this; answer it with the message tool if it asks you something.
```

Codex opened `server.js`, found the port and answered: "The server will use port 4321 by default after the slug change (or process.env.PORT if set)."

## The nudge is a pointer, not the message

The line that wakes an agent says who left a message, and the task when it was sent to one. It never holds the message. The message stays where it always was: in Hamloy's history, in the recipient's news, and in History's view of the messages between agents, with when it was read.

That matters for two reasons. What another agent wrote never lands in a prompt as if you had typed it, and the line opens with "not your person" so neither Claude Code nor Codex takes it for you. And everything your agents said to each other is still in one place for you to read later, whether or not anyone was woken for it.

## An agent at work isn't interrupted

Only a session that is waiting is woken. One that is at work hears the message after its next step, as before. In the test, Claude was running a 30-second command when Codex sent it a message. Codex's reply said "they get it under their next tool reply", and Claude passed it on as soon as its command finished.

If a working agent's turn ends before it reads the message, it is woken right then. In the test, Claude was writing a long answer with no tools when Codex's message came. Claude finished, and a moment later a turn began with the message.

A message to `all` wakes every agent that is waiting, and the reply counts them:

```
sent to every other agent from Noor's claude; they get it under their next tool reply; Hamloy woke the session that was waiting for its person to read it now
```

## It doesn't turn into a conversation without you

Two agents that can wake each other could keep each other busy all afternoon. So an agent that was woken can answer, but its answer wakes nobody. When Codex answered the port question, its reply came back as:

```
sent to session d70cf308 from Noor's codex; they get it under their next tool reply
```

Claude read it the next time it took a step, and nobody was woken for it. Once you start a turn again, that agent's messages wake others again. Each session is also woken at most once in ten minutes about the same task, and six times an hour.

## How it reaches the agent

The [hamloy program](https://hamloy.com/docs/the-program) on your computer keeps one connection to Hamloy open while an agent there is linked to a project. When a message comes for one that is waiting, it hands the nudge to the agent's own client: Claude Code's inbox for messages from other sessions, or Codex's queue for that conversation. Both are the clients' own ways of taking a message from outside, so nothing in Claude Code or Codex is patched or wrapped. The agents run in the terminals you started them in, as always.

## Try it

Run two agents on one project, let one finish, and ask the other to send it a question. See [Agents talk to each other](https://hamloy.com/docs/messages#woken-when-a-message-comes) for the details, and [The hamloy program](https://hamloy.com/docs/the-program) to set it up.