1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl
Chi tiết nguồn
<p>When building an AI agent, selecting a model is only the first step. The agent still needs tools, instructions for finishing the job, a way to manage context growth in long sessions, and guardrails before it executes any consequential actions, like issuing a refund.</p> <p>We are upgrading Amazon Bedrock AgentCore harness to use Strands harness, our open-source agent harness, released earlier this year, available under an Apache 2.0 license. AgentCore harness also introduces lifecycle hooks, so you can apply your own deterministic checks and notifications at defined points in the agent loop.</p> <p>With this upgrade, agents that rely on the managed defaults get a recommended model, a task-oriented system prompt, automatic prompt caching (initially for Anthropic models on Amazon Bedrock), and proactive context management. They also get additional built-in tools for planning, web retrieval, filesystem access, context offloading, and task delegation. This gives agents greater capabilities during long tasks, allowing them to keep track of subtasks, reduce context window usage, and delegate work. With hooks, you can transform non-deterministic AI behavior into predictable, safe, and governed workflows by running deterministic code at specific lifecycle checkpoints.</p> <p>There’s no new resource type or integration to adopt. You automatically get both updates in the AgentCore harness you already use.</p> <h2 id="strands-capabilities-on-aws">Strands capabilities, on AWS</h2> <p><a href="https://strandsagents.com/docs/user-guide/harness/" target="_blank" rel="noopener">Strands harness</a> provides an assembled agent foundation with recommended instructions, tools, and context management. <a href="https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/harness.html" target="_blank" rel="noopener">Amazon Bedrock AgentCore harness</a> operates that foundation as a managed AWS service. The result is a production-grade default agent that doesn’t require you to assemble and operate the harness or its infrastructure yourself.</p> <p>You do not need to provision compute, bundle and host the agent loop, manage session scaling, or operate tool-execution infrastructure. Each session runs in a secure, kernel-isolated microVM in AgentCore runtime, a capability of Amazon Bedrock AgentCore, with managed compute, scaling, and high availability.</p> <p>AgentCore achieves this by connecting the harness to the services required for production agents, including session persistence, streaming responses, usage metadata, observability, AgentCore memory, Identity, Gateway, Browser, Code Interpreter, and customer-provided containers. You retain control over the model, instructions, tools, permissions, and lifecycle policies while AgentCore manages the underlying execution environment.</p> <h2 id="a-more-capable-managed-harness">A more capable managed harness</h2> <p>Harness now provides a stronger experience when you use its managed defaults:</p> <ul> <li><strong>A current recommended model.</strong> When you omit the model, Harness uses a recommended default model that evolves as new models are released, always keeping your harnesses up to date. Explicit harness-level and per-invocation model configurations continue to take precedence.</li> <li><strong>Task-oriented instructions.</strong> The managed system prompt encourages the agent to gather relevant context, use appropriate tools, continue until the task is resolved, adapt to failures or denied actions, and verify its work before reporting completion. The default system prompt improves over time to support the latest harness behavior.</li> <li><strong>Automatic prompt caching.</strong> For supported models using Converse on Amazon Bedrock, Harness caches the system prompt, tool definitions, and conversation history. Repeated calls with the same prompt and tool surface can use lower-priced cache-read tokens, reducing input processing latency and cost.</li> <li><strong>Proactive context management.</strong> By default, Harness summarizes older conversation turns while retaining recent context once the context window reaches a configurable threshold. Keeping the context lean this way helps Harness run at <a href="https://strandsagents.com/blog/we-ran-94000-trials-to-measure-the-cost-of-harness-choice/" target="_blank" rel="noopener">about 34% lower token cost than other leading harnesses</a>.</li> <li><strong>Context offloading.</strong> Large tool results can be moved out of the immediate model context. The agent receives a preview and can retrieve the complete result when needed, reducing repeated context usage without losing access to the data.</li> <li><strong>Planning across invocations.</strong> The <code>todo_write</code> tool maintains a structured task plan that can be restored in later invocations within the same session, including after conversation summarization.</li> <li><strong>Focused delegation.</strong> The <code>subagent</code> tool delegates a self-contained task to a fresh worker and returns the result to the parent agent. The worker is internal to the invocation, not a separately managed harness resource, and shares invocation limits and your tool-call lifecycle hooks.</li> <li><strong>Web retrieval.</strong> The <code>web_fetch</code> tool retrieves content from a specified webpage to give your harness up-to-date external context.</li> <li><strong>Granular filesystem access.</strong> With separate <code>read</code>, <code>write</code>, and <code>edit</code> tools, you can grant only the granular filesystem capabilities an agent needs.</li> </ul> <p>Customer-provided Model Context Protocol (MCP) servers, AgentCore Gateway (a capability of Amazon Bedrock AgentCore), Browser, Code Interpreter, inline functions, skills, memory, and customer-provided containers continue to work through the existing harness interfaces.</p> <h2 id="recommended-by-default-configurable-when-needed">Recommended by default, configurable when needed</h2> <p>Harness