The wrkr CLI

Cache — wrkr cache

Replaces Upstash.

Redis is already running on your machine. wrkr cache prints a ready connection URL. It's a full Redis over a normal long-lived connection — not a hosted REST subset, no signup.

wrkr cache
# → prints a ready-to-use Redis connection URL

When to reach for it

Caching, sessions, rate limiting, pub/sub, and short-lived (ephemeral) queues. Because it's plain Redis over the connection URL, everything Redis does is available: TTL expiry, pub/sub, Lua scripts, transactions.

Command reference

You'll usually just ask your agent; these are the exact commands it runs (and you can too).

wrkr cache [--json]

Full flags and examples: wrkr cache --help.

What you get

  • Full Redis over a normal connection — not a REST/edge subset. Use any Redis client for your language.
  • TTL, pub/sub, Lua, transactions — the real feature set, not a hosted slice of it.

Limits

  • Memory is bounded, with LRU eviction — it's a cache, so old keys are evicted under pressure. Don't store anything you can't afford to lose here.
  • For durable queues and anything that must survive eviction or a restart, use the database, not the cache.