dsh-ci-context

When running a DeepSeek Harness agent inside a CI pipeline, the agent rarely knows which workflow, job, or commit it is executing on, forcing every turn to manually feed runtime coordinates through the prompt. dsh-ci-context solves this with a durable ambient context snapshot: on the first step of every turn it reads a fixed allowlist of non-secret variables from GitHub Actions, GitLab CI, or any CI=true environment, normalizes them, and injects a structured metadata block. Identical snapshots are never re-appended, and resumed sessions remain consistent.

The plugin is deliberately narrow. It never enumerates process.env, does not touch actor emails, commit messages, changed-file lists, credentials, or token-shaped variables. URLs must be HTTP(S) and are automatically stripped of query strings and fragments. It does not poll provider APIs, read logs or test results, or trigger pipelines. Its boundary is clear: hand the agent a business card about where it currently is, and nothing more.

Built for developers who run DeepSeek Harness automation in GitHub Actions, GitLab CI, or other CI=true environments and want the agent to natively perceive repository, workflow, job, and commit SHA without widening the variable surface area. It is a lightweight, auditable middle layer between the CI environment and the agent context window.