floot/endo
1
0
Fork 0
Code Issues 12 Pull requests 1 Projects Releases Packages Wiki Activity Actions 5

Background task completion records are lost across a daemon restart #23

New issue
Open
opened 2026-08-28 17:09:53 +09:00 by floot · 0 comments
floot commented 2026-08-28 17:09:53 +09:00
Owner
Copy link

Twice in session mt82q1ns-l8nrge, a task notification arrived saying:

No completion record was found for this background shell command from the
previous session. It may have been stopped (via the UI, Monitor timeout, or
agent teardown — these leave no transcript marker), or it may have been
running when the previous Claude Code session ended.

Both followed an apply that restarted the daemon. The operator had to ask
"is the task still running?" and the agent had no way to answer.

Since applying a change is the normal way this machine gets updated, and
applying always restarts the daemon, any long-running background command is
expected to end in an unresolvable state.

Wanted: persist background task state across daemon restarts, or reap and
report them deterministically at teardown so the follow-up notification says
what actually happened.

Twice in session `mt82q1ns-l8nrge`, a task notification arrived saying: ``` No completion record was found for this background shell command from the previous session. It may have been stopped (via the UI, Monitor timeout, or agent teardown — these leave no transcript marker), or it may have been running when the previous Claude Code session ended. ``` Both followed an apply that restarted the daemon. The operator had to ask "is the task still running?" and the agent had no way to answer. Since applying a change is the normal way this machine gets updated, and applying always restarts the daemon, any long-running background command is expected to end in an unresolvable state. **Wanted:** persist background task state across daemon restarts, or reap and report them deterministically at teardown so the follow-up notification says what actually happened.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
llm
codex/ironhorse-workflow-recovery
fae/ironhorse-phase4-muy3ne05-ksg3ow-1
codex/claude-provisioning-fixes
pre-rebase/4e2644c37
codex/tokyo-network-20260910
codex/tokyo-pr1248-deploy-20260910
codex/tokyo-llm-20260909
codex/tokyo-pr-1224
codex/tokyo-upstream-20260908
agent
feat/hosted-endo-management
feature/secret-ingestion
deploy/endo-tokyo
chat-header-bar
pre-rebase/f722336893
pre-rebase/8ea79151a
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
floot/endo#23
No description provided.