Context

I hit two linked issues in --session --auto flows:

1. First CI would frequently exit immediately on a historical completion_result restored from a prior session, before the new prompt could run. So first invocation on a new session would work fine, but a follow up prompt the - prompt would never execute.
2. The follow-up --auto prompt could hang because the extension emits a resume_task / resume_completed_task ask after restore, but the CLI was sending the prompt as a new task instead of answering that ask.

This update fixes both: prevent early CI exit on historical completion, and ensure the prompt answers the resume ask so the session continues instead of stalling.

Implementation

CI exit guard (historical completion):

• Added a ciCompletionIgnoreBeforeTimestampAtom that represents “ignore completion_result at or before this timestamp.”
• When resuming a session, we set this timestamp from the last known chat message and clear the “resumed” flag once the prompt starts.
• useCIMode and the message handler now check this timestamp (plus the resume flag) to avoid exiting on historical completion_result.
• effects.ts mirrors the same check to avoid setting ciCompletionDetectedAtom from restored messages.
• Tests were updated to cover “skip historical completion” and “detect new completion after ignore timestamp.”

Resume ask handling (prevents hang):

• Implemented explicit resume-ask detection via isResumeAskMessage / shouldWaitForResumeAsk.
• In UI.tsx, when --auto is used after a session restore and a resume ask arrives, the prompt is sent using sendAskResponse (as a response to that ask) instead
  of creating a new task.
• Commands are only executed when we are not answering a resume ask.
• Attachments are handled consistently in both paths (resume response vs new task).
• Added focused tests for the resume-ask helper to keep the logic well-defined.

Screenshots

Before:

❯ kilocode --auto "whats 2+2?" --json > /tmp/invocation1.json

kilocode-backend/cloud-agent florian/chore/fix-parse-tool-metadata-from-ask* ≡19s
❯ kilocode --auto "whats 4+4?" --json --session=0eeb751e-8d9f-4853-993f-3bfee207dbea > /tmp/invocation2.json

that second invocation doesn't do anything

{"timestamp":1,"source":"cli","id":"msg-1768591300815-2","type":"welcome","content":"","metadata":{"welcomeOptions":{"clearScreen":false,"showInstructions":false,"instructions":[]}}}
{"timestamp":1768591230871,"source":"extension","type":"say","say":"text","content":"whats 2+2?"}
{"timestamp":1768591230897,"source":"extension","type":"say","say":"api_req_started","metadata":{"apiProtocol":"openai","tokensIn":11292,"tokensOut":95,"cacheWrites":0,"cacheReads":0,"cost":0.07294625,"usageMissing":false,"inferenceProvider":"Anthropic"}}
{"timestamp":1768591242685,"source":"extension","type":"say","say":"text","partial":false,"content":"2 + 2 = **4**\n\nThis is a simple arithmetic question that doesn't require any tools or planning. The sum of 2 and 2 equals 4."}
{"timestamp":1768591243925,"source":"extension","type":"say","say":"completion_result","partial":false,"content":"2 + 2 = **4**"}
{"timestamp":1768591244327,"source":"extension","type":"ask","ask":"completion_result"}
{"timestamp":1768591300858,"source":"extension","type":"ask","ask":"resume_completed_task"}
{"sessionId":"0eeb751e-8d9f-4853-993f-3bfee207dbea","updatedAt":1768591302852,"timestamp":1768591303823,"event":"session_synced"} 

How to Test

Get in Touch