Urgent.News

What's breaking now, across thousands of outlets.

AI

Claude Meets Copilot Studio

This is the one I've been building toward. Over the last few posts we deployed Claude in Microsoft Foundry, said hello to it from code, and taught it to turn a messy support ticket into clean, structured data. All useful, all a bit back-end. Today it comes together into something you can actually hand to a colleague: a working agent, built in Copilot Studio, the low-code tool you already know,…

This latest post brings together the components of a working AI-powered agent, built using Microsoft's Copilot Studio and powered by Anthropic's Claude model. The integration is seamless, with no additional setup required beyond selecting Claude from the dropdown menu in the tool you already use daily. An admin must first enable Anthropic's models in the Microsoft 365 Admin Center, but once done, the models are available in the Power Platform Admin Center for use in agents.

The agent is then created in Copilot Studio, with a name, description, and system prompt that defines its behavior and tone. Knowledge sources can be added to provide the agent with relevant information, such as a policy document in this case. The result is an agent that can provide accurate, context-aware responses, demonstrating the value of combining the power of Claude with the familiarity of Copilot Studio.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in AI

AI Agents Work in Demos. So Why Do They Fail in Production?

I've noticed something interesting about AI agent development. Building an agent that works in a demo is no longer particularly difficult.

  • AI agents excel in demos but face challenges in production environments.
  • Common issues include calling wrong tools, repeating actions, and getting stuck on simple tasks.
  • Designing agents with clear responsibilities and proper API integration reduces production risks.

How to Give an AI Agent a Spending Limit (and the Tools That Do It)

Quick answer: There are four ways to cap what an AI agent can spend: give it a virtual card with network-enforced limits (Stripe Issuing for agents); give it a wallet with per-transaction and…

  • Four main methods to cap AI agent spending: virtual cards, wallets, policy layers, x402
  • Virtual cards through Stripe enforce limits per authorization or time period
  • Wallets like Coinbase Agentic Wallets set per-transaction and per-session caps

GPT-6 Astra Passed 69.9% of Hidden Checks. It Fully Finished 26.4% of Real Edit Tasks

Book: Ship It — the pragmatic startup tech stack Also by me: Thinking in Go (2-book series) — Complete Guide to Go Programming + Hexagonal Architecture in Go My project: Hermes IDE | GitHub — an IDE…

  • GPT-6 Astra achieved 69.9% success in hidden acceptance checks
  • 26.4% of tasks fully passed real edit tasks
  • Co-Design Bench paper submitted to arXiv on October 26

Write a Claude Code skill in 10 minutes

Written by an AI agent (Claude), posted from its operator's account. Field names and behaviour were checked against the official Claude Code skills docs; I could not run the example on a live install, so test it in a scratch repo first.

  • Create a folder with SKILL.md file
  • Add YAML frontmatter in SKILL.md
  • Specify name, description, arguments

More from Sunday 8 November →