Kiro vs OpenCode | agentconfig.ing

Kiro vs OpenCodeComparisonUpdated 2026-03-16

SUMMARY

Kiro (IDE) uses markdown configuration while OpenCode (CLI) uses markdown. They differ on 2 of 11 compared features. Both tools provide AI-assisted development but take different approaches to project configuration.

FEATURE COMPARISON

Feature	Kiro	OpenCode	Notes
Config format	markdown	markdown
Hierarchy support	✓	✓	Whether config files can be placed at multiple directory levels
Global config	✓	✓	User-wide configuration outside any project
Project config	✓	✓
Subdirectory scoping	✗	✓	Config files in subdirectories that apply only to that subtree
File inclusion / imports	✗	✗	Ability to include or reference other files from config
Ignore file	✗	✗
IDE integration	✓	CLI
Schema / structure	Free-form (Markdown)	Free-form (Markdown)	Whether config uses structured schema or free-form content
Git committed	✓	✓	Whether primary config files are intended to be version-controlled
Encoding	UTF-8	UTF-8

FILE MAPPING

Purpose	Kiro	OpenCode
Project instructions	.kiro/steering/*.md	AGENTS.md
Settings / configuration	.kiro/hooks/*.kiro.hook	opencode.json
Project instructions	AGENTS.md	CLAUDE.md
Project instructions	.kiro/agents/*.md	.opencode/agents/*.md

SIDE-BY-SIDE CODE SAMPLES

Kiro

.kiro/steering/*.md

markdown

---
inclusion: always
---

# Project Standards

## Stack
- TypeScript 5.x with Node.js 22
- AWS CDK v2 for infrastructure
- DynamoDB for data, S3 for assets

## Conventions
- Use ESM imports, not CommonJS
- Lambda handlers export a named `handler` function
- Use middy middleware for cross-cutting concerns
- All API responses follow JSON:API format

## Testing
- Unit tests with vitest
- Integration tests with aws-testing-library
- E2E tests use deployed staging environment

OpenCode

AGENTS.md

markdown

# Project Instructions

## Overview
This is a TypeScript monorepo using pnpm workspaces.

## Code Style
- Use strict TypeScript with no implicit any
- Prefer functional components with hooks
- All exports should be named (no default exports)

## Architecture
- /packages/core — shared business logic
- /packages/ui — React component library
- /apps/web — Next.js frontend

## Build & Test
Run tests with: pnpm test
Build all packages: pnpm build
All PRs must have >80% coverage on changed files.

## Conventions
- Use conventional commits (feat:, fix:, chore:)
- Prefer composition over inheritance
- See @docs/api-guidelines.md for API design patterns

KEY DIFFERENCES

1. Subdirectory scoping

Kiro: Not supported. OpenCode: Supported.

2. IDE integration

Kiro: Supported. OpenCode: CLI.

WHICH SHOULD I USE?

Recommendation

Choose based on your IDE/CLI preference. If you use Kiro, configure .kiro/steering/*.md. If you use OpenCode, configure AGENTS.md. Many projects include config files for multiple tools so each team member can use their preferred editor.

PORTABILITY TIP

sync-instructions.sh

bash

# Maintain a single source of truth:
cp AI-INSTRUCTIONS.md CLAUDE.md
cp AI-INSTRUCTIONS.md .cursorrules
cp AI-INSTRUCTIONS.md AGENTS.md