Kiro Integration Guide

Overview

Kiro is an AWS-backed agentic IDE/CLI built around spec-driven development. Cup’n’String provides process detection, provider/API governance, MCP-aware controls where available, and local workspace protection.

Support level

Auto-Discovered + Compatibility Adapter

What Cup’n’String detects

• Kiro IDE and CLI processes
• Workspace paths
• Agent configuration where available
• Provider/API egress

What it governs

• Outbound model/provider traffic
• Local service access
• Secret exposure
• MCP/tool activity where routed through managed paths

Recommended policies

• Use observe mode first
• Allow approved AWS/Kiro endpoints as required
• Block unknown model gateways
• Shield project and cloud credentials

Setup outline

1. Ensure the Cup’n’String agent is active.
2. Launch Kiro CLI or IDE.
3. Configure regional endpoints in Cup’n’String to observe Kiro traffic patterns.

Verification

Review logs in the Cup’n’String console to ensure Kiro processes are auto-discovered and mapped under active environments.

Troubleshooting

If process hooks are missing, verify that Kiro CLI is in your system PATH and visible to the agent runner.

Known limitations

Native depth depends on available Kiro integration hooks.