Delegate not showing in acp-fleet

[richardaubin]

I have a delegate running but is not showing in the fleet so I can't see what it's doing. Is this normal?

[ranxianglei]

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 Short answer: no — an async delegate dispatched from the same pi session should appear in /acp-fleet immediately (and in the small footer widget while running). If yours doesn't show, one of these three is almost certainly the cause:

1. It's running in a different pi process (most common). The fleet list is per-process in-memory state. This applies if you dispatched the delegate from another terminal/instance, or fully quit and restarted pi after dispatching. The child is deliberately detached and survives its parent exiting, so the work keeps going — but the new process has no way to know about it. Check ls $TMPDIR/acp-delegate/: every async run writes <runId>.out, <runId>.activity, <runId>.session.jsonl. Files whose runId isn't in your fleet are orphans from the previous process. To watch one live: tail -f $TMPDIR/acp-delegate/<runId>.activity. To stop one: kill its child process.

2. The run was sync. async:false runs (and one-shot modes like pi -p/json, which auto-downgrade async→sync) never register in the fleet at all — by design, since the result comes back inline in the same turn. During a sync run you'd see the pending acp_delegate tool call directly in the conversation instead.

3. It's queued behind a concurrency limit — only if you set delegate.maxConcurrent (default is unlimited): queued runs show in the /acp-fleet list as ○ queued, but not in the small footer widget. Note finished entries are capped at 12 in the list, so older ones scroll out.

Quick self-check: look at the tool result the model got when dispatching. If it said Delegated to … (runId …) + Running in the background → it was an async run and should have shown in that same pi process's fleet. That same result includes a live activity-file path — tailing it lets you watch the delegate work even outside the fleet.

If none of these fit (same process, default async, list still empty), that would be a real bug — tell me what /acp-fleet shows and paste the dispatch tool result and I'll dig in.

[richardaubin]

I think #2 applies. Will confirm if it happens again.

[ranxianglei]

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 Makes sense — sync runs (async:false) block the turn and return their result inline, so they're intentionally not tracked in the fleet list or footer widget. The full output still lands in a result file; the tool result tells you the path if you want to re-read it later.

If you ever need to watch a long task while doing other work, dispatch with async: true (the default) — then it shows up in /acp-fleet immediately and streams live activity to its <runId>.activity file.

Glad that explains it — I'll leave this open in case it recurs differently; feel free to close it if you're happy.