DX-2929: add DeepSeek Harness session-persistence backend on Upstash Redis - #20
Draft
CahidArda wants to merge 1 commit into
Draft
DX-2929: add DeepSeek Harness session-persistence backend on Upstash Redis#20CahidArda wants to merge 1 commit into
CahidArda wants to merge 1 commit into
Conversation
…pstash Redis Adds @upstash/agentkit-deepseek, a durable session-persistence provider for the DeepSeek Harness (ctx.sessionPersistence) — a drop-in replacement for the shipped JSONL and SQLite backends, which write to local disk and so cannot persist or resume sessions in a serverless or multi-replica deployment. Like the first-party backends it composes the harness's PersistenceCoordinator and implements only the PersistenceBackend storage hooks, and it passes the harness's own backend-agnostic conformance suite against real Upstash Redis. Sessions are stored as a Redis list indexed by event seq, which makes the backend seek-capable (readFrom reads only the requested suffix). Appends and repairs each run as a single Lua script, giving the atomic materialize-plus-first-batch the seam requires and enforcing contiguous seq in storage. Credentials resolve through ctx.credentials before falling back to Redis.fromEnv(), so the managed .credentials.yaml store works — it is never materialized into process.env. Config names the reference, never the value. An agentkit-deepseek command writes that store through the harness's own provider.
CahidArda
marked this pull request as draft
August 14, 2026 16:04
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds @upstash/agentkit-deepseek, a durable session-persistence provider for the DeepSeek Harness (ctx.sessionPersistence) — a drop-in replacement for the shipped JSONL and SQLite backends, which write to local disk and so cannot persist or resume sessions in a serverless or multi-replica deployment.
Like the first-party backends it composes the harness's PersistenceCoordinator and implements only the PersistenceBackend storage hooks, and it passes the harness's own backend-agnostic conformance suite against real Upstash Redis.
Sessions are stored as a Redis list indexed by event seq, which makes the backend seek-capable (readFrom reads only the requested suffix). Appends and repairs each run as a single Lua script, giving the atomic materialize-plus-first-batch the seam requires and enforcing contiguous seq in storage.
Credentials resolve through ctx.credentials before falling back to Redis.fromEnv(), so the managed .credentials.yaml store works — it is never materialized into process.env. Config names the reference, never the value. An agentkit-deepseek command writes that store through the harness's own provider.