@seekrit/proxy

An npx-able launcher for seekrit-proxy, seekrit's egress proxy for untrusted workloads: the workload sends {{seekrit:NAME}} placeholders, the proxy swaps in the real decrypted value on the way to an allowlisted upstream. The agent never holds the key.

SEEKRIT_TOKEN=skt_… npx -y @seekrit/proxy --config seekrit-proxy.toml

The proxy itself is a Rust binary. This package downloads the released build for your platform, verifies its SHA-256 against the checksum published beside it, and runs it with the arguments you passed. It interprets no flags of its own — --help shows the proxy's help — and adds no defaults.

Don't have a config yet?

The seekrit CLI generates one, and can run the proxy in one step without writing a file:

npx -y @seekrit/cli proxy run --preset openai      # nothing written
npx -y @seekrit/cli proxy init --preset openai     # a reviewable seekrit-proxy.toml
npx -y @seekrit/cli proxy init --agent nova        # from published policy

Environment

| Variable | Default | Purpose | | --- | --- | --- | | SEEKRIT_TOKEN | — | Service token the proxy resolves with. Required — it fails closed without one. | | SEEKRIT_PROXY_BIN | — | Path to a binary you already have. Skips the download entirely. | | SEEKRIT_PROXY_VERSION | this package's version | Binary version to fetch. | | SEEKRIT_PROXY_BASE_URL | https://proxy.seekrit.dev | Where artifacts are fetched from. |

Downloads are cached under $XDG_CACHE_HOME/seekrit/proxy (or ~/.cache/seekrit/proxy), keyed by version and target, so the fetch happens once per version.

The package version tracks the binary version it fetches, so npx @seekrit/[email protected] runs proxy 0.7.0.

Other ways to install

• A binary on your PATH — curl -fsSL https://proxy.seekrit.dev/install.sh | sh
• A container — docker run seekritdev/proxy (multi-arch, static musl on scratch)
• From source — cargo build --release in apps/proxy

Security

SEEKRIT_TOKEN must not be readable by the workload the proxy exists to constrain: anything that can read it can call /v1/resolve itself and skip the proxy. Run the proxy as a separate OS user, or in its own container. See the guide's honest limits for the full discussion.