Cursor vs Kiro
A feature-by-feature comparison of Cursor and Kiro across 7 capability categories.
Modalities — Cursor Wins
| Feature | Cursor | Kiro |
|---|---|---|
Text Input | Yes. Agent chat is driven by text prompts in the input. You type instructions, attach @ context, and switch models from that same field. | Yes, requires free plan. Prompts become specs (requirements, design, tasks) then implementation. |
Image Upload / Vision | Yes. You can drag an image into chat or paste a screenshot. Agent also reads image files (.png, .jpg, .gif, .webp, .svg) for vision-capable models. | Partial. Homepage mentions multimodal inputs and Figma as context. A general image-upload vision API was not separately documented. |
Image Generation | Yes. Agent can generate images from text or reference images for UI mockups and diagrams. Files land in the project assets/ folder and show inline in chat. | No. A coding agent, not an image model. |
Voice Mode | Partial. A microphone in the chat input dictation-transcribes prompts, and iOS can dictate to agents. That is one-way voice input, not a two-way spoken conversation loop. | No. No conversational voice loop is documented. |
Video Understanding | Partial. Grok Bot accepts video attachments (up to 200 MB) so that Bot can inspect recorded footage. Core Agent chat is documented for images and files, not a general YouTube/video-watch loop, so this is not product-wide video understanding. | No. Not a video-analysis product. |
Video Generation | No. Not a video generation product. | No. Not a video generation product. |
File Upload (PDF, DOCX) | Yes. Chat @-mentions attach files and folders. Grok Bot also takes PDFs, Office docs, CSV, JSON, source, and notebooks as message attachments. | Yes, requires free plan. Works on local workspaces and, on the web, GitHub/GitLab repos in cloud sandboxes. |
Code Execution | Yes. Agent runs shell commands in the terminal, watches output, and can execute tests, linters, and builds as part of a task. | Yes, requires free plan. Agents implement, test, and can run headless in CI. Web sessions run in isolated sandboxes. |
Audio Input | Partial. Grok Bot message attachments include audio files (25 MB each) in the same table as documents and images, so pre-recorded audio can be sent for a task. Core Agent chat is not documented as a general audio-file transcribe surface, so this is Grok Bot only. | No. No audio-file input is documented. |
Canvas / Artifact Editor | Yes. The Agents Window is an agent-first workspace beside the classic IDE editor, with diffs, file search, and split layouts. Agent also opens in a Cmd+I sidepane. | Unknown. Overlapping columns disagreed (partial vs yes); left unverified rather than copying a no. |
Screen Sharing / Computer Use | Yes. Cloud Agents run a full desktop and can drive mouse/keyboard plus the browser (computer use). You can take over the remote desktop, then hand control back to the agent. | No. No computer-use desktop takeover is documented. Agents edit the workspace. |
Memory & Context — Tie
| Feature | Cursor | Kiro |
|---|---|---|
Persistent Memory | Partial. Grok Bots retain facts and summaries across work. Core Agent chat relies on Rules instead of auto-memory between completions, so this is not ChatGPT-style global memory. | Yes, requires free plan. Steering files (.kiro/steering/, ~/.kiro/steering/, AGENTS.md) persist conventions across sessions and surfaces. |
Large Context Window | Yes. Each chat has a fixed model context window with a usage ring. Cloud Agents let you pick context size; several models document up to 1M-token extended context. | Unknown. Uses multiple FMs via Bedrock/Auto. No token window is published on the pricing page. |
Custom Instructions | Yes. Project and user Rules (.cursor/rules plus User Rules) inject persistent instructions into Agent. Always Apply, glob, and @-mention rules are documented. | Yes, requires free plan. Steering markdown (always / fileMatch / manual) plus AGENTS.md. |
Conversation History | Yes. Past chats persist so you can @Chats into a new prompt. CLI resume/continue reloads prior threads; iOS keeps an agent inbox of running conversations. | Yes, requires free plan. IDE, CLI, web, and Crew keep sessions. Web sandboxes keep running after you close the laptop. |
Integrations — Cursor Wins
| Feature | Cursor | Kiro |
|---|---|---|
Web Search / Browsing | Yes. Agent has a Web tool that generates search queries and performs live web searches during a task. | Unknown. MCP can pull tools; a first-party live-web search toggle was not confirmed. |
Plugins / Extensions | Yes. Cursor Marketplace installs official plugins that bundle rules, skills, MCP servers, and hooks. Teams can ship a private marketplace; VS Code extensions still work in the editor. | Yes, requires free plan. MCP, Agent Client Protocol, Open VSX extensions, Skills.md, and 500+ CLI tools. |
API Access | Yes. Cloud Agents API, TypeScript/Python SDKs, Admin API, Analytics API, and related endpoints are documented. They run agent workflows, not a raw chat-completions API. | Partial. Headless CLI in CI/CD and ACP into other IDEs. That is not a public REST generate API. |
Zapier Integration | Unknown. No first-party Cursor Zapier app was listed on cursor.com/docs. Automations document GitHub, GitLab, Slack, Linear, and webhooks instead. | Unknown. No first-party Zapier app was checked. |
Custom GPTs / Bots | Yes. Grok Bots are named durable agents with a profile, skills, routines, and shareable templates. You create, duplicate, and share a Bot the way Custom GPTs are specialized agents. | Yes, requires free plan. Custom agents plus steering; ACP into other tools. Kiro Crew is the open-source coordinator. |
Real-time Collaboration | Partial. You can share a Cloud Agent URL with teammates (read-only unless team follow-ups are on). Grok Bot group chats exist. This is not a simultaneous multiplayer editor session. | Partial. Team billing and shared steering. Live multiplayer cursors were not documented. |
Live Social Data Integration | No. Not a live social-firehose product. | |
Live Citation Mapping | No. Not a cited-search product. |
Developer — Tie
| Feature | Cursor | Kiro |
|---|---|---|
Function Calling | Yes. Cursor connects to MCP servers that expose tools the model can execute. Agents call those functions from chat and Plan Mode, with user approval before each tool run by default. | Yes, requires free plan. Agents take actions (implement, test, hooks, MCP tools), not chat-only replies. |
Streaming Responses | Yes. iOS follows agent work live and watches the chat stream as the agent codes. The TypeScript SDK iterates streams; ACP clients handle streaming session updates. | Unknown. Token streaming is not documented as an API contract. |
Fine-Tuning | No. Public APIs run hosted agent workflows. Docs do not offer a customer fine-tune SKU for foundation weights; you pick Cursor and third-party hosted models. | No. You pick models (Auto, Claude, GPT, open-weight). No custom-weight training product. |
Embeddings API | No. Cursor APIs are agent, admin, and analytics endpoints, not a vector embeddings API for converting text into embeddings in your own app. | No. Not an embeddings API. |
Structured Output (JSON) | Unknown. ACP and SDKs exchange JSON-RPC/tool payloads, but no first-party JSON-schema guarantee for model replies was documented on the API overview. | Partial. Specs and property-based tests are structured artifacts. Not a JSON-schema chat API. |
Reasoning / Thinking Mode | Yes. The model catalog lists Thinking variants and GPT reasoning-effort options (for example gpt-5-high). The SDK exposes thinking messages and a reasoning-effort parameter. | Unknown. Overlapping columns disagreed (yes vs partial); left unverified rather than copying a no. |
Local Execution | Yes, requires free plan. IDE and Crew run on your machine; web sandboxes are cloud. Models are hosted. | |
Open Weights | Partial. You can select open-weight models (Qwen, DeepSeek, MiniMax, GLM). The Kiro product itself is not an open-weight release except Crew. | |
Multi-Agent Orchestration | Yes, requires free plan. Parallel agents implement tasks; hooks fire on IDE events; Crew coordinates tools. |
Platforms — Tie
| Feature | Cursor | Kiro |
|---|---|---|
Web App | Yes. Cursor Web at cursor.com/agents starts and manages cloud agents from a browser on any device, alongside desktop and iOS. | Yes, requires plus plan. Kiro on the web (preview) is for paid Pro+ tiers; sandboxes keep running in the cloud. |
iOS App | Yes. Native Cursor for iOS (App Store) directs cloud and local agents, reviews PRs, and streams work. Requires iOS/iPadOS 26+; listed on Start through Enterprise. | Yes, requires plus plan. Homepage: sign in on mobile with a paid account. Store listing OS split was not opened this round; Google/Apple both implied by “mobile app”. |
Android App | Partial. There is no native Android app; docs say Android is planned. Use cursor.com/agents in Chrome and Install App for a PWA. | Unknown. A mobile app is documented; Android vs iOS split was not confirmed on a store page. |
Desktop App | Yes. Cursor is a native IDE: .dmg on macOS 12+, .exe on Windows 10+, and apt/yum/AppImage on Linux. Quickstart starts with installing that desktop app. | Yes, requires free plan. Downloadable IDE for the OS; Open VSX + VS Code settings import. |
Chrome Extension | No. Documented clients are the desktop IDE, cursor.com/agents, iOS, Slack, GitHub, Linear, and the API. Agent uses a built-in IDE browser, not an official Chrome extension. | No. Not distributed as a Chrome extension. |
Privacy — Cursor Wins
| Feature | Cursor | Kiro |
|---|---|---|
GDPR Compliant | Yes. Enterprise docs link a GDPR-compliant DPA and state Cursor maintains GDPR compliance alongside SOC 2 Type II. Individual plans follow the Privacy Policy, not the DPA. | Unknown. Needs an AWS DPA read for Kiro specifically. |
Opt Out of Data Training | Yes. Privacy Mode is a settings toggle: with it on, Customer Data is not used for training by Cursor or model providers under ZDR. Teams/Enterprise can enforce it org-wide. | Unknown. Enterprise privacy is advertised; a consumer training opt-out toggle was not checked. |
Enterprise Privacy Mode | Yes, requires enterprise plan. Enterprise adds Privacy Mode enforcement, ZDR, optional CMEK, data residency, SSO/SCIM, and a DPA. Privacy Mode is on by default for Enterprise teams. | Yes, requires enterprise plan. IAM, SSO, usage dashboards, IP indemnity, GovCloud, centralized billing. |
Workspaces — Tie
| Feature | Cursor | Kiro |
|---|---|---|
Projects / Folders | Yes. You open a project folder after install. Agents Window adds multi-workspace; Agent search docs cover multi-root workspaces with per-folder context. | Yes, requires free plan. Workspace .kiro/specs and steering; Crew is a persistent local workspace. |