[FEATURE] Support configurable session backends (e.g., S3)

Resolved 💬 3 comments Opened Dec 4, 2025 by povils Closed Feb 6, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

Currently, sessions are stored only on the local filesystem. It would be useful to allow configurable session backends so that sessions can be saved and restored from alternative storage systems (for example, AWS S3). This would enable running the tool in distributed environments or containers where local filesystem persistence is not ideal.

Proposed Solution

Introduce a pluggable session backend system where the storage mechanism can be configured. For example:

Default remains local filesystem for backward compatibility.

Add support for S3 (and optionally other backends) by implementing an interface for save_session and load_session operations.

Allow users to configure the backend through a configuration file or environment variable.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

Configuration and settings

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗