<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Strands on Ken Kitts</title><link>https://kenkitts.com/tags/strands/</link><description>Recent content in Strands on Ken Kitts</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 13 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://kenkitts.com/tags/strands/index.xml" rel="self" type="application/rss+xml"/><item><title>Building an Agent on Bedrock AgentCore, Part 5: Whose Notes Are These?</title><link>https://kenkitts.com/posts/bedrock-agentcore-part-5/</link><pubDate>Mon, 13 Jul 2026 00:00:00 +0000</pubDate><guid>https://kenkitts.com/posts/bedrock-agentcore-part-5/</guid><description>The agent finally learns who it&amp;#39;s talking to. Cognito JWT auth locks the gateway, an interceptor Lambda injects identity on a channel the model can&amp;#39;t touch, and DynamoDB grows a composite key.</description></item><item><title>Building an Agent on Bedrock AgentCore, Part 4: The Notes Were Always Ephemeral</title><link>https://kenkitts.com/posts/bedrock-agentcore-part-4/</link><pubDate>Tue, 30 Jun 2026 00:00:00 +0000</pubDate><guid>https://kenkitts.com/posts/bedrock-agentcore-part-4/</guid><description>For three posts the agent has saved your notes to a Python list that dies with the process. This post gives them a real home — DynamoDB behind a Lambda, served to the agent as MCP tools through an AgentCore Gateway. The agent can&amp;#39;t tell the remote tools from the local ones. That&amp;#39;s the trick, and the knife.</description></item><item><title>Building an Agent on Bedrock AgentCore, Part 3: Giving It a Memory That Outlives the Process</title><link>https://kenkitts.com/posts/bedrock-agentcore-part-3/</link><pubDate>Sat, 27 Jun 2026 00:00:00 +0000</pubDate><guid>https://kenkitts.com/posts/bedrock-agentcore-part-3/</guid><description>The agent runs in the cloud now, and it still forgets everything the instant the box recycles. This post wires it to AgentCore Memory — durable conversation that survives a cold start, then long-term memory so it remembers you across sessions. Two honest scars included, free of charge.</description></item><item><title>Building an Agent on Bedrock AgentCore, Part 1: The Loop Was Never the Hard Part</title><link>https://kenkitts.com/posts/bedrock-agentcore-part-1/</link><pubDate>Thu, 25 Jun 2026 00:00:00 +0000</pubDate><guid>https://kenkitts.com/posts/bedrock-agentcore-part-1/</guid><description>I already built an agent from scratch — a while loop and 600 lines of Python. It worked great, right up until I had to run it somewhere other than my laptop. This series is about that &amp;#39;somewhere.&amp;#39; Part 1: what AgentCore actually is, and a Strands notes agent running locally in 40 lines.</description></item><item><title>Building an Agent on Bedrock AgentCore, Part 2: Teaching It to Run Somewhere I Can Close My Laptop</title><link>https://kenkitts.com/posts/bedrock-agentcore-part-2/</link><pubDate>Thu, 25 Jun 2026 00:00:00 +0000</pubDate><guid>https://kenkitts.com/posts/bedrock-agentcore-part-2/</guid><description>In Part 1 the agent ran on my laptop, which is a great place for software to live right up until you close the lid. This post hands the exact same agent to AgentCore Runtime — one new file, no changes to the agent — and gets it running in the cloud behind a real endpoint.</description></item></channel></rss>