Skip to main content
Files capture what you already know (manual uploads) and what you discover as you go (auto‑captured artifacts from AI runs) so every investigation, assessment, or campaign starts with the right context. Your stored files keep findings, evidence, and prior decisions at your fingertips. As you scan, probe, and document, outputs are saved and indexed automatically (logs, traces, PoCs, screenshots, reports) so you can:
  • Move from zero to context in minutes on new tasks
  • Reuse prior work to accelerate testing and triage
  • Maintain continuity across hand‑offs and long‑running projects
When you ask a question or kick off a task, the assistant pulls in the most relevant excerpts with citations, grounding answers in your own material. The more you work, the more valuable your stored files become, compounding efficiency across engagements.

​
What you can store

  • Past findings, confirmation steps, bypass techniques, and exploit variations to verify regressions
  • Findings and evidence: scan outputs, logs, screenshots, PoCs, write‑ups
  • Architecture and app docs: READMEs, API docs, diagrams (text extracts)
  • Ad‑hoc notes and exports: CSVs, Markdown, text files
Common formats: .md, .txt, .pdf (text extracted), .csv, .json, .log, source files, and more.

​
Ways to add files

  • Manual upload: drag‑and‑drop one file
  • Auto‑capture during AI runs: any files generated or fetched by tools are saved (e.g., httpx results, HTTP traces, generated reports)
  • Programmatic integrations: artifacts created by your pipelines show up automatically

​
How indexing works

  • Content is split into small, meaningful chunks for accurate retrieval
  • Metadata is attached automatically (source, filename, timestamps) for traceability
  • Hybrid retrieval (semantic + keyword) ensures relevant passages are found

​
How retrieval works

  • Implicit assist: while the AI plans or answers, it searches your stored files and injects the most relevant excerpts into the response with citations
  • Direct ask: say “search files for CVE-2024-xxxx confirmation steps” or “what bypass techniques do we have for DOM XSS in the admin portal?”
  • Tag and reuse: pin key docs so they are always considered for the current task
  • Citations: responses include links back to the exact passages used