note

You can securely store pentest notes using a file-based storage system with concurrency-safe locking. This prevents write conflicts when multiple agents append findings, hypotheses, and results to a specific challenge code simultaneously.

Organize penetration testing findings by separating notes into three types: info, infer, and result. This structure limits each challenge to one file per note type, keeping markdown documentation structured and easily accessible.

Prevent file write conflicts by using file locks designed for concurrency-safe note storage. This ensures that when multiple agents append markdown notes to the same challenge file, no data is overwritten or lost.

Yes, you can retrieve a concise summary of existing pentest notes using dedicated read and summarize APIs. This allows security analysts to quickly access prior discoveries and adjust testing strategies for the next attempt.

No external dependencies are required to manage markdown files. The note storage system operates independently using a file-based architecture with built-in locking mechanisms to handle concurrent read and append operations.

A dedicated challenge note system provides structured markdown storage with specific note types and concurrency-safe file locking. This prevents data loss and enables quick summarization of findings that standard text files cannot guarantee.