Files
evil_MoE/.claude/memory/feedback_no_nohup_with_pueue.md
T
wassname 9c188f60be memory: track agent memory in repo .claude/memory (symlinked from harness path)
Move per-project agent memory into the repo so it is version-controlled.
Harness path /root/.claude/projects/.../memory now symlinks here, so
auto-load still works while the files live under git. Un-ignore only
.claude/memory/ (worktrees, locks, local settings stay ignored).

Co-Authored-By: Claudypoo <288921227+claudypoo@users.noreply.github.com>
2026-06-03 11:08:25 +00:00

1.0 KiB

name, description, metadata
name description metadata
feedback-no-nohup-with-pueue Don't wrap pueue follow/wait in `nohup ... &`; run the client directly as the background task.
node_type type originSessionId
memory feedback c06c2b0e-44ee-45a1-b213-4f77c006109c

When monitoring pueue jobs from a run_in_background bash task, run the client directly: pueue follow <id> | tail -N (or pueue wait <id>; pueue log <id>). Do NOT wrap it in nohup bash -c '... &'.

Why: pueue's daemon already owns the job; follow/wait are just clients streaming the daemon's log, so nohup buys nothing. Inside run_in_background (itself already a harness-tracked process), an extra nohup ... & spawns a child and the outer shell exits in ~0s, so the harness notifies on the wrapper exit while the real follow runs orphaned. Symptom: "completion notifications fire early / abort my sleeps."

How to apply: background command = the bare pueue client, no nohup, no &. The harness then tracks the client itself and wakes me on real finish/fail. Related: feedback-afk-autonomy.