pnpm add -g @i4ctime/q-ring # or: npm i -g / brew install i4ctime/tap/qring
qring doctor # verify keyring backend + qring-mcp on PATHPreferred: add kiro-plugin/ from a checkout of this repo as a Power via Kiro's Powers panel (docs) — it reads POWER.md and wires mcp.json, steering, and hooks.
Or copy into your Kiro config directly:
pnpm install
pnpm run plugin:sync:kiro # mcp.json → ~/.kiro/settings, plus steering/ and hooks/Kiro's mcp.json ships an autoApprove allowlist for the read-only tools, so status/context calls don't prompt.
qring set OPENAI_API_KEY # value prompted, maskedSteering docs activate on demand with # tags in chat:
| Type | What you get |
|---|---|
#qring-secret-management |
Store/retrieve/organize workflow guidance + live tools |
#qring-secret-scanning then "scan this repo" |
Hardcoded-secret scan with auto-fix |
#qring-cmd-health-check |
Full health report — decay, anomalies, audit integrity |
#qring-exec-with-secrets then "run the tests" |
exec_with_secrets with redacted output |
#qring-cmd-dashboard |
Live localhost dashboard |
The three hooks watch file writes and shell commands for .env/credential leaks.
MCP server not connecting, keyring errors → troubleshooting.md. Full Power reference → kiro-plugin/README.md.