Skip to content

Releases: opencue/authmux

authmux v0.1.26

Choose a tag to compare

@NagyVikt NagyVikt released this 12 Jun 10:10

Patch release. Rolls up changes accumulated since the last tagged release (v0.1.23), including the previously untagged 0.1.24/0.1.25 work.

Highlights

  • Parallel account isolation — keep parallel Claude accounts isolated; cue aliases stay explicit; codex launches through cue (#38, #39, #40).
  • Skill-profile launches — specialize authmux launches by skill profile + launch-time skill-profile picker; add hermes-agent as a third skill-profile target (#35, #36).
  • CLI/JSON parity--json output across the remaining read commands (#34) and on 5 core commands.
  • Observability — structured logger + authmux diag bundle (#32); AuthmuxError taxonomy (#28).
  • Durability — atomic writes + registry lock; back up snapshots before codex and restore after symlink clobber (#24, #25, #29).
  • Refactors — split usage.ts (#33) and account-service.ts into focused modules (#30); lazy path getters (#27).
  • Renameagent-authauthmux with hermes-agent mirror.

Full changelog: v0.1.23...v0.1.26

codex-account-switcher v0.1.20

Choose a tag to compare

@NagyVikt NagyVikt released this 28 Apr 20:41
c6be654

codex-account-switcher v0.1.20

Summary

This patch keeps codex-auth use and official codex login snapshot sync on faster paths, then bumps the package to the next publishable npm version.

What's changed

  • Updated package metadata from 0.1.19 to 0.1.20.
  • Reused registry identity metadata during external login sync before falling back to parsing saved snapshots.
  • Collapsed direct account switching session-state updates so codex-auth use <account> records the active account and auth fingerprint in one session-map write.
  • Added regression coverage for registry-guided alias refresh when a saved snapshot needs to be overwritten from fresh login bytes.

Verification

  • npm test
  • npm pack --dry-run

Upgrade notes

  • No breaking CLI changes.
  • Manual publish should use npm publish --access public after verification.

Publish checklist

  1. Review package metadata and release notes.
  2. npm test
  3. npm pack --dry-run
  4. npm publish --access public
  5. Create GitHub release v0.1.20 from releases/v0.1.20.md