Sessions and history
What a session is, where its history lives and what its status means.
A session is one conversation with the agent in one project.
Where the history is stored
- The full session (your prompts, the agent's replies and reasoning, every tool step and file change) is stored on your PC.
- BambooKit Cloud keeps a small index so your phone and this site can list sessions: title, status, project, model, agent, change counts, what the agent is doing right now, and times.
- When you open a session elsewhere, its history and chat are read live from your PC.
- After each finished turn, your PC also saves a compressed copy of the history to private cloud storage, kept 7 days after the last save. When the PC is offline, the phone and this site show that copy (marked Saved copy).
Statuses
| Status | Meaning |
|---|---|
| Working | The agent is running. The current action is shown, e.g. Running npm test, Editing src/app.ts, Waiting for approval |
| Retrying | The model provider failed and the agent is retrying |
| Error | The last run failed; the message explains why |
| Idle | Waiting for your next message |
You get a notification when a session finishes (Agent finished) or fails (Agent failed).
What the history contains
| Part | Content |
|---|---|
| Summary | Status, project, branch and the commit it started from, agent, model, duration (active work time), prompts, files changed, lines added and removed, tests passed and failed |
| Prompts | Everything you asked, with times |
| Timeline | Prompts, replies, file reads and edits, commands, test runs, searches, sub-agents, errors, in time order |
| Changes | Each changed file (added, modified, deleted, renamed) with every edit's diff |
| Tests | Test commands the agent ran (npm test, pytest, go test, cargo test and similar) with passed or failed by exit code |
Everything comes from what the agent recorded on your PC; nothing is estimated.
Before and After
For a changed file, Before and After show the whole file. After is the file as it is now on your PC. Before is rebuilt by undoing the session's own recorded edits; if that is not possible exactly (the file also changed outside the session), it is the version in the last Git commit, and labelled so. New files have no Before. Before and After are read live and need the PC online; they are never stored in the cloud.
Changes when change tracking is off
When the agent's own change tracking (snapshots) is off, BambooKit builds the change list from the agent's edits, so it still works.
Rewind
In Desktop, Undo and Redo in the command palette rewind or restore the last message. Rewinding returns the conversation (and, where the agent keeps snapshots, the files) to before that message.
Todos
When the agent plans its work it keeps a todo list. The session's Todos tab on the phone shows it live from the PC: each item as pending, in progress or done, updating as the agent works.
Full file changes
The Changes tab lists every changed file (added, modified, deleted, renamed) with lines added and removed. Open a file for its full Diff (each recorded edit, in order), and its whole Before and After.
From the phone and the web
| Action | Phone | Web |
|---|---|---|
| Stop a running agent | Yes | No |
| Answer approvals and questions | Yes | Yes |
| Continue on PC, then chat and choose the model | Yes | Continue on PC only |
| Rename a session | Yes | Yes |
| Like (★) a session | Yes | Yes, with a Liked filter |
Messages need the session to be continued on the PC first: press Continue on PC once and the PC opens the session in BambooKit. Each message uses the model you pick in the model picker (the PC's configured providers and models). A rename is carried out by the PC, which owns the title; likes are kept by BambooKit only and never sent to the PC.
Deleting
Delete a session in Desktop; it disappears from the phone and this site. Its saved copy is removed within 7 days.