Persist AI synthesis output to cache and support file output #78

Open
opened 2026-04-12 20:56:16 -06:00 by claude-code · 0 comments
Collaborator

The AI synthesis (brief + detailed + flags) is printed to the terminal and then discarded. For a tool whose entire purpose is producing investigation results, the output should not be ephemeral.

Two parts:

  1. Write synthesis to cache. Save synthesis.json (containing brief, detailed, and flags) to the investigation cache alongside plan.json and plan_evaluation.json. This makes the investigation results a permanent artifact that survives the terminal session and can be reviewed later.

  2. Support --output / -o for the full investigation report. The existing --json -o flag writes the base scan report. The AI synthesis should be included in that output (it currently may not be), and there should be a straightforward way to get the investigation results into a file.

This is the investigation tool's primary deliverable. It should be treated as a first-class artifact, not a side effect of running the command.

The AI synthesis (brief + detailed + flags) is printed to the terminal and then discarded. For a tool whose entire purpose is producing investigation results, the output should not be ephemeral. Two parts: 1. **Write synthesis to cache.** Save `synthesis.json` (containing brief, detailed, and flags) to the investigation cache alongside `plan.json` and `plan_evaluation.json`. This makes the investigation results a permanent artifact that survives the terminal session and can be reviewed later. 2. **Support `--output` / `-o` for the full investigation report.** The existing `--json -o` flag writes the base scan report. The AI synthesis should be included in that output (it currently may not be), and there should be a straightforward way to get the investigation results into a file. This is the investigation tool's primary deliverable. It should be treated as a first-class artifact, not a side effect of running the command.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: archeious/luminos#78
No description provided.