Describe the bug
When running /pi-vcc-recall in a new session that has no prior conversation, the following error occurs:
The session JSONL file does not exist yet because Pi hasn't written any messages to disk in the new session.
To Reproduce
- Install pi-vcc:
pi install npm:@sting8k/pi-vcc
- Start a brand new Pi session:
pi
- Immediately run
/pi-vcc-recall <query> before any conversation
- Error appears
Expected behavior
/pi-vcc-recall should either:
- Search previous session JSONL files instead of only the current one, OR
- Show a friendly message like "No session history yet" instead of throwing ENOENT
Environment
- pi-vcc version: latest (npm:@sting8k/pi-vcc)
- Pi version: v0.70.2
- Running inside Docker container (root)
- Session folder:
/root/.pi/agent/sessions/--workspace--/
Additional context
The JSONL files from previous sessions DO exist and are confirmed via find /root/.pi -name "*.jsonl". The issue is that recall only looks at the current session file which hasn't been written yet in a fresh session.
Describe the bug
When running
/pi-vcc-recallin a new session that has no prior conversation, the following error occurs:The session JSONL file does not exist yet because Pi hasn't written any messages to disk in the new session.
To Reproduce
pi install npm:@sting8k/pi-vccpi/pi-vcc-recall <query>before any conversationExpected behavior
/pi-vcc-recallshould either:Environment
/root/.pi/agent/sessions/--workspace--/Additional context
The JSONL files from previous sessions DO exist and are confirmed via
find /root/.pi -name "*.jsonl". The issue is that recall only looks at the current session file which hasn't been written yet in a fresh session.