Feature Request: Cloud-Based Session Storage for Session Management

[tahitimoon]

I really like this library and am planning to use it in a production environment. However, the current session management only supports storing sessions on the local file system, which is not very convenient to manage. For building production-grade systems, cloud storage is essentially a requirement.

It would be great if session storage could be extended to support cloud storage backends such as S3 buckets. I recently noticed that Strands Agents already provides this capability, and I’m wondering whether the Claude Agent SDK has plans to add similar support.

Reference documentation:
https://strandsagents.com/latest/documentation/docs/user-guide/concepts/agents/session-management/

[cdnsteve]

What about local session management instead of dependency of a third-party like S3? Would that fit the need @tahitimoon ?

[tahitimoon]

What about local session management instead of dependency of a third-party like S3? Would that fit the need @tahitimoon ?

I think there might be a slight misunderstanding - the current implementation already supports local session management (file system storage), which works great for development and single-server deployments.

My feature request is specifically about adding cloud storage options for production environments where:

1. Horizontal scaling: When running multiple server instances behind a load balancer, sessions need to be accessible across all instances
2. Reliability: Cloud storage provides built-in redundancy and persistence that local file systems may not guarantee
3. Deployment flexibility: Many modern deployment platforms (containerized environments, serverless, etc.) have ephemeral file systems

So ideally, the SDK would support both approaches:

• Local file system (already exists) - perfect for development and simple deployments
• Cloud storage backends (S3, Azure Blob, GCS, etc.) - for distributed production systems

The goal isn't to replace local storage, but to provide additional options for different use cases. Think of it like how many database ORMs support both SQLite (local) and PostgreSQL/MySQL (remote) - different tools for different scenarios.

[oneryalcin]

Yeah I had to implement this myself, it works fine but had to run a custom GCS backend with checkpointing, as we needed to deploy to prod. Agreed would make it more useful if already one available.

[cdnsteve]

Ok I'm starting to work on a PR for this

[cdnsteve]

@tahitimoon mind checking the PR above (#466)
To get some feedback?
I wanted to keep it more focused around the primitive level so others could expand.

[tahitimoon]

@tahitimoon mind checking the PR above (#466) To get some feedback? I wanted to keep it more focused around the primitive level so others could expand.

Thanks a lot for sharing the PR! It’s just that their review process is really slow, and a lot of PRs still haven’t been approved.

[digi0pz]

We've recently started adopting the Claude Agents SDK and have been really impressed with it overall. That said, as we work toward scaling in production, the file-based session management approach is becoming a significant bottleneck.

We'd love to see support for database-backed session management as an alternative. Databases are generally the goto for production-grade session handling. They give us durability, concurrency, and the ability to run analytics on things like session history, tool call patterns, latency, and more.

Happy to contribute or provide more context on our use case if that would help move this forward. Thanks for the great work on the SDK!

[niceban]

I ran into the same problem. A lot of the pain here is not really prompt-related — it’s that Claude Code is being used like a short-lived command instead of a managed runtime.

I built a small project called claude-node that directly controls the local Claude CLI as a persistent subprocess, so an external Python app can explicitly start, send, resume, and stop sessions while keeping the native CLI behavior.

If what you want is a stable session/controller layer around Claude Code, this might be relevant:
https://github.com/claw-army/claude-node