Ai Change Desk

AI Change Desk | EP026: Agent Toolchain Ownership Check

AI agents are moving from chat windows into toolchains: managed execution environments, SDKs, MCP servers, mobile approvals, workspace integrations, search agents, shopping agents, and enterprise platforms. This episode translates the week of announcements into one operator question: who owns the toolchain when the agent starts acting? * Google I/O 2026 pushed agentic Gemini deeper into developer tools, Search, Workspace, shopping, app development, and personal agent surfaces. * Anthropic announced it is acquiring Stainless, an SDK and MCP server tooling company that has generated official Anthropic SDKs. * Anthropic and KPMG announced a global alliance to embed Claude into KPMG Digital Gateway and make Claude available to more than 276,000 employees. * OpenAI Codex mobile and ChatGPT personal finance remain active control signals from the prior week: approvals and sensitive data context are moving closer to always-on workflows. Do not treat agent access as a one-time tool approval. Treat it as a toolchain lifecycle: owner, connector, permission boundary, evidence, fallback, and shutdown authority. By Wednesday, May 27, 2026, complete one agent-toolchain ownership review for your highest-impact AI workflow. Fields to capture: workflow name, agent surface, SDK/API/tool dependencies, connector owner, permission boundary, human approval point, evidence trail, fallback route, shutdown owner, and next review date. * Anthropic: Anthropic acquires Stainless — https://www.anthropic.com/news/anthropic-acquires-stainless [https://www.anthropic.com/news/anthropic-acquires-stainless] * Anthropic: KPMG integrates Claude across its core business and workforce of more than 276,000 — https://www.anthropic.com/news/anthropic-kpmg [https://www.anthropic.com/news/anthropic-kpmg] * Google: I/O 2026 collection — https://blog.google/innovation-and-ai/technology/developers-tools/google-io-2026-collection/ [https://blog.google/innovation-and-ai/technology/developers-tools/google-io-2026-collection/] * Google: I/O 2026 developer highlights — https://blog.google/innovation-and-ai/technology/developers-tools/google-io-2026-developer-highlights/ [https://blog.google/innovation-and-ai/technology/developers-tools/google-io-2026-developer-highlights/] * Google: I/O 2026 opening keynote — https://blog.google/innovation-and-ai/sundar-pichai-io-2026/ [https://blog.google/innovation-and-ai/sundar-pichai-io-2026/] * OpenAI: Work with Codex from anywhere — https://openai.com/index/work-with-codex-from-anywhere/ [https://openai.com/index/work-with-codex-from-anywhere/] * OpenAI: ChatGPT release notes — https://help.openai.com/en/articles/6825453-chatgpt-release-notes [https://help.openai.com/en/articles/6825453-chatgpt-release-notes] AI-assisted tools were used in parts of the research and production workflow. Final editorial judgment, risk posture, and release approval stayed human-led. This is operational guidance, not legal advice. These are Michael's opinions and are not representative of any organization.

AI Change Desk | EP025: Away-Mode Control Check

Michael is back after a week away handling personal things and camping by the beach with family and dogs. The timing created the perfect operating question: while people are away from the desk, AI work keeps moving. This episode turns fresh AI workflow-surface announcements into a practical control check for operators. The core issue is not whether teams can work from anywhere. They already can. The issue is whether the organization knows what can move, what must wait, what creates evidence, and who can stop a workflow when the normal owner is offline. * OpenAI Codex moving into mobile and remote task oversight. * OpenAI personal finance in ChatGPT as a signal for sensitive connected-account workflows. * Google Gemini Intelligence across Android devices and browser contexts. * Anthropic and PwC expanding Claude deployment across professional workflows. * OpenAI launching The OpenAI Deployment Company as a deployment-layer signal. Run a 45-minute Away-Mode Control Check on one live AI workflow: 1. Map which surfaces can trigger it. 2. Classify the action state it can reach. 3. Define what happens when the owner is away. 4. Confirm what evidence is created. 5. Identify the data class touched. 6. Set final-confirmation rules. 7. Name who can stop it. * OpenAI, “Work with Codex from anywhere,” May 14, 2026. * OpenAI, “Simplify your personal finances with ChatGPT,” May 15, 2026. * Google, “A smarter, more proactive Android with Gemini Intelligence,” May 12, 2026. * Anthropic, “Expanding our partnership with PwC,” May 14, 2026. * OpenAI, “OpenAI launches The OpenAI Deployment Company,” May 11, 2026. AI-assisted tools were used in parts of the research and production workflow. Final editorial judgment, risk posture, and release approval stayed human-led. This is operational guidance, not legal advice. These are Michael’s opinions and are not representative of any organization.

AI Change Desk | EP024: Delegation Quality Check

Episode date: 2026-05-06 Format: Wednesday brief Runtime target: 9-12 minutes Agents are moving from answering questions to taking assignments. This episode connects Microsoft Copilot Cowork, Microsoft Agent 365, and Anthropic's financial-services agent templates into one operating question: when AI does the assignment, who owns the review? * Delegation is becoming embedded inside everyday work surfaces, not just chat windows. * Agent control planes help with inventory and governance, but dashboards do not replace workflow ownership. * Vertical agents in finance make review, source lineage, evidence, and fallback ownership more urgent. * Useful output is not the same as ready output. By Wednesday, May 13, 2026, run a 30-minute delegation-quality review for one AI-assisted workflow. Capture the task, approved users, sources, output artifact, reviewer, evidence, fallback owner, stop condition, and user message. * Microsoft: Copilot Cowork: From conversation to action across skills, integrations, and devices - https://www.microsoft.com/en-us/microsoft-365/blog/2026/05/05/copilot-cowork-from-conversation-to-action-across-skills-integrations-and-devices/ [https://www.microsoft.com/en-us/microsoft-365/blog/2026/05/05/copilot-cowork-from-conversation-to-action-across-skills-integrations-and-devices/] * Microsoft: Microsoft Agent 365, now generally available, expands capabilities and integrations - https://www.microsoft.com/en-us/security/blog/2026/05/01/microsoft-agent-365-now-generally-available-expands-capabilities-and-integrations/ [https://www.microsoft.com/en-us/security/blog/2026/05/01/microsoft-agent-365-now-generally-available-expands-capabilities-and-integrations/] * Anthropic: Agents for financial services - https://www.anthropic.com/news/finance-agents [https://www.anthropic.com/news/finance-agents] * Microsoft: Microsoft 365 Copilot, human agency, and the opportunity for every organization - https://www.microsoft.com/en-us/microsoft-365/blog/2026/05/05/microsoft-365-copilot-human-agency-and-the-opportunity-for-every-organization/ [https://www.microsoft.com/en-us/microsoft-365/blog/2026/05/05/microsoft-365-copilot-human-agency-and-the-opportunity-for-every-organization/]

AI Change Desk | EP023: Trust Boundary Check

Advanced Account Security, OpenAI on Amazon Bedrock, FedRAMP availability, partnership changes, and the May 8 macOS remediation deadline all point to one Monday operating question: when AI becomes infrastructure, who owns the trust boundary across identity, cloud channel, compliance scope, endpoint evidence, and agent logging? * OpenAI introduced Advanced Account Security for ChatGPT accounts, with Codex coverage through the same login. * Amazon Bedrock added OpenAI models, Codex, and Managed Agents powered by OpenAI in limited preview. * OpenAI and Microsoft updated their partnership terms, changing the cloud-channel dependency map. * OpenAI announced FedRAMP 20x Moderate authorization for ChatGPT Enterprise and API Platform. * OpenAI's macOS app remediation deadline remains May 8, 2026. AI approval is no longer just tool approval. Teams need evidence that account access, cloud channel, data scope, endpoint/client trust, and audit ownership all line up with the work people are actually doing. Before scaling an AI workflow, answer five questions: 1. Which account boundary carries the work, and is phishing-resistant authentication required? 2. Which cloud channel carries the work: direct provider, Azure, Amazon Bedrock, FedRAMP environment, pilot, or blocked? 3. Which data class is allowed on that channel? 4. Which endpoint/client requirement must hold before use? 5. Where is the evidence, and who owns the exception path? Run a 45-minute trust-boundary check across the top five AI workflows people are using or requesting this week. For each workflow, map account, channel, data, endpoint, evidence owner, and exception owner. Then send one plain-language memo: what is approved, what is limited preview, what needs evidence, what is blocked, and who approves exceptions. * OpenAI, Introducing Advanced Account Security: https://openai.com/index/advanced-account-security/ [https://openai.com/index/advanced-account-security/] * AWS, Amazon Bedrock now offers OpenAI models, Codex, and Managed Agents: https://aws.amazon.com/about-aws/whats-new/2026/04/bedrock-openai-models-codex-managed-agents/ [https://aws.amazon.com/about-aws/whats-new/2026/04/bedrock-openai-models-codex-managed-agents/] * Amazon, OpenAI Models on Amazon Bedrock: https://www.aboutamazon.com/news/aws/bedrock-openai-models [https://www.aboutamazon.com/news/aws/bedrock-openai-models] * OpenAI, The next phase of the Microsoft OpenAI partnership: https://openai.com/index/next-phase-of-microsoft-partnership/ [https://openai.com/index/next-phase-of-microsoft-partnership/] * OpenAI, OpenAI available at FedRAMP Moderate: https://openai.com/index/openai-available-at-fedramp-moderate/ [https://openai.com/index/openai-available-at-fedramp-moderate/] * OpenAI, Our response to the Axios developer tool compromise: https://openai.com/index/axios-developer-tool-compromise/ [https://openai.com/index/axios-developer-tool-compromise/] AI-assisted tools were used in parts of the research and production workflow. Final editorial judgment, risk posture, and release approval stayed human-led. This is operational guidance, not legal advice. These are my opinions and are not representative of any organization.

AI Change Desk | EP022: Access Lifecycle Check

OpenAI Workspace Agents, FedRAMP Moderate availability, the OpenAI-Microsoft partnership update, Anthropic-Amazon compute expansion, and the Sora shutdown all point to one Wednesday operator question: when AI access expands, shifts, or disappears, who owns the lifecycle before teams build on the wrong surface? * Workspace Agents point to reusable agent surfaces inside business workspaces. * FedRAMP Moderate availability expands the regulated-access surface for ChatGPT Enterprise and the API Platform. * OpenAI and Microsoft updated their partnership structure, creating a dependency-map refresh signal. * Anthropic and Amazon expanded their compute collaboration for up to 5 gigawatts of capacity. * Sora discontinuation keeps the sunset/export/migration question on the table. AI access is no longer a yes-or-no inventory question. Teams need to know whether each AI surface is approved, piloted, sunsetting, or blocked, and who owns evidence, fallback, communication, and exceptions. Run a 30-minute access lifecycle check: 1. List three AI surfaces people actually use or are requesting this week. 2. Mark each as approved, pilot, sunset, or blocked. 3. Name the admin owner, evidence owner, and sunset/migration owner. 4. Confirm export and fallback paths. 5. Send one plain-language memo about what is allowed, changing, ending, blocked, and who approves exceptions. * OpenAI Help Center, ChatGPT Enterprise and Edu release notes: https://help.openai.com/en/articles/10128477-chatgpt-enterprise-edu-release-notes [https://help.openai.com/en/articles/10128477-chatgpt-enterprise-edu-release-notes] * OpenAI, OpenAI available at FedRAMP Moderate: https://openai.com/index/openai-available-at-fedramp-moderate/ [https://openai.com/index/openai-available-at-fedramp-moderate/] * OpenAI, The next phase of the Microsoft OpenAI partnership: https://openai.com/index/next-phase-of-microsoft-partnership/ [https://openai.com/index/next-phase-of-microsoft-partnership/] * Anthropic, Anthropic and Amazon expand collaboration: https://www.anthropic.com/news/anthropic-amazon-compute [https://www.anthropic.com/news/anthropic-amazon-compute] * OpenAI Help Center, What to know about the Sora discontinuation: https://help.openai.com/en/articles/20001152-what-to-know-about-the-sora-discontinuation [https://help.openai.com/en/articles/20001152-what-to-know-about-the-sora-discontinuation] AI-assisted tools were used in parts of the research and production workflow. Final editorial judgment, risk posture, and release approval stayed human-led. This is operational guidance, not legal advice. These are my opinions and are not representative of any organization.