Inside Turborg Storage: Your Bot's Memory
Hi, it's Christina 👋 Some skills and turboflows need to remember things between messages - quiz scores, karma points, who you've already greeted, a running poll tally. Your turborg keeps all of that in Storage, and you can see and manage it any time.
What Storage is
Storage is a simple key/value store that lives with your turborg. Whenever a flow or skill runs setvar, getvar or incr, it reads and writes here. The values survive restarts, so your quiz leaderboard (or anything else) is never lost.
Open it from any turborg via Storage.
How to read it
Entries are grouped by namespace - the name of the skill or flow that owns them. In the screenshot above you can see:
- an ai-quiz namespace holding the current question plus each player's score (
quiz-score-alice = 7,quiz-score-bob = 4, …); - a karma-counter namespace with each person's karma total.
For every entry you see its key, its value, its size, and - if it has one - an expiry (otherwise "Never"). The header shows a running total (e.g. 140 B · 10 keys), and there's a Refresh button.
How to manage it
Storage is read-and-clear - you look, and you can delete, but you don't hand-edit values here (the automations own those).
- Delete one key - the trash icon on a row. Handy for resetting a single person's score.
- Clear all on a namespace - wipes everything that automation has stored (e.g. reset the entire quiz leaderboard).
Deletes take effect immediately - the bot simply won't find the value on its next lookup, no restart needed.
How automations use it
If you build a turboflow, three steps talk to Storage:
- Set a variable (
setvar) - save a value under a key, e.g.points-{user}. - Get a variable (
getvar) - read it back into the flow. - Increment a counter (
incr) - add to a number. Perfect for karma, points and scores.
Namespaces are isolated. Each flow (or skill) gets its own private namespace named after it, so two automations can never clobber each other's data. That's why a multi-part game - like the AI Quiz - is built as one flow: so all its steps share the same scoreboard.
Good to know
- Keys can expire. A flow can set a time-to-live, so temporary values (a running poll, a cooldown) clean themselves up.
- No quota to worry about today - the size totals are just there so you can see what's stored.
- Account-wide, your dashboard shows a "Storage: N KB across M turborgs" summary so you can keep an eye on everything at once.
That's Storage - the memory behind your turborg's smartest tricks.
Ready to try it yourself? Create your free turborg → - no card needed.