tancheng33/dsh-spill-s3

README excerpt

dsh-spill-s3 English 中文 An S3-compatible backend for the DeepSeek Harness spill storage seam ( ctx.spillStore ). Oversized tool output goes to object storage — AWS S3, MinIO, Cloudflare R2, or any S3-compatible server — instead of the disk of whichever machine happened to run the agent. Why When a tool result is too large for the model's context, the harness spills it: the full text is persisted and the model gets a locator plus retrieval guidance. The shipped backend, @deepseek-ai/dsh-spill-local , writes that text to a private directory on the local host. That is the right default, and the wrong deployment for a team: dsh-spill-local dsh-spill-s3 Where artifacts live a private dir on the agent's host your bucket A headless/containerized run artifacts die with the container artifacts outlive it Another engineer wants to look shell onto that host already has bucket access Encryption at rest / lifecycle / retention whatever the host does whatever your bucket policy says This plugin swaps the substrate , not the policy. It implements the one method the seam declares — saveText — and leaves retention ( @deepseek-ai/dsh-output-retention ) and tool-result replacement ( @deepseek-ai/dsh-…

Category