Kiro CLI 1.24+ output format change breaks usage parsing

[kilhyeonjun]

Summary

The Kiro provider fails to parse usage data with error:

Failed to parse Kiro usage: No recognizable usage patterns found. Kiro CLI output format may have changed.

This appears to be caused by Kiro CLI changing its /usage output format, likely related to AWS Q Developer rebranding.

Environment

• CodexBar version: 0.18.0-beta.2
• kiro-cli version: 1.24.1
• macOS version: Tahoe
• Plan type: Q Developer Pro (IAM Identity Center / managed by admin)

Expected Output (what parser expects)

Based on KiroStatusProbe.swift and KiroStatusProbeTests.swift, the parser expects:

| KIRO FREE                                          |
████████████████████████████████████████████████████ 25%
(12.50 of 50 covered in plan), resets on 01/15
Bonus credits: 5.00/10 credits used, expires in 7 days

The parser looks for these regex patterns:

• \|\s*(KIRO\s+\w+) - plan name (e.g., | KIRO FREE)
• █+\s*(\d+)% - progress bar with percentage
• \((\d+\.?\d*)\s+of\s+(\d+)\s+covered - credits used/total
• resets on (\d{2}/\d{2}) - reset date

Actual Output (kiro-cli 1.24.1)

Plan: Q Developer Pro
Your plan is managed by admin

Tip: to see context window usage, run /context

Analysis

1. Rebranding: "KIRO" → "Q Developer" - plan name format completely changed
2. No credits display: Enterprise/managed plans may not show credit usage
3. No progress bar: The ████ pattern is gone
4. Different structure: Output is now plain text without the table-like format

Possible Solutions

1. Update parser to handle new format:

   • Parse Plan: (.+) for plan name
   • Handle "managed by admin" case (show plan name only, no usage %)
   • Try /context command for usage data?

2. Graceful degradation: When old patterns don't match, try new patterns; if still no match, show "Usage data unavailable" instead of error

Steps to Reproduce

1. Install kiro-cli 1.24+
2. Login via kiro-cli login (IAM Identity Center)
3. Enable Kiro provider in CodexBar
4. Observe error in menu bar / logs

Additional Context

• kiro-cli whoami works correctly:

  Logged in with IAM Identity Center (https://d-xxxxxxxx.awsapps.com/start)
  Profile: QDefaultProfile
  

• The issue may affect both enterprise (managed) and personal (free/pro) plans differently