Summary

/status in chat surfaces the full terminalSummary of completed background tasks (cron jobs), flooding the status card with content that was already delivered to the user independently.

Version

OpenClaw 2026.3.31 (213a704)

Steps to Reproduce

1. Create an agentTurn cron job with sessionTarget: "isolated" and delivery.mode: "announce" (e.g. a daily briefing that produces ~500 words of output)
2. Let the cron run and deliver successfully
3. Send /status in Telegram (or any chat surface)

Expected

Clean status card showing session info, model, tokens, queue, etc. Completed background tasks that already delivered their output should not appear.

Actual

The entire terminalSummary of the last completed cron task is appended to the status card via the 📌 Tasks: line, producing a wall of text.

Root Cause

formatSessionTaskLine in commands-status-*.js (built from src/auto-reply/reply/commands-status.ts):

function formatSessionTaskLine(sessionKey) {
    const tasks = listTasksForSessionKey(sessionKey);
    if (tasks.length === 0) return;
    const latest = tasks[0];
    // ...
    const detail = latest.status === "running" || latest.status === "queued"
        ? latest.progressSummary?.trim()
        : latest.error?.trim() || latest.terminalSummary?.trim();
    // ...
}

The function lists ALL tasks associated with the session (via taskIdsByRelatedSessionKey), including completed isolated cron tasks. When the latest task is a finished cron job, it renders terminalSummary — the full task output — inline in the status card.

The causal chain:

1. Isolated cron tasks set their ownerKey to the main session (correct — the main agent owns the cron)
2. listTasksForSessionKey indexes by both ownerKey and childSessionKey, so completed cron tasks appear in the main session's task list
3. formatSessionTaskLine picks the latest task regardless of status or runtime type
4. For non-running tasks, it falls through to terminalSummary with no filtering or length limit

Suggested Fix

The status card task line should only display active (queued/running) tasks. Completed tasks have already delivered their output via their configured delivery mechanism — the status card should show operational status, not replay deliverables.

function formatSessionTaskLine(sessionKey) {
    const allTasks = listTasksForSessionKey(sessionKey);
    if (allTasks.length === 0) return;
    const activeTasks = allTasks.filter((task) => task.status === "queued" || task.status === "running");
    if (activeTasks.length === 0) return;
    const latest = activeTasks[0];
    const headline = `${activeTasks.length} active`;
    const title = latest.label?.trim() || latest.task.trim();
    const detail = latest.progressSummary?.trim();
    const parts = [headline, latest.runtime, title, detail].filter(Boolean);
    return parts.length ? `📌 Tasks: ${parts.join(" · ")}` : void 0;
}

Alternative: if showing completed task count is desirable, add a summary count without rendering terminalSummary (e.g. 📌 Tasks: 0 active · 2 completed).