Managing CodeBot Data
You can review and delete the data CodeBot codebot stores via the "Manage CodeBot Data" menu item, which may be in the application menu or the CodeBiot menu, depeding on app and platform.
Some CodeBot data is specific to the workspace or solution, while some data (such as global memories or approvals) is stored gobally and applies across workspaces and solutions.
The Manage CodeBot data sheet will present this infortmartion dspread axcros siz tabs:
CodeBot-related data can include:
- Approvals
- Memories
- Schedules
- Skills
- MCPs
- State & Usage
Approvals
As you work with CodeBot, certain actions (such as modifying a file, or running an external command) will require your Approval, which oyu can decide to grant once, for the current session, or indefinitely.
Indefinite approvals will be stored locally (for the app or for the workflow/solution, depending on context) and will persist after the app restarts, so you don't have to approve the same action or type of action again and again, every time.
On the Approvals tab, yu can see a list of all not-one-time approvals you granted before, and you can revoke individual or all approvals, if you change your mind. If an approval is removed, CodeBot will ask again next time it perfect that action.
Memories
Schedules
Skills
MCP
The Model Context Protocol (or MCP) is an open standard that allows you to connect existing services to CodeBot to talk to. For example, you could allow CodeBot access to you Notion workspace, Canva, or a third party database ot tool, via MCP.
On this tab, you can see all MCPs you have configured, and their status. Yoiu can also add, edit or remove them.
Configured MCP servers apear to CodeBot as additional Tools it can call.
State & Usage
Finally, as part of regular operation, CodeBot collects and caches local data. This includes
- A local usage ledger that lets you keep track of cost and requests
- The state of the agent runtime and chat history, so that when you quit the app and restart it, you can continue your conversation where you left of
- A transcript of the chat, so you scroll back and see what you and CodeBot talked about, even after the app is restarted.
On the "State & Usage" tab, you can
- launch the usage view (also available from the main menu via "Show AI Usage"
- open the local folder(s) that store this data
- delete this data
Note: what is stored and where depends on the application.
CodeBot in Fire/Water/Earth stores state and caches for each solution in a CodeBot/Caches folder in your platforms Application Data folder, and usage data under Elements/Usage in that same location.
Campfire stores state and caches in a hidden .campfire subfolder of each workspace, and stores usage data globally (but oper workspace) in your platforms Application Data folder.
GitBrowser stores only usage data, globally for the app, in your platforms Application Data folder. Because it offers no chat, it has no need to store agent runtime state or transcripts.