Buffaly session anatomy
Understand what a Buffaly session contains, why it is durable, and how to inspect the work that happened inside it.
What a session stores
A session is more than a chat transcript. It is the working container for messages, tool calls, artifacts, plan state, scratch notes, local task files, validation evidence, and the handoff details Buffaly needs to resume long work.
When Buffaly resumes work, it uses this durable session context plus ontology memory and available tools to continue from the current route instead of starting over.
- Messages explain what the user asked and how Buffaly responded.
- Tool calls and outputs show the evidence Buffaly used, such as builds, searches, audits, and service responses.
- Artifacts and task files preserve durable work products that should outlive one chat turn.
Timeline, Plan, Scratch, and Tasks
The timeline is the visible history of the session: user requests, assistant messages, progress updates, and tool activity. For long tasks, it helps reviewers understand what happened and why without inspecting raw files first.
How users inspect it
Use the session UI to review the timeline, open generated artifacts, inspect tool output, and confirm whether a task is complete, still in progress, or blocked by a real decision.
A useful request is: ask Buffaly to summarize the session state, name the current plan, list the durable artifacts, and identify the next safe action before continuing long work.
For long work, look for the plan, scratch notes, committed changes, durable task updates, and explicit validation output. Those are stronger evidence than a final message alone.
Good user requests
- "Show me the current plan."
- "Summarize the scratch notes."
- "List the artifacts created in this session and how to verify them."
- "Continue from the last pending task."
- "Create a durable task artifact with acceptance criteria."
Good habits
Ask Buffaly to keep durable task state for multi-step work, to cite validation evidence before declaring completion, and to preserve artifact paths that you may need later.
If a session becomes very long, compaction should preserve decisions and next steps, while task files and artifacts preserve durable detail that should not be lost when the visible conversation is summarized.