PREFERRED way to use a secret. Runs a local command, resolving any stillvault://<path> references after a named human approves the release. The secret is injected into the child process and is NEVER returned to you or shown in this conversation — you get only the command's output. The call blocks until a human approves on their device (or times out). Examples: run psql with stillvault://db/prod/dsn as an argument, or curl an API with a key in a header. Prefer this over stillvault_reveal whenever you just need to use the secret rather than read its value.

Returns a secret's plaintext VALUE into this conversation after a named human approves the release. WARNING: this puts the secret in the model's context and therefore in your LLM provider's logs — it is the opposite of how Stillvault is meant to be used. Prefer stillvault_run, which uses the secret without revealing it. Use this only when the value itself must be read (e.g. to display it to the human who asked, or to write it into a file you are editing). The call blocks until a human approves on their device.