session

To capture open-loop ideas during a coding session, you can park them in project-scoped memory. This prevents context loss by automatically creating memory files to track diverging thoughts for later recall.

Managing deferred questions during design reviews is best handled by parking items in per-project memory. This isolates context per project and uses a resolution log to audit when items are surfaced or closed.

To resume parked items from a previous agile standup, run the resume command. This surfaces up to 10 open items stored in project-scoped memory, allowing you to immediately recall previously deferred ideas.

Context management handles stale parked items by enforcing TTL rules. Items aged 14 days or more are marked as stale when surfaced, and items older than 30 days are automatically deleted from the memory files.

Yes, you can archive resolved questions during an interactive coding session by using the archive command with text input. This closes the parked item and logs the action in the central resolution log for audit purposes.

The limit for open items in a single session memory is 10. This cap ensures the memory surface remains manageable and prevents context overload when you run the summary or resume commands.