andyvandaric/kiroku

★ 25PowerShellAudience · developerComplexity · 2/5ActiveSetup · moderate

Mindmap

mindmap
  root((kiroku))
    Inputs
      Kiro accounts
      Chat prompts
      Install script
    Outputs
      Active session
      Account rotation
      Quota status
    Use Cases
      Avoid credit cutoff
      Pool many accounts
      Drop-in CLI replace
      Long coding sessions
    Tech Stack
      PowerShell
      Bash
      Kiro CLI
      WezTerm

mindmap root((kiroku)) Inputs Kiro accounts Chat prompts Install script Outputs Active session Account rotation Quota status Use Cases Avoid credit cutoff Pool many accounts Drop-in CLI replace Long coding sessions Tech Stack PowerShell Bash Kiro CLI WezTerm

Things people build with this

USE CASE 1

Pool multiple Kiro CLI accounts and keep a long coding session alive past one quota

USE CASE 2

Replace kiro-cli chat with kiroku chat for transparent account switching

USE CASE 3

Run a background quota watcher that swaps accounts before a hard credit cutoff

USE CASE 4

Set up WezTerm on Windows as the recommended host for Kiroku sessions

Tech stack

PowerShellBashKiro CLI

Getting it running

Difficulty · moderate Time to first run · 30min

You need one Kiro account per slot you want in the pool, and the install pipes a remote script through PowerShell or bash.

In plain English

Kiroku is a wrapper around Kiro CLI, an AI coding assistant tool. The README is written mostly in Indonesian, with English headings. The pitch is simple: Kiro CLI gives you a fixed amount of credits per account, around 1000, and a heavy coding day burns through them. When that happens the session breaks and you lose context. Kiroku lets you register many Kiro CLI accounts in a single pool and rotates between them automatically when one runs low. The command line is meant to be a drop-in replacement. You type 'kiroku chat' where you used to type 'kiro-cli chat', and the wrapper picks the active account, tracks remaining credits, and switches to the next one in the pool before the current one hits its limit. A background quota watcher does the monitoring, so the swap happens proactively rather than after a failure. A small status panel at startup shows the pool size, the current account, the remaining credits, and the watcher state. Installation is a one-line shell script. On Windows you pipe an install.ps1 through PowerShell 7. On macOS or Linux you pipe an install.sh through bash. The installer pulls in Kiro CLI if it is missing, verifies the binary checksum, sets up PATH, and on Windows also installs the WezTerm terminal as the recommended host. After install you run 'kiroku login' once per account you want to add, then 'kiroku account list' to see the pool. The tool runs on Windows x64, macOS on both Intel and Apple Silicon, and Linux on x64 and ARM64. The Kiro CLI requirement is real: you need an active Kiro account for each slot in the pool, and the author notes that the free tier works while the Pro tier is recommended. Kiroku itself is described as a private distribution at version 0.1.0, with the installer guiding access. The name comes from Kiro plus the Japanese word for path or road, framed as a ninja with many escape routes. No license file is mentioned in the README.

Copy-paste prompts

Prompt 1

Install Kiroku on Windows via the install.ps1 script and add three Kiro accounts to the pool

Prompt 2

Walk me through kiroku login and kiroku account list to confirm my pool is registered

Prompt 3

Explain how Kiroku's quota watcher decides when to rotate to the next Kiro account

Prompt 4

Wrap kiroku chat in a tmux session that survives terminal close on Linux ARM64

Prompt 5

Audit the install.sh script before piping it to bash on macOS Apple Silicon

Open on GitHub → Explain another repo

Generated 2026-05-22 · Model: sonnet-4-6 · Verify against the repo before relying on details.