v0.3.0
vaulted-agent 0.3.0
New
va run -m MANIFEST [--backend NAME] -- cmd…– inject vault secrets into any command without a harness fileva doctor– check harnesses, backend CLIs, auth files, manifest syntax (no secret values)va secrets list|get|which|validate– Bitwarden SM helpers using the same auth as launchesva version/--version/-V- Named Bitwarden refs:
UUID,uuid:…,name:KEY,project:PROJECT/KEY - Manifest validation rejects placeholders (
REPLACE_…, all-zero UUIDs, …) before launch - Bitwarden setup explains SM access token vs vault password and can build a refs file from
bws secret list
Fixes
install.sh --backend …rewritesDEFAULT_BACKENDin the installed launcher- Install summary prints the correct token path (
bws.env/op.env/ …) - Clearer no-TTY / agent→agent auth errors when a token prompt is impossible
- Remote installer pin:
DEFAULT_VERSION=v0.3.0
Upgrade
curl -fsSL https://stephens.page/vaulted-agent/install.sh | bash
# or
VAULTED_AGENT_VERSION=v0.3.0 curl -fsSL https://stephens.page/vaulted-agent/install.sh | bashExisting harnesses and token files are kept.