Amazon Bedrock

Amazon Bedrock AI

Amazon Bedrock AI

Amazon Bedrock AI

Amazon Bedrock AI

Amazon Bedrock AI

Amazon Bedrock AI

Amazon Bedrock AI

Amazon Bedrock AI

Amazon Bedrock AI

Amazon Bedrock AI

Fable 5 is open

submitted by /u/Competitive_Fly_4151 [link] [comments]

Please help me been like this for 2months

https://preview.redd.it/eslpcm8gem8h1.png?width=1145&format=png&auto=webp&s=64724fa247e8c2d793054d8b2eb288b630cd3cc5 i can't for my life find whats causing this issue, Claude Code is just stuck not generating any response Roo Code also has the same issue I'm using Bedrock Amazon submitted by /u/Cautious-Control-419 [link] [comments]

CC 2.1.176 (+4,360 tokens) and 2.1.179 (+5,328 tokens) systmem prompts

REMOVED: System Prompt: Claude in Chrome skill note — Removes the note telling the agent to invoke the claude-in-chrome skill (via the Skill tool) before using any mcpclaude-in-chrome browser tools. Agent Prompt: Coding session title generator — Adds examples to match the session's language (a Korean-session title) and to avoid refusal/error titles or an English title for a non-English session. Data: Claude API reference (all languages) — Adds refusal-fallback guidance for Fable 5, recommending the opt-in server-side fallbacks parameter (beta server-side-fallback-2026-06-01, falling back to Opus) by default so a policy decline is re-served by the fallback model inside the same call; cURL, Python, and TypeScript include runnable examples with switch-point and served-by detection, C# and Go give inline SDK snippets, and Java, PHP, and Ruby point to each SDK's examples/. Notes the parameter is rejected on the Batches API and unavailable on Amazon Bedrock, Vertex AI, and Microsoft Foundry (use the client-side middleware there). Skill: Building LLM-powered applications with Claude — Reframes refusal stop-reason handling to opt into fallbacks by default: new Fable 5 code should include the server-side fallbacks parameter so a refusal doesn't fail the request outright, tell the user it's enabled, and drop it only if they decline, with client-side middleware where server-side fallbacks aren't supported. Skill: Design sync Storybook source shape — Adds a [GRIDOVERFLOW] validation warning and a cardMode: "column" override for stories wider than a grid cell (data tables, full-width bars), plus rebuild rules noting presentation-only keys (cardMode/primaryStory) carry grades via a targeted rebuild while a viewport change re-grades and needs a full build. Skill: /design-sync package source shape — Adds a [GRIDOVERFLOW] validation warning and a cardMode: "column" override for wide components (data tables, full-width bars) that render wider than their grid cell, batching every flagged component into one targeted rebuild. Skill: Model migration guide — Adds "default to opting in" guidance for refusal fallbacks, recommending migrated and new Fable 5 code ship the server-side fallbacks opt-in from day one rather than as a later hardening step. System Prompt: Coordinator mode orchestration — Expands the concurrency guidance: launch independent workers in parallel via multiple tool calls in one message and cover multiple research angles, but don't parallelize simple tasks that are faster in a single worker loop. System Prompt: Fork usage guidelines — Updates the "when to fork" instruction to fork by passing subagenttype: "fork" instead of omitting subagenttype. System Prompt: Forked agent guidance — Explains that calling Agent with subagenttype: "fork" creates a background fork that inherits your full conversation context (rather than omitting the type), and notes that other subagent types — or omitting it — start fresh agents with no context. System Prompt: Subagent delegation examples — Updates the worked examples to pass subagenttype: "fork" when forking and clarifies that a non-fork subagenttype starts a fresh agent. System Prompt: Writing subagent prompts — Reframes the briefing note to say any agent other than a fork starts with zero context (previously "when spawning a fresh agent with a subagenttype"). Tool Description: Agent (simple usage notes) — Notes that a new Agent call starts a fresh agent except subagenttype: "fork", which inherits your context (when forking is available). Tool Description: Agent (usage notes) — Updates the fresh-agent note so a new Agent call starts a fresh agent with no memory of prior runs except subagenttype: "fork", and clarifies that a research-only agent is not aware of the user's intent because it is a fresh agent. Tool Description: Agent (when to launch subagents) — Rewrites the subagenttype guidance so "fork" forks yourself (inheriting your full conversation context and always running on your model, ignoring any model override) while any other type — or omitting it — starts a fresh agent (general-purpose by default). Tool Description: Artifact — Adds that reading an existing artifact's content is done by calling WebFetch with its URL. Tool Description: claude.ai Project — Adds file-upload support: projectinfo now lists file uploads (PDFs, images), projectread reads document-kind uploads (PDF, docx) while image and other non-document uploads return empty content with filekind set, and projectdelete deletes only text docs (file uploads are read-only via the tool and must be removed in claude.ai). Tool Description: WebFetch (concise) — Adds an exception (when the Artifact tool is enabled) that claude.ai/code/artifact/{uuid} URLs ARE fetchable via your claude.ai login and should use WebFetch, not curl, which gets the SPA shell or a Cloudflare 403. Tool Description: WebFetch private URL warning — Adds the same exception (when the Artifact tool is enabled) that claude.ai/co

How can I connect the Claude Windows app to use AWS Bedrock for coding?

Hi everyone, I'm trying to use the Claude Windows desktop app for coding tasks, but instead of using an Anthropic subscription or API key, I'd like to use my existing AWS Bedrock access and have all usage billed through AWS. Has anyone successfully set this up? A few specific questions: Can the Claude Windows app be configured to use Amazon Bedrock as the backend for coding? Is this available for individual AWS accounts, or is it only supported through enterprise-managed deployments? Do I need to use Claude Code separately, or can the desktop app itself connect to Bedrock? What are the exact setup steps on Windows (AWS credentials, IAM permissions, configuration files, etc.)? Are there any limitations compared with using Claude directly through Anthropic? If you've got this working, I'd really appreciate a step-by-step guide or links to any documentation/tutorials. submitted by /u/AdmirableStation7449 [link] [comments]

Don't be someone's dumb pipe

The enterprise AI governance race isn't about compliance. I went looking to see why these companies are actually talking this up. For the press, AI governance is a boring compliance story — audits, kill switches, making sure agents follow the rules. But if you look at the actual moves ServiceNow, Microsoft and Salesforce are making, something more interesting is happening. These companies are all facing the same nightmare. They risk becoming dumb pipes, the middleman plumbing data around while the real power stays with the LLM providers. They don't own the control plane, OpenAI and Google own the intelligence layer, AWS owns the infrastructure, and the enterprise software vendors become irrelevant billing systems in the middle. Staking a claim on the governance layer is their moat. That's not compliance. That's survival. Here's the pattern I noticed in the primary sources: The kill switch buy: ServiceNow acquired Traceloop for $80M in March 2026 — runtime observability for AI agents. The stock was at $120 on its way to $83. The market wasn't rewarding the thesis. Management bought anyway. The control plane play: ServiceNow connected AI Control Tower to Amazon Bedrock AgentCore, one governance layer over every AI agent an enterprise builds on AWS regardless of which model runs underneath. Nine partners announced integrations in ten days. Cognizant this week layered their Guardian agents on top. Three vendors, one workflow, multiple meters running simultaneously. Selling the lock before finishing the door: AI Control Tower hits general availability in August 2026. The governance layer being sold to enterprises right now isn't fully shipped. The Cognizant partnership announced this week is operationalizing a platform that hits GA in ten weeks. The chaos underneath: Bernstein flagged that Salesforce couldn't cleanly explain whether Agentforce revenue comes from stand-alone, embedded or unlimited credit tiers. NIST is still writing the AI agent security framework. The EU compliance deadline just moved to December 2027. Agents are being governed by other agents. Guardian agents watch the AI agents. Three vendors claim the control plane simultaneously. The rulebook hasn't even been written. This isn't about making AI safe. It's three companies building a moat around territory that doesn't fully exist yet — because the alternative is becoming someone else's dumb pipe. Happy to dig into the primary sources if anyone wants to nerd out on the specifics. submitted by /u/roll0ver [link] [comments]

AI agents being governed by other AI agents, nothing to see here

Who governs AI agents once they're running in production? I went looking for the answer. It's more complicated than the press releases suggest. This week Cognizant and ServiceNow announced a partnership specifically to close what they're calling the "enforcement gap" in enterprise AI governance. The Everest Group analyst quote from the press release cuts to it: "The hard part of AI governance was never writing the policy. It's enforcing it as systems learn and act." Here's what the enforcement actually looks like. In May, ServiceNow connected AI Control Tower to Amazon Bedrock AgentCore — a single governance layer over every AI agent an enterprise builds on AWS. Cognizant then deploys "Guardian agents" that monitor AI behavior in real time and enforce responsible AI principles throughout the lifecycle. Agents are being governed by other agents. Guardian agents watch the AI agents. The question the press releases don't answer: who watches the Guardian agents? The regulatory picture doesn't help. NIST issued a Request for Information in January specifically on securing AI agent systems — the federal standards body is asking industry how to manage agentic AI risk because the frameworks don't exist yet. The EU AI Act compliance deadline for high-risk AI systems just moved to December 2027. AI Control Tower doesn't hit general availability until August 2026. The enforcement layer is already being sold. The rulebook is still being written. Happy to dig into the primary sources if anyone wants specifics. submitted by /u/roll0ver [link] [comments]

All the AWS Bedrock AgentCore best practices in one Claude Code skill. So the agent doesn't scour dozens of docs or go trial-and-error

Open-source Claude Code plugin: a consolidated collection of official best practices for building AI agents on AWS, centered on Amazon Bedrock AgentCore (also Strands + Bedrock). The point: building on AgentCore normally means the agent crawls across dozens of AWS docs or figures things out by trial and error, and still trips on version-specific details (legacy `InvokeModel` over Converse, bare-string `serviceTier`, deprecated `structured_output()`, wrong prompt-cache TTL, the ARM64 runtime contract). Here the official guidance is already gathered, organized, and routed by use case, so the agent goes straight to the right approach. Every best practice carries its official source URL. It's a routing SKILL.md (use case → recommended stack → which files to open) + 20 reference files + 369 official source URLs. Built and QA'd with Claude Code multi-agent workflows, including a pass that verified 292 snippets one by one against the official docs. Repo: https://github.com/ferdinandobons/AWSBedrockAgentCoreSkill submitted by /u/Ambitious-Pie-7827 [link] [comments]

trying to see if Mythos claims are verified or not

The claims about Mythos Preview (Anthropic's unreleased Claude model) are substantially verified from multiple independent sources, though the exact CVE numbers and commit hashes for the FFmpeg vulnerability are still being disclosed through coordinated security processes. Key Verified Facts 1. OpenBSD 27-year-old vulnerability ✅ Verified What: A bug in OpenBSD's TCP SACK (Selective Acknowledgment) handling introduced around 1998[forum.devtalk] Impact: Allows an attacker to remotely crash any OpenBSD machine just by connecting to it via TCP[linkedin] Details: OpenBSD tracks SACK state as a singly linked list of holes; the vulnerability is subtle and survived 27 years of expert review[reddit] Patch: Available at openbsd/pub/Openpatches/.8/025ack.patch[reddit] 2. FFmpeg 16-year-old vulnerability ✅ Verified What: A bug in FFmpeg's H.264 decoder where a 32-bit slice counter is stored in a 16-bit lookup table, initialized to 65535[secureworld] Impact: A specially crafted frame with exactly 65,536 slices causes counter collision triggering out-of-bounds write[secureworld] Origin: Type mismatch dates to FFmpeg's 2003 H.264 commit; exploitable code path introduced in 2010 refactor[secureworld] Testing evasion: The code path was hit by automated testing tools 5 million times without flagging the bug[linkedin] Patch status: Three FFmpeg vulnerabilities found by Mythos were patched in FFmpeg 8.1[secureworld] 3. Linux kernel vulnerability chain ✅ Verified What: Mythos autonomously found and chained multiple Linux kernel vulnerabilities for privilege escalation[reddit] Impact: Escalation from ordinary user to complete root control of the machine[linkedin] Cost: Under $2,000 in tokens to create the exploit chain[linkedin] Status: Anthropic is funding the Linux Foundation to fix these vulnerabilities[linkedin] Supporting Evidence Source Type Key Confirmation Anthropic's risk report Official PDF Technical assessment of Mythos Preview released April 7, 2026 [anthropic] AI Security Institute evaluation Independent Confirmed 73% success on expert-level cyber CTF tasks [aisi.gov] Debian security tracker Official CVE-2026-40962 fixed in FFmpeg 8.1 [security-tracker.debian] Reddit/OpenBSD forum Community Patch discussion and technical details [reddit] Why This Matters This is considered "possibly the most frightening cybersecurity news in decades" because: AI found bugs that survived decades of expert audits and relentless fuzzing[agent-wars] Mythos found thousands of zero-days versus Opus 4.6's ~500[reddit] The model achieved 181 working exploits in Firefox benchmark testing[agent-wars] Access is gated/restricted due to dual-use risk[docs.aws.amazon] The FFmpeg commit should indeed be public given it's open source, and the patch is in FFmpeg 8.1. The exact commit hash is being handled through coordinated disclosure, but the vulnerability details are confirmed by multiple independent security researchers.The claims about Mythos Preview (Anthropic's unreleased Claude model) are substantially verified from multiple independent sources, though the exact CVE numbers and commit hashes for the FFmpeg vulnerability are still being disclosed through coordinated security processes.Key Verified Facts1. OpenBSD 27-year-old vulnerability ✅ VerifiedWhat: A bug in OpenBSD's TCP SACK (Selective Acknowledgment) handling introduced around 1998[forum.devtalk] Impact: Allows an attacker to remotely crash any OpenBSD machine just by connecting to it via TCP[linkedin] Details: OpenBSD tracks SACK state as a singly linked list of holes; the vulnerability is subtle and survived 27 years of expert review[reddit] Patch: Available at openbsd/pub/Openpatches/.8/025ack.patch[reddit]2. FFmpeg 16-year-old vulnerability ✅ VerifiedWhat: A bug in FFmpeg's H.264 decoder where a 32-bit slice counter is stored in a 16-bit lookup table, initialized to 65535[secureworld] Impact: A specially crafted frame with exactly 65,536 slices causes counter collision triggering out-of-bounds write[secureworld] Origin: Type mismatch dates to FFmpeg's 2003 H.264 commit; exploitable code path introduced in 2010 refactor[secureworld] Testing evasion: The code path was hit by automated testing tools 5 million times without flagging the bug[linkedin] Patch status: Three FFmpeg vulnerabilities found by Mythos were patched in FFmpeg 8.1[secureworld]3. Linux kernel vulnerability chain ✅ VerifiedWhat: Mythos autonomously found and chained multiple Linux kernel vulnerabilities for privilege escalation[reddit] Impact: Escalation from ordinary user to complete root control of the machine[linkedin] Cost: Under $2,000 in tokens to create the exploit chain[linkedin] Status: Anthropic is funding the Linux Foundation to fix these vulnerabilities[linkedin]Supporting EvidenceSource Type Key Confirmation Anthropic's risk report Official PDF Technical assessment of Mythos Preview released April 7, 2026 [anthropic] AI

Introducing dynamic workflows in Claude Code

Today we're introducing dynamic workflows in Claude Code. Claude now writes its own orchestration scripts, fans work out across tens to hundreds of parallel subagents in a single session, and verifies its own results before anything reaches you. Work you'd normally plan in quarters can finish in days. Built for the tasks a single pass can't handle: codebase-wide bug hunts, security and optimization audits, large migrations and language ports, and high-stakes work where you want adversarial agents trying to break the answer before you see it. Progress is checkpointed, so long runs survive interruption. One early example: Jarred Sumner used dynamic workflows to port Bun from Zig to Rust. Roughly 750,000 lines, 11 days from first commit to merge, 99.8% of the test suite passing. Available today in research preview on Max, Team, and Enterprise (admin-enabled) plans, plus the Claude API, Amazon Bedrock, Vertex AI, and Microsoft Foundry. Turn on auto mode and either ask Claude to create a workflow or flip on the new ultracode setting. Read more: https://claude.com/blog/introducing-dynamic-workflows-in-claude-code submitted by /u/ClaudeOfficial [link] [comments]

How to use legacy model Claude Sonnet 4

Hi everyone, I’m working on a research paper where we previously used Claude Sonnet 4 as the backbone. We now need to run additional experiments with the same model, but it has been marked as a legacy model. I tried accessing it via AWS Bedrock, but I get this error: Access denied. This model is marked as Legacy by the provider, and you have not been actively using it in the last 30 days. Please upgrade to an active model on Amazon Bedrock. Has anyone dealt with this before? Is there any way to still run this model? submitted by /u/Worried-Challenge308 [link] [comments]

Claude Desktop with API Key

Guys is there anyway (official/workaround) I can use Claude desktop but with an API key from Amazon Bedrock I have a lot of credits there and I wanna use the same anthropic models without paying the monthly subscription submitted by /u/teenwolf09 [link] [comments]

Anthropic officially launched 13+ FREE AI courses with certificates (Including Agentic AI and Claude Code!)

Just found out about this and had to share because almost nobody is talking about it yet. If you are tired of paying for AI courses or getting hit with paywalls just to get a certificate, Anthropic (the creators of Claude) quietly dropped a massive library of completely free, official training modules. Yes, they actually give you an official certificate of completion directly from Anthropic once you finish. Here is the breakdown of what is available and exactly how to get it without spending a dime. What is in the course catalog? They have split the training into a few different paths depending on what you want to do: The Big Surprise: Agentic AI & MCP: They have official courses on the Model Context Protocol (MCP). This is the cutting-edge tech used to build AI Agents that can browse your local computer, use tools, and execute tasks autonomously. Claude Code 101: Dedicated developer modules for their new command-line agent. It teaches you how to let Claude edit your codebase, run tests, and use its new "Plan Mode." API & Cloud Architecture: Deep dives into building with the Claude API, plus corporate tracks for deploying Claude securely inside Amazon Bedrock and Google Cloud Vertex AI. Everyday Productivity: If you aren't a coder, they have "Claude 101" and "AI Fluency" tracks. These teach advanced prompting, managing Projects, and using Artifacts for daily work. How to access it for free Anthropic hosts these courses on their official training academy platform (built on Skilljar). Because I can't post direct links here, here is how you find it: Search Google for "Anthropic Skilljar Academy" or "Anthropic Skilljar Catalog". Click the official link pointing to the Anthropic Skilljar domain. Sign up for a free account. You do not need to enter any credit card info. Choose your track, complete the lessons, pass the quick review quizzes, and download your certificate. Alternative Free Options If you want interactive coding environments alongside your videos, CodeSignal also has a free partnership track called "Developing Claude Agents" in Python and TypeScript that grants free certificates upon passing their labs. Go grab these before they decide to gate them behind a paywall! submitted by /u/Specialist_Engine522 [link] [comments]

SendUserFile tool for surfacing generated deliverable files to the use - what's new in CC 2.1.142 (+1,080 tokens)

NEW: Tool Description: SendUserFile — Describes the SendUserFile tool for surfacing generated deliverable files to the user, with optional captions and normal or proactive status. Agent Prompt: Coding session title generator — Wraps the session content in tags and tells the model to treat it as data, not follow links or instructions inside it, and not state inabilities. If the content is just a URL or reference, it should describe what the user is asking about (e.g. "Review Slack thread") rather than refuse. Adds a "Bad (refusal)" example. Agent Prompt: Managed Agents onboarding flow — Adds a "Console escape hatch" instruction telling the runtime code to print the session's Console URL right after sessions.create() so users can watch the session in the UI while iterating, defaulting the workspace slug to default. Agent Prompt: /rename auto-generate session name — Wraps the conversation content in tags and instructs the model to treat it as data to summarize, not instructions to follow. Data: Live documentation sources — Adds a WebFetch URL for the Amazon Bedrock documentation page, covering the AnthropicBedrockMantle client, anthropic.-prefixed model IDs, auth paths, feature availability, and regions. Data: Managed Agents core concepts — Adds a "Watch it live in Console" tip pointing at https://platform.claude.com/workspaces/{workspace}/sessions/{session.id}, with default as the fallback workspace slug, and asks generated code for locally-iterating users to include the print/console.log of that link. Skill: Create verifier skills — Swaps the hardcoded TodoWrite tool reference for one that resolves to either TaskCreate or TodoWrite depending on whether the tasks feature is enabled. Skill: Model migration guide — Adds an Amazon Bedrock model IDs section explaining that Bedrock clients use the same Messages API and breaking changes but require an anthropic. provider prefix on model IDs, with a rename table for claude-opus-4-7 and claude-haiku-4-5. Notes that code_execution_* tool versions and Task Budgets are first-party-only and should be skipped for Bedrock, and warns that the legacy InvokeModel/Converse Bedrock integration with ARN-versioned IDs is out of scope. Details: https://github.com/Piebald-AI/claude-code-system-prompts/releases/tag/v2.1.142 submitted by /u/Dramatic_Squash_3502 [link] [comments]

Claude Platform on AWS reference - what's new in CC 2.1.139 (+2,248 tokens)

NEW: Data: Claude Platform on AWS reference — Reference documentation for using the Claude Developer Platform through AWS infrastructure, including AnthropicAWS clients, required region and workspace configuration, SigV4 authentication, and short-term API keys. Agent Prompt: Conversation summarization — Adds requirement to note security-relevant instructions or constraints (sensitive files, forbidden operations, credential handling rules) and preserve them verbatim in the summary so they remain in effect after compaction. Agent Prompt: Recent Message Summarization — Same security-relevant instructions preservation requirement added to the recent-portion summarization flow. Data: Live documentation sources — Adds WebFetch URLs for Claude Platform on AWS and its required IAM actions documentation. Skill: Building LLM-powered applications with Claude — Reframes cloud-provider access so Claude Platform on AWS is treated as Anthropic-operated with same-day API parity and full Managed Agents support, while Bedrock, Vertex, and Foundry remain Claude API + tool use only. Skill: Dynamic pacing loop execution — Reorders steps so the brief confirmation (task ran, monitor as wake signal, fallback delay choice) is written as text before the schedule-wakeup call ends the turn. Skill: /insights report output — Removes the trailing additional-message block from the shareable report response. Skill: /loop self-pacing mode — Same reordering as dynamic pacing loop: confirm self-pacing, monitor wake signal, and fallback delay as text before the schedule-wakeup call. Skill: Model migration guide — Adds a Claude Platform on AWS section noting it uses bare first-party model IDs and that the full rename table and breaking-change sections apply verbatim, distinct from Bedrock. System Prompt: Auto mode — Drops the "Auto Mode Active" header and reframes destructive-action guidance generically rather than auto-mode-specific. System Prompt: Harness instructions — Removes the standalone note that automatic context compaction will trigger when conversations grow long. System Prompt: Memory instructions — Replaces 3–4 word titles with short kebab-case slugs, nests type under a metadata block, and introduces [[their-name]] cross-links between related memories. System Prompt: Partial compaction instructions — Adds the same security-relevant instructions preservation requirement so sensitive-file rules, forbidden operations, and credential handling carry across partial compactions. System Reminder: Output style active — Lets an output style supply its own per-turn reminder text, falling back to the default "follow the specific guidelines" wording. System Reminder: Task tools reminder — Removes the instruction telling Claude to never mention the reminder to the user. System Reminder: TodoWrite reminder — Removes the instruction telling Claude to never mention the reminder to the user. Tool Description: PowerShell — Adds a substantial reference table mapping Unix commands (head, tail, which, touch, wc, mkdir -p, rm -rf, ln -s, chmod, 2>/dev/null, inline VAR=x, bash control flow) to their PowerShell equivalents, and clarifies that -ErrorAction SilentlyContinue still causes exit 1 unless promoted to terminating and caught. Details: https://github.com/Piebald-AI/claude-code-system-prompts/releases/tag/v2.1.139 submitted by /u/Dramatic_Squash_3502 [link] [comments]

The Claude Platform on AWS is now generally available.

AWS customers get the full set of Claude API features, with AWS authentication, billing, and commitment retirement. Build and deploy agents at scale with Claude Managed Agents, or use features like the advisor strategy, code execution, web search, web fetch, the Files API, MCP connector, prompt caching, citations, and batch processing. Anthropic operates the service, and all new features ship the same day they go live on the native Claude API. Claude also remains available on Amazon Bedrock, where AWS is the data processor. This is a good fit for teams with strict regional data residency requirements or that need data processed exclusively within AWS infrastructure. Read more: https://claude.com/blog/claude-platform-on-aws submitted by /u/ClaudeOfficial [link] [comments]