Codexbar is not working for kiro-cli

[whiletruelearn]

[clawsweeper]

Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed June 28, 2026, 4:09 AM ET / 08:09 UTC.

Summary
Keep open under this repository's conservative cleanup policy: current main likely addresses the visible Kiro timeout through the merged PTY-based Kiro fix, but the report only includes a screenshot and the fix is not in the latest release tag.

Reproducibility: unclear. The screenshot proves the visible timeout message, but it does not include versions or command output, and I did not run a live Kiro probe under the repository policy.

Ways to help us reproduce this

• Add expected vs actual behavior.

Next step
No repair lane is safe yet because current main already has the likely Kiro timeout fix and the report lacks enough data to identify a distinct remaining failure.

Review details

Best possible solution:

Ship the PTY-based Kiro fix, then ask for versions and redacted kiro-cli --version plus codexbar usage --provider kiro --source cli --format json --json-only --no-color output if the timeout still happens.

Do we have a high-confidence way to reproduce the issue?

Unclear. The screenshot proves the visible timeout message, but it does not include versions or command output, and I did not run a live Kiro probe under the repository policy.

Is this the best way to solve the issue?

Yes for the known timeout shape: current main's PTY transport is the narrow maintainable fix for kiro-cli needing a terminal. It is unclear whether this report still fails after that commit.

AGENTS.md: found and applied where relevant.

Remaining risk / open question:

• The report lacks CodexBar version, kiro-cli version, direct kiro-cli timing, and codexbar usage --provider kiro output, so it cannot yet prove a new current-main failure.
• The most relevant fix is current-main-only by local tag inspection, so released users may still see this until a release includes the PTY change.
• No live Kiro provider probe was run because repository policy says live provider checks need explicit request.

Codex review notes: model internal, reasoning high; reviewed against 18eab6b68e3e.

Label changes

Label changes:

• add P2: A Kiro provider timeout breaks usage visibility for affected users, but the blast radius is limited to one provider path and likely already has a main-branch fix.
• add impact:auth-provider: The issue affects provider CLI discovery/execution for Kiro usage collection.
• add issue-rating: 🦪 silver shellfish: Current issue advisory state selects this label.
• add clawsweeper:needs-info: Current issue advisory state selects this label.

Label justifications:

• P2: A Kiro provider timeout breaks usage visibility for affected users, but the blast radius is limited to one provider path and likely already has a main-branch fix.
• impact:auth-provider: The issue affects provider CLI discovery/execution for Kiro usage collection.

Evidence reviewed

What I checked:

• Repository policy read: AGENTS.md was read fully; its guidance to prefer focused provider/parser inspection and avoid live provider probes without explicit request was applied. (AGENTS.md:23, 18eab6b68e3e)
• Issue screenshot: The attached image shows the Kiro menu card reporting Kiro CLI timed out. with no CodexBar version, kiro-cli version, or command output.
• Kiro provider contract: Kiro is a supported CLI-only provider that uses kiro-cli chat --no-interactive "/usage" and requires the CLI to be installed and logged in. (docs/kiro.md:11, 18eab6b68e3e)
• Current main behavior: Current main runs Kiro /usage through runViaPTY with a 20 second deadline and maps PTY timeout to KiroStatusProbeError.timeout. (Sources/CodexBarCore/Providers/Kiro/KiroStatusProbe.swift:417, 18eab6b68e3e)
• Merged PTY fix provenance: Merged PR fix(kiro): run kiro-cli through a PTY so usage loads (fixes #1619) #1744 says real kiro-cli 2.8.1 and packaged-app proof showed Kiro usage returning in seconds after routing whoami, /usage, and /context through the PTY runner. (Sources/CodexBarCore/Providers/Kiro/KiroStatusProbe.swift:450, da693aa7ce9f)
• Release provenance: The PTY fix commit is only contained by main in this checkout; git tag --contains returned no release tags, so latest release v0.37.2 predates the likely fix. (da693aa7ce9f)

Likely related people:

• sf-jin-ku: Authored the merged Kiro PTY transport work that directly targets the visible timeout symptom. (role: recent area contributor; confidence: high; commits: 4ac29c375187, da693aa7ce9f; files: Sources/CodexBarCore/Providers/Kiro/KiroStatusProbe.swift, Tests/CodexBarTests/KiroStatusProbeTests.swift)
• steipete: Contributed Kiro PTY cleanup repairs, documented the landing of PR 1744, and authored the current main changelog commit. (role: recent area contributor and merger; confidence: high; commits: d9424144fc8c, 9c8a9a667329, 18eab6b68e3e; files: Sources/CodexBarCore/Providers/Kiro/KiroStatusProbe.swift, Sources/CodexBarCore/Host/Process/SpawnedProcessGroup.swift, CHANGELOG.md)
• Nathan Eror: Introduced the Kiro provider and initial AWS kiro-cli usage tracking surface. (role: introduced behavior; confidence: medium; commits: bbda93528714; files: Sources/CodexBarCore/Providers/Kiro/KiroStatusProbe.swift, Sources/CodexBarCore/Providers/Kiro/KiroProviderDescriptor.swift, Tests/CodexBarTests/KiroStatusProbeTests.swift)
• Yuxin-Qiao: Authored the earlier merged account-probe timeout fix on the same Kiro usage path. (role: recent timeout contributor; confidence: medium; commits: 8009f70b60ac; files: Sources/CodexBarCore/Providers/Kiro/KiroStatusProbe.swift, Tests/CodexBarTests/KiroStatusProbeTests.swift)

How this review workflow works

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

[steipete]

Closing as fixed on current main by #1744 (da693aa7). That change routes Kiro whoami, /usage, and /context through the PTY transport required by current kiro-cli; the PR includes redacted real kiro-cli 2.8.1 and packaged-app proof, and its exact-head CI passed.

Important release boundary: the fix is not in the latest v0.37.2 tag yet. If the timeout persists after a release containing da693aa7, please reopen with the CodexBar version, kiro-cli --version, and redacted output from:

CodexBar.app/Contents/Helpers/CodexBarCLI usage --provider kiro --source cli --format json --json-only --no-color

[whiletruelearn]

@steipete Thanks for the update. Just curious to know when is the new release expected .

[steipete-oai]

Will be out tomorrow!