CLI Authentication Became More Trustworthy

Kindship now distinguishes configured credentials from genuinely authorized ones, restores Codex device auth more cleanly, and keeps cross-CLI behavior more consistent.

This was a trust-building update. The workspace got much better at telling you whether a coding CLI is really ready to run, instead of stopping at the weaker question of whether a credential exists somewhere.

Auth Status Became Honest

Credential state is now much closer to the truth users care about.

  • The UI distinguishes configured from genuinely authorized credentials
  • Status labels now separate not installed, not reachable, not configured, and auth failed
  • Failure reasons surface more clearly, so fixing a provider is less of a blind hunt

Codex Device Auth Came Back In A Cleaner Form

Codex setup is less awkward again, especially if you prefer device-based login.

  • Codex device auth is available again in the credentials dialog
  • Local device-auth sessions are detected properly
  • The dialog layout is more usable for longer credential instructions and multi-provider setup

Cross-CLI Behavior Is More Consistent

The broader coding-agent fleet behaves more like one coherent system.

  • Runs now remember which CLI produced them, so activity parsing is less guessy
  • Shared skills fan out more consistently across supported CLIs
  • Cross-tool execution feels less like a series of special cases