Bitwarden Custom field support

[ABrizmohun]

Fnox is so close to solving the secret management for me any my team; however, a lot of the values we need are in Bitwarden in custom fields.

The docs say: "Custom field extraction is not yet implemented. Use standard fields for now."

1. Is this something that is being worked on?
2. Are there any workarounds for now?

I would contribute to this if I knew Rust.

[jdx]

Thanks for raising this. The provider had partial plumbing for custom fields, but it returned the complete item JSON instead of extracting the requested value.

I opened PR #690 to implement custom fields for both backends:

• With bw, references such as My Item/API Key now extract the exact, case-sensitive field name from the item JSON.
• With rbw, fnox now uses the native --field option.

Until a release containing this lands, the direct CLI workarounds are:

bw get item "My Item" --session "$BW_SESSION" | jq -r --arg field "API Key" ".fields[] | select(.name == $field) | .value"
rbw get "My Item" --field "API Key"

If you are able to try the PR against your vault, feedback would be welcome.

AI-assisted — Tool: Codex; model: unavailable/unavailable; version: unavailable.

[ABrizmohun]

Thanks for the quick turnaround @jdx

I tested, and it works great.

One small issue is that it doesn't work if the field name contains a /, but I can work around that by renaming my fields.

[jdx]

@ABrizmohun Thanks for the report and screenshots. The reference parser was splitting on every /, so it rejected the value before invoking either Bitwarden backend.

I opened PR #693 to treat only the first slash as the item/field delimiter and preserve any remaining slashes in the exact custom field name. It includes coverage for both bw and rbw, plus a vault-backed regression test for an API/Key field.

If convenient, verification against your vault would be welcome.

AI-assisted — Tool: Codex; model: unavailable/GPT-5; version: unavailable.

[ABrizmohun]

Yep, field names with slashes work great now