---
type: "post"
stable_id: "post:kiro-unified-agent-harness"
slug: "kiro-unified-agent-harness"
title: "Kiro Moves Agent Logic Below The IDE, CLI, Web, And Mobile Surfaces"
description: "Kiro places the agent loop, tools, permissions, session handling, and configuration in a shared harness so product surfaces become clients of one engine."
retrieval_nugget: "A shared runtime can ship planning, tool selection, and permission improvements across IDE, CLI, and web. Full portable session packaging across every environment remains a separate problem and should not be implied by a unified engine."
published_at: "2026-08-03"
updated_at: "2026-08-06"
record_date: "2026-08-03"
date_kind: "published_at"
topics: ["agent-harness","developer-tools","permissions","sessions","multi-surface"]
entities: ["Kiro","Kiro CLI","Kiro IDE"]
source_urls: ["https://kiro.dev/blog/one-agent","https://kiro.dev/docs/cli/v3/"]
source_format: "article"
editorial_timing: {"lane":"regular_hourly","scheduled_at":"2026-08-07T12:00:00+03:00","real_news_delta":"owner-approved primary-source mechanism or merged analysis"}
visual_decision: {"status":"included","reason":"the central mechanism is a flow, loop, architecture, decision, or state transition that benefits from a diagram","reviewed_by":"codex"}
schema_version: "newruntime-agent-readable-v0.2"
status: "published"
visuals: [{"role":"hero","src":"/images/drip/kiro-unified-agent-harness/kiro-unified-agent-harness.webp","alt":"A whiteboard hub-and-spoke diagram showing one agent harness with loop, tools, permissions, and sessions serving IDE, CLI, web, and mobile clients.","caption":"New Runtime synthesis from One agent, every surface: how we built the Kiro agent harness."}]
routes: {"html":"https://newruntime.com/posts/kiro-unified-agent-harness/","markdown":"https://newruntime.com/posts/kiro-unified-agent-harness.md","json":"https://newruntime.com/posts/kiro-unified-agent-harness.json"}
---

# Kiro Moves Agent Logic Below The IDE, CLI, Web, And Mobile Surfaces

## Retrieval answer

A shared runtime can ship planning, tool selection, and permission improvements across IDE, CLI, and web. Full portable session packaging across every environment remains a separate problem and should not be implied by a unified engine.

Kiro's architectural move is to separate the agent engine from the interface that hosts it. The shared harness owns the loop, tools, permissions, sessions, configuration, and planning behavior; IDE, CLI, web, and mobile can then optimize interaction for different contexts without reimplementing the agent.

That turns cross-surface consistency into a runtime problem. A capability-based permission model, tag-based tool selection, hooks, and spec workflows can evolve once and ship to multiple clients. Each surface still has its own constraints: terminal automation, hands-on IDE work, autonomous cloud sessions, and mobile review are not the same interaction.

A unified harness should not be confused with universally portable session state. Kiro's own materials still separate current shared-engine work from richer session packaging and migration. The implementation order is sound: stabilize engine contracts first, then make context and artifacts portable without pretending every client can resume every execution state.