ce-sessions

You can query coding agent session history by asking questions about past work, attempts, and investigations. The system interprets prior sessions to locate and summarize decisions, work completed, and next steps across multiple projects and runs.

Tracing previous debugging attempts is done by querying your coding agent session history. This allows you to understand how problems were investigated and what was tried, accelerating debugging and learning by referencing prior investigations across runs.

Yes, you can locate and summarize past session work, decisions, and next steps. By applying questions about past sessions and prior attempts to the system, you retrieve context on what was investigated across different projects and runs.

You ask questions about what a coding agent worked on by providing your query along with runtime context. The system includes your working directory, repo name, and git branch to accurately query and interpret the relevant session history.

You need to query session history when users reference prior sessions or past investigations, or when you need to understand what was tried across sessions. It is essential for tracing previous attempts to accelerate debugging and learning.