ns-omp-provider-kiro
v0.4.0
Published
OMP (oh-my-pi) provider plugin: adds Kiro (AWS CodeWhisperer/Q) models via your kiro-cli login
Maintainers
Readme
ns-omp-provider-kiro
Kiro (AWS CodeWhisperer/Q) models in OMP.
Published on npm as ns-omp-provider-kiro:
omp plugin install ns-omp-provider-kiroPin a version with omp plugin install [email protected] — bare
names, scoped names, and name@version all resolve as npm specs.
From a local build
To build from a clone instead — for developing this package or
ns-kiro-core before a release — install from the path:
git clone [email protected]:ngosangns/ns-bridge.git
cd ns-bridge && pnpm install && pnpm -r build
omp plugin install ./packages/omp-provider-kiroSign in once with kiro-cli — Builder ID, IAM Identity Center, Google, GitHub, or enterprise OIDC all work, because kiro-cli does them:
kiro-cli loginThen, in OMP:
/login kiro
/model/login kiro picks up the kiro-cli session and refreshes it when it expires,
writing the refresh back so both tools stay on the same token. With no session
on the machine it prompts for a Kiro API key (ksk_…) instead.
/model lists whatever your account's region actually serves: the catalog is
fetched from Kiro's management API and cached for an hour, so a model added
upstream shows up without a release here.
Notes
- Reasoning effort maps onto Kiro's own ladder per model —
xhighandmaxexist only where the model advertises them, and a request for more thinking than a model offers is clamped rather than rejected. - Usage (
/settings) reports the account's Kiro credit balance — the one the host is signed in with, so run/login kiroafter signing the machine into a different account. - Sessions come from the machine: the kiro-cli store first, the Kiro IDE's token
file as a fallback. They can be different IdC users of the same Kiro profile,
so
KIRO_AUTH_SOURCE=ideswitches a machine over to the IDE's login instead. KIRO_API_KEYis read as a fallback when no session is stored.KIRO_DEBUG=1writes a full request/response trace to~/.ns-kiro-provider/logs/kiro-debug.log, with credentials redacted.
This is the recommended Kiro path in OMP. ns-omp-provider can also register a
kiro provider, but leaves it off by default so the two never fight over the id.
Part of ns-bridge.
