--- title: AgentCore Harness + Strands vs Amazon Quick: Chat Agents, Flows, and Automate (August 2026) description: Do not pick AgentCore vs Quick. Pick the surface. Agent Skills are official on Harness and Strands, not Chat Agents. August 2026 list price: 500-employee Quick Professional ~$10,250/mo vs ~$791 AgentCore at 50K sessions. url: https://www.factualminds.com/blog/agentcore-harness-strands-vs-amazon-quick-chat-agents-flows-2026/ datePublished: 2026-08-14T00:00:00.000Z dateModified: 2026-08-14T00:00:00.000Z author: palaniappan-p category: Generative AI tags: agentcore, strands, amazon-quick, amazon-quick-suite, bedrock, ai-agents, agent-skills --- # AgentCore Harness + Strands vs Amazon Quick: Chat Agents, Flows, and Automate (August 2026) > Do not pick AgentCore vs Quick. Pick the surface. Agent Skills are official on Harness and Strands, not Chat Agents. August 2026 list price: 500-employee Quick Professional ~$10,250/mo vs ~$791 AgentCore at 50K sessions. import { Image } from 'astro:assets'; import fiveLanes from '~/assets/images/blog/agentcore-harness-strands-vs-amazon-quick-five-lanes-2026.webp'; > **AWS lifecycle notice (June 30, 2026)** — Amazon Bedrock Agents Classic and Amazon Q Business are in maintenance for new customers after **July 30, 2026**. Net-new custom agents should use [Bedrock AgentCore](/blog/amazon-bedrock-agentcore-production/). Net-new workforce AI should use [Amazon Quick Suite](/services/amazon-quick-suite/). Full matrix: [lifecycle roundup](/blog/aws-service-lifecycle-updates-june-2026/). **On August 14, 2026**, the procurement question is no longer “AgentCore or Quick.” AgentCore **Harness** has been generally available since **June 17, 2026** ([What's New](https://aws.amazon.com/about-aws/whats-new/2026/06/amazon-bedrock-agentcore-harness-generally-available/), [Harness skills](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/harness-skills.html)). **Strands Agents 1.0** already ships Graph, Swarm, Workflow, and an official [AgentSkills](https://strandsagents.com/docs/user-guide/concepts/plugins/skills/index.md) plugin. Amazon Quick splits the employee side into **Chat Agents**, **Flows**, and **Automate** ([Flows](https://docs.aws.amazon.com/quick/latest/userguide/using-amazon-quick-flows.html), [Automate vs Flows](https://docs.aws.amazon.com/quick/latest/userguide/using-amazon-quick-automations.html)). Pick the **surface**, not the brand name. This post is the five-lane comparison. It is **not** a rewrite of the [July 2026 platform TCO guide](/blog/aws-bedrock-agentcore-vs-amazon-q-enterprise-decision-guide-2026/) (workforce assistant vs custom agent infra) or the [August Harness ship map](/blog/production-ai-agents-aws-agentcore-harness-strands-2026/). Those still stand. What they do not answer: whether Agent Skills are official on Quick, whether a Flow can hold a conversation, and what 500 employee seats cost on the **August** Quick price list. > **First-party signals we reuse (not new client invoices)** — Gateway server-side tools cut median tool round-trip **~180 ms → ~95 ms** on a **B2B CRM assistant** (12 tools, ~8k turns/day) — [Gateway post](/blog/amazon-bedrock-agentcore-gateway-server-side-tool-execution-2026/). Support-style AgentCore at **50K sessions/mo ~$791/mo** platform + model — [July TCO worksheet](https://www.factualminds.com/examples/architecture-blog-2026/agentcore-vs-amazon-q/tco-worksheet.csv). August Quick **list-price** remodel of the same 500-employee silhouette: Professional **~$10,250/mo** — [`tco-scenarios.csv`](https://www.factualminds.com/examples/architecture-blog-2026/agentcore-harness-strands-vs-quick/tco-scenarios.csv). > **Reproduce this** — Copy [`examples/architecture-blog-2026/agentcore-harness-strands-vs-quick/`](https://www.factualminds.com/examples/architecture-blog-2026/agentcore-harness-strands-vs-quick/README.md) into the RFC. Fill seat counts in [`tco-scenarios.csv`](https://www.factualminds.com/examples/architecture-blog-2026/agentcore-harness-strands-vs-quick/tco-scenarios.csv). Route with [`decision-matrix.md`](https://www.factualminds.com/examples/architecture-blog-2026/agentcore-harness-strands-vs-quick/decision-matrix.md). Confirm live rates on [Quick pricing](https://aws.amazon.com/quick/pricing/) and the [AgentCore calculator](/tools/amazon-bedrock-agentcore-pricing-calculator/). **Opinionated take:** Quick Chat Agents and Flows win time-to-value and ACL connectors for employees. You give up [AgentSkills.io](https://agentskills.io/specification) portability and customer-facing APIs. Harness wins the first production product or ops agent that must load AWS procedures. Strands on Runtime wins the day config cannot express hop caps. Automate is Enterprise-only unattended process work — not a Strands substitute. ## History: how five names landed on one RFC | Date | What shipped | Who breaks without the date | | ------------------------------------ | ----------------------------------------------------------------------------------- | -------------------------------------------------------------------------- | | **13 Oct 2025** | AgentCore GA — Runtime, Memory, Gateway, Identity, Observability | Teams still quoting “Bedrock Agents” as the only AWS agent SKU | | **Oct 2025** | Amazon Quick Suite GA (Q Business + QuickSight lineage) | Buyers treating QuickSight Q and Q Business as the 2026 default | | **17 Jun 2026** | AgentCore **Harness** GA, including first-class Skills (`awsSkills`, Git, S3, path) | Teams hand-rolling session stores and pasting runbooks into system prompts | | **Strands 1.0** (Summit season 2026) | Agents-as-Tools, Graph, Swarm, Workflow, A2A, **AgentSkills** plugin | Harness-only designs that need a DAG this quarter | | **30 Jun / 30 Jul 2026** | Q Business and Bedrock Agents Classic maintenance for new customers | Net-new Classic or Q Business POCs | If you only remember one line from the [Quick Suite history post](/blog/amazon-quick-suite-history-q-business-kendra-migration-2026/): **Quick** is the workforce workspace. **AgentCore** is how you run agents you own. The rest of this page is which _surface_ inside those two brands. ## Five surfaces (stop collapsing the names) Five labeled lanes: Harness, Strands, Chat, Flows, and Automate _Harness and Strands load Agent Skills. Chat, Flows, and Automate do not. Diagram is a label aid, not an AWS architecture icon set._ | Surface | What it is | You own | AWS owns | | ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- | ------------------------------------ | | **Quick Chat Agents** | Persona + Spaces + action connectors in the Quick UI ([working with agents](https://docs.aws.amazon.com/quick/latest/userguide/working-with-agents.html)) | Instructions, sharing, blocked-word guardrails | Index, ACL inheritance, chat UX | | **Quick Flows** | No-code step graph; generate from chat or the visual editor | Flow design, who can run it | Editor, connectors, agent-hour meter | | **Quick Automate** | Unattended multi-step automations — **Enterprise plan only** | Process docs, HITL, deploy | Automation runtime | | **AgentCore Harness** | Config-driven loop **on** Runtime | Model, tools, Memory, skill sources | Orchestration, streaming, session VM | | **Strands on Runtime** | Code-first SDK (Agents-as-Tools, Graph, Swarm, Workflow) | Container, topology, evals | Isolation, Identity, Gateway, traces | **Quick Flows vs Automate** (AWS’s own split): Flows are personal/team, user-run, shorter tasks. Automate is centralized, can run without a user, long-running, extra control-flow and custom code — and it is **not** on Professional ([choosing Flows vs Automate](https://docs.aws.amazon.com/quick/latest/userguide/using-amazon-quick-automations.html)). **Harness vs Strands:** treat Harness as the paved road for the first production agent. Treat Runtime + Strands as the paved road once topology, hop caps, or A2A show up. Export Harness; do not rebuild IAM, Memory, or Gateway. That graduation is the [ship map](/blog/production-ai-agents-aws-agentcore-harness-strands-2026/). ## Agent Skills: official on Harness and Strands, not on Quick This is the lock-in tell the July platform guide did not cover. Agent Skills are bundles of markdown and scripts in the [AgentSkills.io](https://agentskills.io/specification) shape: a `SKILL.md` with YAML frontmatter, optional `scripts/` and `references/`. Metadata is injected up front (~100 tokens); the full body loads on demand. That is **progressive disclosure**. | Capability | Harness | Strands | Chat Agents | Flows | Automate | | ------------------------- | ----------------------------------------------------------- | ----------------------------------------------------- | -------------------------------------------------------------------------- | ---------------------------------- | ------------------------------------ | | AgentSkills.io `SKILL.md` | **Official** — `awsSkills`, Git, S3, path | **Official** plugin `AgentSkills` / `Skill.from_file` | No | No | No | | AWS Agent Toolkit catalog | `awsSkills` glob (`core-skills/*`, ops, storage, analytics) | Same packs from disk or Git if you wire them | N/A | N/A | N/A | | Progressive disclosure | Yes | Yes | Instructions always in the persona | Step prompts | Process-doc plan | | Per-invoke override | Yes (`InvokeHarness`) | Plugin / code config | No | No | No | | Closest Quick equivalent | — | — | Custom instructions + Spaces + action connectors + uploaded reference docs | Chat-agent step is **single-turn** | Upload process docs → generated plan | Full table with source URLs: [`skills-support-matrix.md`](https://www.factualminds.com/examples/architecture-blog-2026/agentcore-harness-strands-vs-quick/skills-support-matrix.md). The [AWS Agent Toolkit](/blog/aws-agent-toolkit-for-aws-skills-guide/) is the catalog Harness `awsSkills` is built to consume. Assumes AWS CLI v2, a Harness execution role, and a [supported region](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/agentcore-regions.html). Empty `awsSkills` object enables the curated bundle; glob `paths` if you want a subset. ```bash # Enable AWS-curated skills on a harness (control plane) aws bedrock-agentcore-control create-harness \ --harness-name ops-assistant \ --execution-role-arn "${ROLE_ARN}" \ --skills '[{"awsSkills":{"paths":["core-skills/*","specialized-skills/operations-skills/*"]}}]' ``` ```python # Per-invoke overlay — invoke-time skill with the same name wins # boto3 with bedrock-agentcore client; pin the SDK your account documents response = client.invoke_harness( harnessArn=HARNESS_ARN, runtimeSessionId=SESSION_ID, # >= 33 characters skills=[{"awsSkills": {"paths": ["core-skills/aws-cdk"]}}], messages=[{"role": "user", "content": [{"text": "Draft a CDK stack for a Lambda function."}]}], ) ``` **Do not port `SKILL.md` packs into Quick instructions.** That drop loses globs, Git pins, and on-demand loading. If the team already maintains skills, the surface is Harness or Strands. If they do not, and the users are employees asking SharePoint, Quick instructions are the right artifact — just do not call them skills. ## Cost: July worksheet vs August list price One worked example (the standard allows one silhouette for math): **500 employees** on Quick vs **one 50K-session/month product agent** on AgentCore. | Row | What it is | Monthly | | --------------------------------- | --------------------------------------------------------------------------------------------------------------------- | ------------ | | **A-jul-2026** (historical) | 400 Lite ($3) + 100 Pro ($20) + 2 Enterprise Index units @ $0.264/hr | **~$3,580** | | **A-aug-pro** (list, 14 Aug 2026) | 500 × Professional **$20** + **$250** account infra; assume no index or agent-hour overage; **Automate not included** | **~$10,250** | | **A-aug-ent** | Same 500 on Enterprise **$40** because you need Automate | **~$20,250** | | **C** (published AgentCore) | 50K support-style sessions; Runtime + Memory + Gateway + Haiku-like tokens | **~$791** | | **H** (hybrid sketch) | 100 Professional seats + the same 50K-session agent | **~$3,041** | Sources: [Quick pricing](https://aws.amazon.com/quick/pricing/) fetched **14 August 2026** (Professional $20, Enterprise $40, $250/account infrastructure, included agent hours Pro 2+2 / Ent 4+4, overage **$3**/agent-hour and **$6**/research-hour, index 25 GB / 50 GB pooled per user then **$5**/GB-month). AgentCore row **C** is reused from the [July worksheet](https://www.factualminds.com/examples/architecture-blog-2026/agentcore-vs-amazon-q/tco-worksheet.csv), not re-benchmarked. Plug your seats into [`tco-scenarios.csv`](https://www.factualminds.com/examples/architecture-blog-2026/agentcore-harness-strands-vs-quick/tco-scenarios.csv). **Honest gap:** we do not have a published Quick Automate client invoice. The Enterprise row is list price on the same 500-employee shape, labeled as such. **What changed vs July:** Lite **$3** and index **$/hour** are the wrong quote for a net-new AWS-account Quick buy in August. Professional is the floor for custom Chat Agents and Flows on that page. Automate is the reason you pay $40. Agent hours are the silent overage — Research, Flows, Automate, desktop, and custom apps meter to the second after the included pool. **AgentCore bill shape** is unchanged: Harness rides Runtime-shaped vCPU/GB-hour + Memory events + optional Gateway/Browser/Code Interpreter + Bedrock tokens. Skills fetch is not a separate SKU. Browser left on still dominates — see the 12-component [pricing post](/blog/amazon-bedrock-agentcore-pricing-12-components/) and the [calculator](/tools/amazon-bedrock-agentcore-pricing-calculator/). Direction of the July result still holds and the gap **widened** for “give every employee a seat” vs “meter a product agent.” Right-size seats (row **H**) before you declare Quick too expensive. ## Feature updates that change the choice Each bullet is who breaks, not a feature list. - **Harness GA + Skills (17 Jun 2026).** Teams still copying runbooks into a 4k-token system prompt. Turn on `awsSkills` or a Git pin instead. - **Strands 1.0 Graph / Swarm / A2A.** Harness config cannot express hop caps. Export; do not wait for a checkbox. - **Quick Chat Agents / Flows / Automate split.** Automate is Enterprise-gated. A Professional quote that “includes automations” is a Flows quote unless you said $40. - **Flows chat-agent step is single-turn** ([AI response steps](https://docs.aws.amazon.com/quick/latest/userguide/ai-response-steps.html)). Multi-turn interviews in a Flow fail UAT. Stay in Chat or move to Harness. - **Agents Classic / Q Business maintenance (30 Jul 2026).** Net-new Classic is the wrong default. Existing tenants keep running. ## Three implementation shapes (choose, don’t tour) ### 1. Customer storefront — Strands on Runtime The [eCommerce AgentCore sample](/blog/ecommerce-ai-agents-amazon-bedrock-agentcore-2026/) is a supervisor plus four specialists, eight Gateway tools, Cedar on refunds and cancels. That is a **product API** with Policy-gated writes. Quick Chat Agents cannot be the shopper storefront: no white-label session contract, no Cedar on Gateway, seat math does not fit anonymous volume. **Choose Strands (Runtime).** Do not start on Harness if you already know you need Agents-as-Tools and hop caps. Do not start on Quick. ### 2. Internal HR / IT helpdesk — Chat Agents + Flows AWS’s public [employee onboarding chat agent](https://aws.amazon.com/blogs/machine-learning/build-ai-powered-employee-onboarding-agents-with-amazon-quick/) pattern is the right _shape_: Spaces for the handbook, action connectors for tickets, share with a group. Our July FAQ still holds: if the goal is permission-aware answers over ServiceNow, Confluence, and SharePoint in 30–60 days and you have no agent engineering team, **AgentCore is over-engineering**. Add **Flows** for the repeating “open the ticket, draft the reply, post to Slack” path. Stay on Professional unless the process must run unattended. **Choose Chat Agents + Flows.** Move a write-back that Flows cannot express to Harness — not the whole helpdesk. ### 3. Ops assistant that must follow AWS runbooks — Harness + `awsSkills` If the agent’s job is “how do we handle an ECS service stuck in DRAINING” against _your_ runbooks **and** AWS-recommended procedures, that is the [AWS Agent Toolkit](/blog/aws-agent-toolkit-for-aws-skills-guide/) plus Harness `core-skills/*` and `specialized-skills/operations-skills/*`. Quick instructions are not a substitute for the catalog. > **From a real engagement** — A B2B CRM assistant, 12 Gateway tools, ~8k turns/day. Moving tool execution server-side on AgentCore Gateway cut median tool round-trip **~180 ms → ~95 ms**. That latency budget is why we will not put the same tool chain behind a Quick action connector and call it done. Detail: [Gateway server-side tools](/blog/amazon-bedrock-agentcore-gateway-server-side-tool-execution-2026/). > **What broke** — Support-bot pilots on AgentCore. Browser stayed enabled on conversational turns that only needed Gateway tools. Platform compute landed at roughly **3×** a Runtime-shaped session. Detected on the vCPU/GB-hour line, not in eval scores (the answers still looked fine). Recovery: default Browser and Code Interpreter **off**; enable per skill or per intent. Same warning is in the [Harness ship-map FAQ](/blog/production-ai-agents-aws-agentcore-harness-strands-2026/). ## When to choose (five questions) Answer in order. Full RFC copy: [`decision-matrix.md`](https://www.factualminds.com/examples/architecture-blog-2026/agentcore-harness-strands-vs-quick/decision-matrix.md). 1. **Employees + SSO + ACL chat?** → Quick **Chat Agents**. 2. **Customer or product API?** → AgentCore **Harness** (or Strands if topology is already known). 3. **Existing `SKILL.md` packs?** → Harness or Strands. Quick cannot consume them. 4. **Graph, Swarm, hop caps?** → **Strands on Runtime**. Export Harness; keep Gateway and Memory. 5. **Must run with no user at the keyboard?** → Quick **Automate** (Enterprise) **or** AgentCore if it is a product/ops API you version in Git. Hybrid is the enterprise default: Quick for the workforce, AgentCore for the product. Shared Identity Center, separate evals, separate cost alarms. ## What to Do This Week 1. Write one sentence: which **surface** this RFC is buying. Not “we will evaluate AgentCore and Quick.” 2. Copy [`monday-checklist.md`](https://www.factualminds.com/examples/architecture-blog-2026/agentcore-harness-strands-vs-quick/monday-checklist.md) into the ticket. 3. Remodel seats on **August** Quick list prices in [`tco-scenarios.csv`](https://www.factualminds.com/examples/architecture-blog-2026/agentcore-harness-strands-vs-quick/tco-scenarios.csv). Do not paste the July **~$3,580** into a 2026-Q3 budget. 4. Inventory `SKILL.md` repos. If any exist, attach them on Harness or Strands this week — do not paste into a Quick persona. 5. If the agent is a product API, stand up **one** Harness in non-prod and cap Browser. If it is employee Q&A, create **one** custom Chat Agent against one Space. 6. Need a two-week surface-choice review (Quick employees + AgentCore product)? [Book it](/contact-us/) or start from [Generative AI on AWS](/services/generative-ai-on-aws/). ## What This Post Doesn't Cover - **Kiro / Amazon Q Developer** — IDE coding assistants; they compete with Copilot, not Harness. See the July guide’s Q Developer FAQ. - **Bedrock Agents Classic migration runbooks** — inventory tools and sessions; not a one-day flip. Use the [production AgentCore guide](/blog/amazon-bedrock-agentcore-production/). - **LangGraph / CrewAI on Runtime** — keep them if you already have a graph you will not rewrite this quarter. They are not the greenfield default next to Strands 1.0. - **A new Quick Automate client bill** — we do not have one published. Enterprise list price is modeled, not measured. - **AWS Context** — still Coming soon as of the [Harness ship map](/blog/production-ai-agents-aws-agentcore-harness-strands-2026/); do not sequence grounding behind it. - **HIPAA/PCI control maps** — both lineages can sit under a BAA; that is a separate engagement, not a SKU picker. --- Need the RFC filled in with your seat count and tool inventory? Start with [Amazon Quick Suite consulting](/services/amazon-quick-suite/) or [contact us](/contact-us/). ## FAQ ### When should I NOT start on AgentCore Harness? Skip Harness when the users are employees who need permission-aware answers over SharePoint, Confluence, or Salesforce and you have no agent engineering team — that is Quick Chat Agents. Also skip Harness when you already need Graph, Swarm, hop caps, or Agents-as-Tools this quarter; start on Strands on Runtime instead of hoping config will grow into a DAG. ### When should I NOT use Quick Chat Agents or Flows for a customer-facing bot? Quick is an employee workspace with SSO and ACL inheritance. External storefront chat, white-label UX, Gateway Policy on refunds, and session economics at tens of thousands of anonymous turns belong on AgentCore. Embedding Quick on a public product page is the failure mode the July 2026 platform guide already flagged. ### What could go wrong if we treat Quick instructions as Agent Skills? You lose progressive disclosure, Git pins, awsSkills globs, and per-invoke overrides. A SKILL.md pack from the AWS Agent Toolkit will not load in Chat Agents. Pasting the markdown into a persona is a different artifact — it bloats every turn and cannot be versioned the way Harness Git/S3 sources can. ### What could go wrong if a Flow chat-agent step is expected to hold a conversation? AWS documents the chat-agent step as a single-turn interaction. The agent answers the instructed task; it does not support back-and-forth inside that step. Multi-turn belongs in Quick chat or on Harness/Strands. Teams that design RFP Flows as interviews hit this on the first UAT. ### Does Quick Automate replace Strands for multi-step workflows? No. Automate is unattended, Enterprise-plan ($40/user/month) process automation with HITL and an actions library — for invoice, vendor, and similar org-owned runs. Strands is code-first topology (Graph, Swarm, Agents-as-Tools) on AgentCore Runtime for product and ops APIs you version in Git. Same English word “workflow,” different buyers. ### Is the July 2026 ~$3,580 Quick TCO still the list-price answer? No. That figure used Q Business-shaped Lite $3 / Pro $20 plus Enterprise Index hours. On 14 August 2026, AWS-account Quick list price is Professional $20 / Enterprise $40 per user, plus $250/account infrastructure, plus agent-hour overage. The same 500-employee silhouette remodeled on Professional is ~$10,250/mo before overage. Keep the July row as history; quote August rates from aws.amazon.com/quick/pricing/. ### Can we run Quick for employees and Harness for the product? Yes — that is the default at scale. Quick Chat Agents and Flows for SSO users; Harness or Strands for the customer API. Shared IAM Identity Center, separate evals and cost alarms. Do not merge the two into one Runtime “so we only have one platform.” ### Should net-new builds still use Bedrock Agents Classic or Amazon Q Business? No. Both enter maintenance for new customers after 30 July 2026. Net-new workforce AI starts on Quick Suite. Net-new custom agents start on AgentCore Harness or Runtime. Existing tenants keep running; inventory tools and indexes before a cutover, do not flip in a day. --- *Source: https://www.factualminds.com/blog/agentcore-harness-strands-vs-amazon-quick-chat-agents-flows-2026/*