Kiro Account Manager: multi-account Kiro IDE credential manager with a built-in API gateway

A Tauri 2.x desktop app that automates account rotation for Kiro IDE quota management

Kiro Account Manager addresses one specific friction point in using Kiro IDE: running multiple personal accounts to extend AI usage quotas. The app stores credentials, monitors per-account limits, and switches to the next account automatically when the active one is exhausted, without user intervention.

The backend is Rust with Tauri 2.x; the frontend is React 18 using Vite, shadcn/ui components, and TailwindCSS 4. This gives the app a native desktop window on Windows, macOS, and Linux without an Electron-style full browser runtime.

Account management covers import, export, token refresh, validation, grouping, and remote deletion. Grouping and tagging let users organise credentials when the count grows. The Kiro integration layer syncs model selection, proxy configuration, MCP, Steering, Skills, Hooks, Custom Agents, Powers, and permissions to the active account whenever an account switch happens.

Binary packages for Windows, macOS, and Linux; the portable ZIP skips auto-update

All three platforms offer pre-built binary packages from the repository's download page. Windows has two options: an MSI installer and a portable ZIP. The MSI installs to %LOCALAPPDATA%\Apps\KiroAccountManager by default without needing administrator privileges; choosing install for all users does require administrator access. The portable ZIP extracts to any directory.

A key difference between the two Windows packages: the MSI supports automatic updates while the portable ZIP does not. The README states that portable ZIP users must manually download and overwrite each new binary package. The portable ZIP also depends on Edge WebView2, which the README notes is generally pre-installed on Windows 10 and Windows 11.

On macOS, the download page offers DMG and tar.gz app bundles for both Intel x64 and Apple Silicon ARM64. The system requirement is macOS 10.15 (Catalina) or later. On Linux, AppImage, DEB, and RPM packages are available for x86_64 and ARM64. Linux requires WebKitGTK 4.0 or later. For AppImage, set the executable bit and run directly; for DEB, install with the system package manager.

Three authentication methods have in-app flows; Microsoft Entra ID is import-only

Google, GitHub, and AWS IAM Identity Center each work through an in-app OAuth flow. AWS IAM Identity Center covers both BuilderId and Enterprise account types. Deep Link OAuth callbacks return the result to the desktop app after browser-based authentication.

Microsoft Entra ID and Azure AD are handled differently. Support exists through the external_idp path, but there is no in-app Microsoft login flow. Entra ID credentials must be imported from a token file obtained outside the app. After import, the app handles subsequent token refreshes by calling the Microsoft OAuth2 token endpoint directly, not through AWS OIDC.

A known issue in earlier builds was that Enterprise accounts were sometimes misclassified as BuilderId during import, causing refresh failures with HTTP 400 errors. The public branch update notes describe a fix that extracts the startUrl and provider from the clientSecret JWT at import time and prioritises the enterprise domain to prevent misclassification.

The built-in API gateway proxies Anthropic Messages and OpenAI Chat Completions to Kiro

An embedded Kiro API Gateway listens locally and accepts three request formats: Anthropic Messages API, OpenAI Responses API, and OpenAI Chat Completions. Streaming is supported for all three. Requests are forwarded to Kiro's backend under the active account's credentials.

For OpenAI-formatted requests, the gateway uses tiktoken-rs with the o200k_base encoding to estimate token counts before forwarding. The o200k_base vocabulary is the encoding used by OpenAI's newer models. The current public branch adds GPT-5.6 series and Claude Sonnet 5 to the gateway's model list and removes Claude 3 alias mappings that are no longer active.

The practical result is that any tool that speaks Anthropic Messages or OpenAI Chat Completions can point at the local gateway instead of the upstream API. Account switching and quota monitoring then apply automatically through the app's account pool, with no changes needed in the calling tool.

macOS style defects cannot be reproduced by the developer; a note in the README says why

A single italic note in the macOS installation section of the README states: if style display abnormalities appear, adjust based on the current repository source code yourself, because the author does not have a macOS device and cannot reproduce or debug the issues. This disclosure sits after the install instructions and is the only mention of it in the documentation.

The June 2026 binary package update notes cover two macOS items: a fix for the macOS window not displaying after launch, and an update to the Intel x86_64 build environment. Both were addressed based on user reports, without the author being able to reproduce the conditions.

For macOS users, visual regressions have no guaranteed fix path from the repository owner. Any macOS-specific style defect that appears in a future binary package would depend on community contributors who have hardware to test on. The window-not-displaying bug was significant enough to land in the first patch from June 2026, and the README note makes clear that the same pattern of community-driven debugging would apply to future macOS issues.

The public branch adds Kiro IDE 1.0 format support for hooks, agents, and permissions

The public branch update notes distinguish changes already in the binary download from changes merged but not yet packaged. Several items in the latter category track Kiro IDE 1.0 format changes.

Hooks in Kiro IDE 1.0 moved from per-file .kiro.hook entries to a JSON format where a single file holds multiple hooks, with field names changing from hook to trigger and action. Custom Agents changed from Markdown front-matter to a JSON format. User-level global hooks at ~/.kiro/hooks became available. The public branch supports both old and new formats for each of these, so existing configuration survives an IDE upgrade without manual migration.

Permissions changed from a Trusted Commands model to a permissions.yaml capability model. The public branch adds a global permissions rule editor and reads and writes ~/.kiro/settings/permissions.yaml directly. On first read, it migrates old kiroAgent.* configuration automatically and removes the old Trusted Commands code paths.

Custom terms limit commercial use; building binary packages on macOS or Linux needs adjustment

The CC-BY-NC-SA-4.0 licence prohibits commercial use and requires attribution and share-alike terms for any derivative. The repository was last pushed on 2026-09-28.

Binary packages are available from the repository's download page, but they do not include the public branch changes described in the previous section. Users who want those changes must build from source. The package.json defines bun install for frontend dependencies and a tauri dev command for local development. A PowerShell file under the scripts/ directory handles production builds, so building binary packages on macOS or Linux requires working around or replacing that step.

A HALL_OF_SHAME.md file appears at the top level of the repository alongside the README, source code, and configuration files. The README does not describe that file's contents.

Editorial conclusion

Kiro Account Manager fits Kiro IDE power users who maintain two or more personal accounts and want automated token refresh and quota-triggered switching without editing config files by hand. The API gateway adds value for teams that want to route Anthropic Messages or OpenAI-format calls through Kiro's backend without changing the calling tool. Custom non-commercial terms apply to the project; check the terms document in the repository before deploying in any commercial context. On macOS, test the window display after first launch, since the developer states they have no macOS device and cannot reproduce or debug rendering defects from their side.

Frequently asked questions

Official sources

1. hj01857655/kiro-account-manager on GitHub
2. Issues
3. Project website
4. README
5. Releases