Skip to content

RedDB navigation

Blog · Category

Agents

13 posts in this category.

  1. Jun 2026 Agents · · 4 min Cross-session task queues — AFK agents with durable resume An AFK agent's to-do list is the worst place to keep ephemeral state. Move it to a RedDB queue with checkpoints, idempotency keys, and a watchdog and a Stop becomes a pause, a crash becomes a retry, and a machine swap becomes a noop.
  2. Agents · · 4 min Eval datasets in RedDB — from ad-hoc prompts to versioned regression sets Most teams evaluate agents with a notebook full of one-off prompts that nobody re-runs. Capture every interesting turn into a RedDB table, tag it, version it, and your eval becomes a query that any model upgrade can be diffed against in seconds.
  3. Agents · · 4 min Sub-agent dispatch via database queue — durable parallelism across sessions Claude Code's Task tool spawns sub-agents that die with the session. Push the work into a RedDB queue instead and workers on any machine pick it up, write results back, and the parent subscribes to completions via LISTEN/NOTIFY. Fire-and-forget becomes durable fan-out.
  4. Agents · · 5 min Context window economics — when memory beats reloading docs Every CLI agent burns tokens re-reading the same files turn after turn. Put a number on the waste, work out the breakeven against a semantic-memory layer in RedDB, and show the SQL plus hook that flips the math for projects past a few thousand lines.
  5. May 2026 Agents · · 4 min Multi-agent shared memory — five agents, one knowledge graph When parallel sub-agents work on related slices of the same problem, they need a shared scratchpad with conflict resolution. A snapshot-read, first-committer-wins write pattern over RedDB gives each agent isolation while still surfacing contradictions as alerts on the orchestrator side.
  6. Agents · · 4 min Agent observability — traces, tokens, and costs in RedDB Most Claude Code setups can't answer "what did the agent cost me last sprint?" or "which tools dominate p99 latency?". A PostToolUse hook that writes every tool call, token count, and cost into RedDB turns those questions into one-line SQL.
  7. Agents · · 4 min An MCP server for RedDB — one database, every agent CLI The Model Context Protocol lets every modern agent CLI — Claude Code, Codex, Cursor, Gemini CLI — share the same toolbelt. Wrap RedDB once and you give all of them agent memory, document storage, and semantic search through a single endpoint. Manifest, server, wiring.
  8. Agents · · 5 min Building a "remember this" skill end-to-end A 30-minute walkthrough — turn a Claude Code skill into a durable note-taker. The skill captures the current conversation slice, embeds it, writes it to RedDB, and surfaces it on the next SessionStart. Every file you need, in order.
  9. Agents · · 5 min Slash commands with memory — commands that learn between sessions A Claude Code slash command is a markdown file with a shell expansion. Wire that shell call to RedDB and the command stops being a stateless macro — /remember, /forget, /recall become a tiny CRUD app the agent uses for itself.
  10. Agents · · 5 min Hooks that mutate state — making Claude Code hooks transactional with RedDB A PostToolUse audit-log hook looks trivial until the agent crashes mid-turn, the network blips, or Slack 503s. Wrap the side effects in a RedDB transaction with idempotency keys and a saga for the external call, and the hook stays honest.
  11. Agents · · 4 min Skills as data — storing metadata, runs, and learned refinements in RedDB Claude Code skills are static SKILL.md files today. Promote them to first-class data — metadata, execution traces, success rates — and the agent can pick the right skill for a new task with a SQL query instead of a keyword-match heuristic.
  12. Agents · · 8 min Agent SDK on RedDB: building custom agents with native persistence A walk through the four surfaces of a small Agent SDK — tool registry, memory adapter, conversation log, eval hooks — backed by RedDB instead of a stack of services. Ends with a working code-review bot in under 300 lines that remembers what it has reviewed, per repository.
  13. Agents · · 4 min RedDB as Claude Code's memory backend — beyond CLAUDE.md Swap the static MEMORY.md file for a queryable, embeddable memory layer. A SessionStart hook reads top-K memories into context, a /remember slash command writes them, and RedDB stores rows, vectors, and audit log in one transaction.

Get the next dispatch.

New essays on multi-model storage, RAG, agents, security. No spam.

No spam. Unsubscribe anytime.

RedDB Cloud

Join the private beta.

One-click managed deploy. Free during beta. Founding pricing locked at GA.