SPECTERAUDITAGENT EVIDENCE / LOCAL INVESTIGATOR BROWSER-ONLY · NO UPLOAD
PRIVATE ANALYSIS / THE FIFTH DOOR

Bring your agent's alibi into the light.

Drop a Kiro CLI messages.jsonl session into Specter. We trace the actual test tool receipts, agent assertions and subsequent source edits. Your file stays in this browser tab.

01. READ LOCAL FILE02. RECONSTRUCT TIMELINE03. VERIFY EVIDENCE FRESHNESS
01 / EVIDENCE INTAKELOCAL ONLY

Your case, not a preset.

Select a Kiro CLI session file. We never transmit or save it, and only show bounded facts extracted from the tool log.

Up to 8 MiB · local Kiro CLI JSONL · no credentials needed
Where do I find a Kiro messages.jsonl file?

Use your file manager to locate a saved Kiro CLI session's messages.jsonl on this computer. Specter does not scan folders or choose a session for you.

Start with the three synthetic cases if you do not have a saved session. Use a private browser environment when inspecting sensitive logs; do not include raw sessions in public recordings.

No local file selected

Three synthetic cases. Each runs through the same local evidence parser as an imported Kiro session. None is a real test attestation.

Trust boundary. The analysis uses in-browser JavaScript and does not submit your file to Specter servers. Raw prompts, commands and private paths are never rendered. Logs are editable and unsigned; no result proves code correctness.
02 / THE SPECTER'S FINDINGAWAITING EVIDENCE

The investigation report

No evidence inspected yet

Your local source file never leaves this page. You can try a synthetic example first.