1. Start with the clue
Operators can ask about a suspicious IP, account, command, Java service, web path, recent file, or broad alert summary. The AI turns that clue into scope, hypotheses, and a first evidence path.
Open Investigator · Local AI incident response
Open Investigator helps response teams start from a weak alert, suspicious IP, account, process, path, web root, Java service, or anomaly description, then collect host evidence through sealed tools and write evidence-backed case reports.
Search intent
Practical workflow
Operators can ask about a suspicious IP, account, command, Java service, web path, recent file, or broad alert summary. The AI turns that clue into scope, hypotheses, and a first evidence path.
Open Investigator records tool observations into evidence.jsonl and command audit logs so every AI-assisted step can be reviewed later.
The run produces Markdown and JSON reports with findings, timeline context, supporting evidence IDs, confidence, and human follow-up points.
Common searches
The source, usage examples, contribution notes, and issue tracker live in the public Open Investigator repository.