Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Jarvis does not finish multi-deliverable tasks — drops remaining items mid-session [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#74658•Fetched 2026-04-30 06:21:39
View on GitHub
Comments
1
Participants
2
Timeline
2
Reactions
2
Author
chrisgwynnechrisgwynne
Participants
chrisgwynnechrisgwynneclawsweeper[bot]clawsweeper[bot]
Timeline (top)
closed ×1commented ×1
RAW_BUFFERClick to expand / collapse

Steps to reproduce

  1. Give Jarvis a multi-step task with distinct deliverables
  2. Jarvis starts working, completes some items, then sends a status reply
  3. The session ends or Jarvis pivots to a new request before the remaining items are delivered

Expected behaviour

Jarvis completes all stated deliverables in a session before going quiet or pivoting.

Actual behaviour

Jarvis begins working through a list, completes the first few items, then sends a status message and stops — even when the remaining items don't require user input and are within scope.

Examples

Tonight (2026-04-29):

  • Said "open PRs for 4 Jarvis-2.0 issues" → completed (✅ PRs 15–18 created)
  • Said "open 3 PRs for Blueprint-2.0" → opened 1 of 3 (graceful shutdown done; as any type fixes and connector stubs filed as lower-priority issues instead of PRs)
  • Said "raise an issue on OpenClaw repo" → did not do it until prompted

Earlier sessions (2026-04):

  • Similar mid-session pivot patterns documented in memory corrections

Proposal

Before going quiet, Jarvis should complete a self-audit checklist:

  1. Did I say I'd do N things? → list them
  2. Which are actually done? → verify each has a concrete output (PR link, issue number, file path, sent message)
  3. Which are still open? → either finish them or explicitly hand off with a named owner and a commit to do it

If a task is genuinely blocked, say so clearly with the blocker. If it got deprioritised mid-session, say that too — don't silently drop it.

Additional context

This is a Jarvis execution quality issue, not an OpenClaw platform bug. The fix lives in Jarvis's own self-management, not in the OpenClaw codebase. Filing here as requested by Chris.

extent analysis

TL;DR

Implement a self-audit checklist in Jarvis to ensure completion of all stated deliverables before going quiet or pivoting.

Guidance

  • Review Jarvis's task management logic to identify why it stops working on tasks after sending a status message.
  • Implement the proposed self-audit checklist to verify task completion and handle blocked or deprioritized tasks.
  • Consider adding a mechanism for Jarvis to explicitly hand off incomplete tasks with a named owner and a commit to complete them.
  • Test the updated logic with various scenarios to ensure Jarvis completes all deliverables as expected.

Example

// Pseudo-code example of self-audit checklist
function selfAudit(tasks) {
  const completedTasks = [];
  const incompleteTasks = [];

  tasks.forEach(task => {
    if (isTaskComplete(task)) {
      completedTasks.push(task);
    } else {
      incompleteTasks.push(task);
    }
  });

  // Handle incomplete tasks
  incompleteTasks.forEach(task => {
    if (isTaskBlocked(task)) {
      // Say so clearly with the blocker
      console.log(`Task ${task} is blocked: ${getBlocker(task)}`);
    } else if (isTaskDeprioritized(task)) {
      // Say so clearly
      console.log(`Task ${task} was deprioritized`);
    } else {
      // Explicitly hand off with a named owner and a commit to do it
      assignTaskOwner(task);
    }
  });
}

Notes

The provided example is a simplified illustration and may need to be adapted to fit the actual implementation details of Jarvis's task management logic.

Recommendation

Apply the proposed self-audit checklist workaround to ensure Jarvis completes all stated deliverables before going quiet or pivoting, as it directly addresses the identified issue with Jarvis's task management logic.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#API routing#API middleware#SSR setup#ISR setup#authentication setup

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Jarvis does not finish multi-deliverable tasks — drops remaining items mid-session [1 comments, 2 participants]