---
name: rbw-add-vaultwarden-422
description: "rbw 1.15.0 cannot create or edit entries against Vaultwarden 1.37 (HTTP 422, missing encryptedFor); reads still work"
metadata:
  node_type: memory
  type: project
  originSessionId: 08d4907d-b091-423a-8695-bd5ec699d8ca
  modified: 2026-11-04T23:14:31.174Z
---

As of 2026-11-04, `rbw add` fails with `api request returned error: 422` against
bw.rcjohnstone.com (Vaultwarden 1.37.5). The Vaultwarden log shows
`missing field encryptedFor`. Upstream: doy/rbw issue #385, unmerged PR #386.
`rbw get`, `list` and `sync` are unaffected.

**Why:** easy to misread as a bad command or a server fault, and nothing is written.

**How to apply:** check whether rbw has been updated past 1.15.0 before retrying.
With stdin that is not a terminal, `rbw add` reads the password from stdin and
ignores $EDITOR, so an agent shell with an open stdin hangs. Pipe the password in.