Skip to content

feature (gated): loopback token-authenticated read-only secret API on the sink #54

Description

@solomonneas

What

A sink serve subcommand exposing synced secrets over a loopback-only, per-invocation-token-authenticated, read-only HTTP API for on-demand agent retrieval. Pattern from Bitwarden CLI bw serve (https://bitwarden.com/help/bitwarden-apis).

Why

Convenient for agent scripts, but it opens a new secret-retrieval surface on the sink, and there is a hard operator lesson on file about unprotected local endpoints being discovered and abused by an agent. If accepted, mandate: loopback bind, token auth, read-only, deny-wins enforcement, and a docs/threat-model.md entry before implementation. Prefer the ephemeral env-injection issue first; it reduces exposure instead of adding a listening socket.

Effort

L

Source: three-lane research sweep (repo audit + comparables + literature), independently reviewed before filing; run 20260724-040709-e9fc6818.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requestsize/LLarge: multi-day or gated

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions