Duva · Reply help

Can I still reply?

Here's what the status colors mean — and how to make sure your reply reaches Claude even after a session has moved on.

What the colors mean

Waiting

An agent polled in the last few seconds and is online right now. Your reply is delivered instantly.

Session ended

No agent has polled recently — that session has moved on. Your reply is still saved on the server; resume on your desktop to deliver it.

Not yet seen

The question was posted, but no agent has polled for it yet. Your reply is saved and waits for the first agent that reads it.

Either way, your reply always saves. The reply endpoint is idempotent — it's delivered whenever an agent session reads the message: instantly if one is live, or later when a new session picks it up.

If the session ended — how to deliver your reply

On your desktop (Claude Code)

Your reply is already saved server-side, so nothing is lost. To pick it up:

Open a terminal in the same project where the question came from.
Run claude. The agent can read your saved reply from the message history and continue from there.
If a workflow was polling via the pidgin/pidgin skill, simply re-running that question's poll will pick up the saved reply.

ChatGPT or Codex

Those clients are not wired into Duva's reply relay. To use your reply there, copy it into a new ChatGPT or Codex session manually. There is no automatic hand-off to those tools.

⚠️ No remote dispatch. Replying from your phone does not spin up a new Claude, ChatGPT, or Codex session. It saves your answer — a session you start reads it.

Why does this happen?

Agent sessions are ephemeral. When Claude sends a question, it polls for your reply every 5 seconds for up to about 5 minutes, then stops. After that the session has moved on — so a fresh session has to read your reply to continue. That's why "Session ended" doesn't mean your reply is lost: it just means a new session, not the original one, will deliver it.