Show HN: A Governed Context Vault for Claude Code and Cowork (AGPL CLI)

A Show HN submission introduced a governed context vault for Claude Code and Cowork, packaged as an AGPL CLI. The write-up is hosted at promptowl.ai under a resource titled around making Claude accountable via a ContextNest plugin. On Hacker News the thread sat at 1 point with 0 comments at the time of the listing, with the discussion entry at item id 49006270.

The product is framed as a context vault: a place to store, scope, and control the material that coding agents load into session context. Targeting Claude Code and Cowork points to a plugin or CLI bridge that sits beside those tools rather than replacing them. The AGPL license signals open source with strong copyleft on network use, so operators who run or extend the vault under that license face disclosure obligations if they distribute modified versions as a service.

For engineers and builders, the hard problem is not “more context” but accountable context: who may inject files, rules, and prior decisions into an agent session, and how those injections are audited when the agent writes code or changes infra. A governed vault is useful where teams already treat Claude Code or Cowork as part of the loop and need a single policy surface for what the model is allowed to see, rather than ad hoc CLAUDE.md files and manual paste.

In the broader market this sits next to other agent-memory and policy layers that try to make IDE and terminal agents safer for multi-user or multi-repo work. Claude Code and Cowork already own the interactive surface; a vault competes less as a chat product and more as a control plane for context provenance. Early Show HN traction was minimal (1 point, no comments), so adoption signal is still thin and will depend on whether teams can install the AGPL CLI without fighting their existing agent config.

Practical next steps: read the PromptOwl piece for install and governance model, then try the vault against one real Claude Code or Cowork workflow and check how it records or blocks context loads. Watch whether the AGPL CLI remains a local control tool or grows into a shared service, and whether the HN thread accumulates concrete install reports rather than silence.