Problem

When prompts are processed on VMs, the outputs are not being stored because currentSessionId is null.

Logs

[WARN] [OUTPUT_STORE] No currentSessionId, skipping storage {"type":"text_delta"}
[WARN] [OUTPUT_STORE] No currentSessionId, skipping storage {"type":"completed"}

This happens even though:

1. The agent is processing prompts correctly
2. Claude is responding with valid content
3. The task completes successfully

Impact

• vm-outputs returns empty arrays even after successful prompt execution
• vm-status shows no conversation history
• Cannot retrieve results from orchestrated VMs

Expected Behavior

The session ID should be set when a prompt is dispatched, and all outputs should be stored and retrievable via vm-outputs.

Reproduction

1. Create a VM from golden image
2. Update to latest vers-agent binary
3. Dispatch a prompt via vm-run
4. Check logs - outputs complete but storage is skipped
5. Call vm-outputs - returns empty array

🤖 Generated with Claude Code