[MODEL] Promised follow-up after an overnight background chain never ran (nothing wakes the idle session)

Open
#104,807 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript

Research direction

Start by tracing how Claude Code launches and monitors chained background runs, then check whether the session has any scheduled wake-up or task continuation mechanism. The issue describes the expected behavior but names no files or tests, so first locate those entry points and existing tests. Done means follow-up runs after the background chain completes, or Claude clearly explains that unattended follow-up cannot occur.

Written by the indexing model from the issue text.

Description

area:agents area:model bug platform:linux
Type of Behavior Issue

Other unexpected behavior

What You Asked Claude to Do

I authorised an overnight chain of long runs, started as systemd user units. Claude promised that when the chain finished, it would send the results to a checker subagent and push a summary for the morning.

What Claude Actually Did

The chain finished cleanly at 23:13. The promised follow-up never ran, because nothing woke the main session after the chain ended, and the session had been compacted in the meantime. The results sat idle until I came back the next morning. My reaction: "not clear to me why not continue the work overnight".

Expected Behavior

Follow-up steps should be wired into the chain itself (the last unit triggers the next step), or into a scheduled wake-up. If neither is possible, Claude should say clearly that the follow-up will not happen unattended. It should not promise steps that depend on the idle main session noticing the end.

Permission Mode

Not recorded.

Can You Reproduce This?

Haven't tried to reproduce

Steps to Reproduce
  1. Ask Claude to launch a long chained background run and to do agent-side follow-up when it ends.
  2. Leave the session idle until the run completes.
  3. Nothing happens until the user sends a new message.
Claude Model

Opus 5.5 (claude-opus-5-5), Claude Code 2.1.296, Linux x64

Impact

Low - Minor inconvenience (a night of unattended time lost)

Dominant language
TypeScript
Stars
154k
Forks
25.6k
Avg merge
12h 27m
Merged PRs (30d)
4

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from anthropics/claude-code

All issues in anthropics/claude-code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.