Answer the 429 question without interrupting anyone
One key, its TTL and the rate-limit counter behind a customer’s 429s, read in seconds and posted back in the thread the question came from.
Redis holds the session tokens, or the rate-limit counters, or the cached response that keeps the pricing page under 200ms. It is also the one datastore in most stacks with no migration history and no point-in-time restore worth planning around.
The useful half is small, specific reads: the key that should have a TTL and does not, the counter that stopped at 03:12, the rate-limit key that explains one customer’s 429s. A companion pulls those through an account you connect and answers in the thread instead of asking for somebody else’s time.
| redis-cli or the console | A Strawberry companion | |
|---|---|---|
| Checking one key and its TTL | Seconds, if you have access | Seconds, without interrupting anyone |
| Tracing a 429 back to a rate-limit key | You correlate by hand | Reads the key and the support thread together |
| Flushing a database | One short command | Available only if you left that action switched on |
| Keeping a flush off the table entirely | Remember not to type it | Switched off, once |
What should you switch off before the first prompt?
Open the Upstash Redis entry under `strawberry://settings/integrations` and read the Available tools list, which names every tool the app exposes and marks the read-only ones. Then use the Permissions block to switch off anything that deletes, expires or flushes.
In Redis, "clear the cache" is a reasonable thing to ask for and a costly thing to get slightly wrong, because the same instance often holds the cache and the thing that is not a cache. Sessions get evicted and everyone gets logged out.
What is Upstash Redis good for here?
Reading.
A key that should have a TTL and does not. A counter that stopped incrementing at 03:12. A rate-limit key for one customer id, which is the fastest answer to "why is this integration getting 429s".
Those lookups take a person out of flow, and they are exactly what to hand over. Pair the lookup with the signed-in tools where the question came from and the answer arrives in the thread. That is closer to support triage than to database work.
- Reads and TTL inspection: the useful half, and low risk.
- Anything that flushes, deletes or expires: switched off, revisited only for a named task.
- A separate Upstash database for cache and for anything durable, if you have not split them.
- Region matters for latency on a global database; the console shows which one the connection lands on.
What the connection handles
You connect Upstash once and see exactly what it can reach before you allow it.
Strawberry never receives the credential, the connection is scoped to one Strawberry profile, and disconnecting removes the managed account.
Intent is yours. An approval card tells you a call is about to happen; it does not know this instance also holds the sessions. That knowledge belongs in the per-action setting rather than in a moment of attention. The security page covers the credential side and is it safe to let AI use my browser covers the approval model.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents