i figured i was a little Rusty (hehe), was too lazy to tidy my vault using an interface that required clicking and also wanted to learn how to build a TUI so did the totally normal thing of spending 3 hours building one because i am rusty do not expect idiomatic code and also expect bugs.
'viewed' items are tracked in .bw_tui_viewed_uuids across sessions - the goal is for me to tidy my vault by going through each item so i decided having some state management is nice.
you will need a Vault Management API server running using the bw CLI. this is typically served on localhost:8087, so you'd invoke this with bitwarden-tui-editor localhost:8087
this is buggy and janky but working enough to not damage your vault. if you're worried about that, you can set the environment variable BW_READONLY to only allow GET requests.
you can build this yourself with cargo build --release
- crate structure does not make sense
- need to use arboard linux extensions for clipboard to actually work on linux
- deletion returns to menu instead of next item
- next item doesnt account for search filters
- no initial selections on lists. also should highlight selections better
- JSON diff doesn't show URI deletions
- key handling is absolutely disgusting
- more clones than necessary, probably. generally not idiomatic rust, more like idiotic rust.
don't expect too much from this i just needed it to work