Skip to content

Fix managed Bitwarden session status - #2

Merged
turinglabsorg merged 2 commits into
mainfrom
fix/managed-bitwarden-session-status
Sep 4, 2026
Merged

turinglabsorg merged 2 commits into
mainfrom
fix/managed-bitwarden-session-status

Conversation

@turinglabsorg

@turinglabsorg turinglabsorg commented Sep 4, 2026 •

Copy link
Copy Markdown
Owner

Summary

  • Make hush doctor validate the encrypted BITWARDEN_SESSION automatically.
  • Make hush bitwarden status report whether the validated session came from encrypted storage.
  • Keep session injection scoped to the bw status subprocess.
  • Bump the release version to 0.4.1.

Verification

  • cargo test --locked
  • cargo clippy --locked -- -D warnings
  • cargo fmt --check
  • Skill validation
  • Live doctor and bitwarden status against the encrypted agent session

@turinglabsorg
turinglabsorg merged commit f7593b5 into main Sep 4, 2026
1 check passed
@turinglabsorg
turinglabsorg deleted the fix/managed-bitwarden-session-status branch September 4, 2026 05:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant