Loading image...Kiro

Product

  • About Kiro
  • IDE
  • CLI
  • Web
  • Mobile
  • Crew
  • Pricing
  • Downloads

For

  • Enterprise
  • Startups
  • Students

Community

  • Overview
  • Ambassadors
  • Discord
  • Events
  • Powers
  • Shop
  • Showcase

Resources

  • Docs
  • Blog
  • Changelog
  • FAQs
  • Report a bug
  • Suggest an idea
  • Billing support

Social

Site TermsLicenseResponsible AI PolicyLegalPrivacy PolicyCookie Preferences
Loading image...Kiro
  • CLI
  • Web
  • Enterprise
  • Pricing
  • Docs
SIGN INDOWNLOADS
Loading image...Kiro

Get Started

InstallationAuthenticationYour first project

Models

OverviewAvailable modelsReasoning effort

Features

How Kiro works
Specs
Steering
Hooks
MCP
Permissions
Custom agents
Agent Skills
Powers
Cloud sessionsCompactionKiroignoreCheckpoints and rewind
Built-in tools
Configuration scopes

IDE 1.x

What's new in 1.0
Setup & First Run
Editor
Chat
Autopilot
Agent Artifacts
Slash commands
Agent notifications
Dockable chat
Export sessions
Terminal
Dev servers
Experimental
Troubleshooting0.x reference

CLI

What's new in 3.0
Setup & First Run
Terminal UI
Chat
Voice modeHeadless modeACPAuto complete
Experimental
2.x reference

Crew

Quick startInstallationRunning 24/7
Chat
Agent Capabilities
Features
Interfaces
Apps
System & storageConfigurationSecurityTroubleshooting

Web

Setup & First RunIdentity Center
Connect your repositories
Working with the agent
Autonomous modeAutomationsMemoryConfiguration Sync
Sandbox

Mobile - Preview

Overview

Commands and Reference

CLI commandsSlash commandsBuilt-in toolsExit codesSettings

Billing

OverviewManaging your subscriptionUpgrading your planDowngrading your planCancelling your planPurchasing add-on creditsManaging your paymentsManaging usage notificationsManaging your taxesContacting billing supportDeleting your accountRelated questions

Enterprise

ConceptsOnboarding quickstart
Connecting your identity provider
Deployment optionsSubscribe your teamManage subscriptions
Governance
Monitor and track
SettingsManaged updatesBillingIAMSupported regions

Privacy and Security

OverviewData protectionCode referencesCompliance validationInfrastructure securityIAM permissionsFirewalls, proxies, and data perimetersVPC endpoints (AWS PrivateLink)

Guides

Overview
Language support
Learn by playing

Migration

Migrating from Q DeveloperMigrating from VSCodeUpgrading from Q CLI
  1. Docs
  2. IDE 1.x
  3. Chat
  4. Agent Artifacts
View as Markdown

Agent Artifacts

View as Markdown

Overview

Agent Artifacts are durable outputs that Kiro creates during a chat session. Instead of leaving a document, diagram, or preview buried in the conversation, Kiro presents it as an artifact that you can open again while the session is available.

Artifacts are session outputs, not project files. Creating an artifact does not add it to your repository or commit it to version control. If you need the content in your project, ask Kiro to create or update a project file separately.

Supported content

Kiro can display these artifact types:

  • Markdown documents
  • Mermaid diagrams
  • Code
  • SVG
  • HTML
  • Images
  • PDF documents
  • Microsoft Office documents

PowerPoint (.pptx) artifacts appear as a text outline. HTML artifacts do not run scripts, so interactions that depend on JavaScript are unavailable. Each artifact has a maximum payload size of 12 MB.

Review an artifact

When an agent creates an artifact, a compact preview appears in the chat transcript. Open the preview to inspect the artifact without searching through the conversation.

In Agent Focus Mode, the full artifact opens beside the chat. The context panel lists the session's artifacts along with Specs and Changed Files, so you can return to an artifact later in the same session.

Storage and project boundaries

Kiro stores artifacts per session in its global application storage, outside your project's .kiro directory. They remain associated with the chat session and do not overwrite local Steering, Specs, Hooks, or other project configuration.

Treat artifacts as session outputs rather than a substitute for source control. Save important content to your project or another durable system when it needs to follow your normal review, backup, and versioning process.

Page updated: September 11, 2026
Autopilot
Slash commands