scratch-pad

You can track multi-step tasks by using a portable Markdown scratch pad to log tool usage, findings, and decisions. It provides structured CLI actions to append records, set checkpoints, and maintain a traceable history locally.

Logging tool usage during a research sprint is best handled by a Markdown memory file that records tool calls, findings, and checkpoints. You can use CLI commands to append entries, create todos, and generate summaries.

Organizing incident response notes requires a local Markdown file that captures checkpoints and decisions. By logging tool calls and progress within a single document, you ensure traceable task history across multiple tools.

A Markdown scratch pad is needed for complex workflows requiring five or more tool calls, analyzing multiple sources, or comparing items. It records the process for reference during the task and can be deleted after use.

Yes, you can use CLI commands including init, append, log-tool, finding, checkpoint, todo, summary, read, and complete to manage a task memory file. These actions structure logging and track progress within a single document.

Yes, the scratch pad always keeps data stored locally. It maintains a Markdown file that can be read to reference previous steps, ensuring your task memory and tool logging remain private and portable.