sbx/kiro-mixin
Kiro CLI overlay with network policy and MCP gateway setup. Run kiro-cli login before starting chat.
6.8K
sbx/kiro-mixin repository overview
Kiro CLI overlay with network policy and MCP gateway setup. Run kiro-cli login before starting chat.
| Name | Required | Default | Description |
|---|---|---|---|
version | Required | — | Kiro CLI release carried by the image |
[email protected]| Type | Required | Description | |
|---|---|---|---|
com.docker.sandbox/network-policy@1 | Required | — | |
com.docker.sandbox/lifecycle@1 | Required | — | |
com.docker.sandbox/agent-context@1 | Optional | — | |
com.docker.sandbox/agent-context@2 | Optional | — | |
com.docker.sandbox/acp@1 | Optional | — | |
Apply this mixin to a sandbox
sbx run <agent> --kit sbx/kiro-mixin:latestMake sure you have docker sbx installed
Run the following command to install sbx on your machine.
brew install docker/tap/sbxwinget install Docker.sbxKiro mixin for Docker Sandboxes
This v3 mixin Kit packages Kiro for Docker Sandboxes. It adds the agent, authentication configuration, and runtime integration to a compatible workload. The workload keeps its entrypoint.
This Kit is built on Docker Hardened Images.
Run
sbx run sbx/shell:latest --kit sbx/kiro-mixin:latest /path/to/workspace
When the shell opens, run kiro-cli chat. This kit supplies an overlay, so it needs a workload such as
Shell.
A manual kiro-cli chat launch keeps its native approval behavior. To match the workload's automatic tool approval, run
kiro-cli chat --trust-all-tools.
Kit arguments
This kit has no create-time kit arguments.
Authentication and configuration
Run kiro-cli login inside the sandbox before starting a chat. This kit does not declare a proxy-managed credential
service. Kiro manages its own sign-in state.
Sign-in state survives stop/start of the same sandbox but is lost when you recreate it. Kiro's sign-in state is not persisted to the host.
The default network policy permits oidc.us-east-1.amazonaws.com:443. If you use IAM Identity Center in another region,
allow oidc.<region>.amazonaws.com:443 in the host runtime's network policy. Use sbx policy log on the host to
identify a blocked login endpoint.
When the runtime supplies an MCP gateway, the kit registers it automatically in ~/.kiro/settings/mcp.json. Startup
replaces this entire file whenever a gateway is configured. Back up custom entries before restarting the sandbox.
ACP support is included. Configure an ACP client to open a non-TTY stream to the sandbox.
sbx exec -i <sandbox> kiro-cli acp
The sandbox supplies the isolation for agent tool execution. Launch the kit through Docker Sandboxes and configure extra tool or MCP destinations in the runtime network policy as needed.
If a tool cannot reach a service, run sbx policy log on the host to identify blocked destinations.
Related kits
sbx/kiro provides the complete agent workload.
Source and security
For the Kit format and capability contracts, see the Sandbox Kit v3 specification.
For runtime setup, see the Docker Sandboxes documentation. For provenance, SBOM, VEX, and image verification, see the Docker Hardened Images documentation.
Kiro is a product of Amazon Web Services. Product names and logos do not imply sponsorship or endorsement.