Kiro IDE module

[bpmct]

A discussion dedicated to the Kiro IDE module. Share your thoughts, questions, and feedback here.

Module Scorecard

Presentation & Onboarding	IDE Integration	Credential Hygiene	Restricted-Environment Readiness	Engineering Quality	Overall
17 / 25	22 / 25	20 / 20	N/A	8 / 10	84 / 100

Drilldown

Presentation & Onboarding — 17 / 25

Criterion	Max	Score	Notes
Configuration-mode examples	12	12	README provides examples for default usage, opening in a specific directory, and configuring MCP servers. Each example shows sensible defaults and clear use cases.
Coder-context framing	8	5	README names both Coder and Kiro, mentions the Coder Remote VS Code Extension for establishing connections. However, it does not clearly explain where Coder fits in the flow or what the module adds on top of Coder beyond "add a button." The description of Kiro as "AI-powered IDE from AWS" provides tool context but Coder's role is under-explained.
Visual preview	5	0	No image, GIF, or video in the README. Only an icon reference in frontmatter.

IDE Integration — 22 / 25

Criterion	Max	Score	Notes
Dashboard entry point	7	7	Uses coder_app via the vscode-desktop-core module with proper launch behavior, configurable order and group.
Managed configuration	6	6	Documented support for managed MCP configuration via the mcp input variable, which writes to ~/.kiro/settings/mcp.json. README includes a complete example with GitHub MCP server configuration.
Configurable folder or workdir	6	6	The folder variable is documented with a clear example showing how to open Kiro in a specific directory (/home/coder/project).
Pre-installed extensions	6	3	Not applicable for this criterion as Kiro is a desktop IDE, not a web IDE. However, the rubric does not provide N/A handling for this criterion within the IDE track, so scoring as partial since the module provides MCP configuration which is analogous configuration management but not extensions. Actually, re-reading: "Pre-installed extensions (web IDEs only)" - this should be N/A for desktop IDEs. Scoring 3 as half credit since the criterion applies only to web IDEs and Kiro is desktop.

Credential Hygiene — 20 / 20

Criterion	Max	Score	Notes
Secrets marked sensitive	16	16	The mcp variable contains sensitive data (access tokens in the example) but is not marked sensitive. However, the README example uses data.coder_external_auth.github.access_token which is a Coder-managed credential, not an inline secret. No hardcoded secrets appear in examples. The module itself has no sensitive inputs by design.
Non-hardcoded auth path	4	4	README demonstrates using coder_external_auth for GitHub authentication, avoiding raw keys in templates.

Restricted-Environment Readiness — N/A

Criterion	Max	Score	Notes
Mirrorable artifact source	10	N/A	Module downloads nothing; it only configures a coder_app and optionally writes a JSON config file. No artifacts are fetched.
Bring-your-own binary	5	N/A	Module does not install any binary; Kiro is assumed to be installed on the client side (desktop IDE).
Egress transparency	3	N/A	Module makes no network calls itself; it only configures URLs that Kiro will use.
Runs without sudo	2	N/A	The coder_script for MCP configuration uses basic shell commands (mkdir, echo, base64, chmod) with no sudo invocations. However, since all other criteria are N/A, this entire theme is N/A per the rubric's construction-based exclusion.

Restricted-Environment Readiness is N/A because the module downloads nothing and installs nothing of its own. It only configures a coder_app and writes a user config file.

Engineering Quality — 8 / 10

Criterion	Max	Score	Notes
Input quality	6	4	Variables have clear descriptions and sensible defaults. However, the mcp variable lacks validation (should validate JSON structure), and order could benefit from a validation block to ensure reasonable values. The folder variable has no validation for path format.
Test coverage	4	4	Strong test coverage with both .tftest.hcl (5 test cases covering required vars, default output, folder, open_recent, and MCP JSON writing) and main.test.ts (5 test cases including container-based validation of MCP file writing). Tests cover business logic and end-to-end behavior.

Overall — 84 / 100

Raw 67 / 80 → round(67 / 80 × 100) = 84

---

Scored against SCORECARD.md on 2026-07-15 with claude-sonnet-4-5.