AI Change Desk | EP030: Always-On Agent Control Check

AI Change Desk | EP033: Agent Runtime Budget Check

Agent work is not just an access question anymore. It is becoming a runtime budget question. This brief looks at Microsoft's Copilot Cowork general availability and Work IQ controls, then pairs that with Anthropic's statement that it is removing access to Fable 5 / Mythos 5 to ask a practical operator question: If an agent can retrieve context, call tools, run longer tasks, and consume metered credits, who owns the budget gate before the work continues? Run one Agent Runtime Budget Gate by June 24, 2026. Use: * Microsoft Copilot Cowork GA: https://www.microsoft.com/en-us/microsoft-365/blog/2026/06/16/copilot-cowork-is-now-generally-available/ [https://www.microsoft.com/en-us/microsoft-365/blog/2026/06/16/copilot-cowork-is-now-generally-available/] * Microsoft Work IQ APIs: https://www.microsoft.com/en-us/microsoft-365/blog/2026/06/02/announcing-the-new-work-iq-apis/ [https://www.microsoft.com/en-us/microsoft-365/blog/2026/06/02/announcing-the-new-work-iq-apis/] * Anthropic Fable/Mythos access-removal statement: https://www.anthropic.com/news/fable-mythos-access [https://www.anthropic.com/news/fable-mythos-access] * OpenAI ChatGPT release notes: https://help.openai.com/en/articles/6825453-chatgpt-release-notes [https://help.openai.com/en/articles/6825453-chatgpt-release-notes] * OpenAI Memory FAQ: https://help.openai.com/en/articles/8590148-memory-faq/ [https://help.openai.com/en/articles/8590148-memory-faq/] Production disclosure: AI-assisted tools were used in parts of the research and production workflow. Final editorial judgment, risk posture, and release approval remain human-led. This is operational guidance, not legal advice.

AI Change Desk | EP032: Memory Summary Exit Check

If AI memory can be edited more visibly, turned off more easily, and still be rebuilt from old context later, the operating question is not whether the settings page looks cleaner. It is what evidence proves sensitive or stale context actually left the workflow. * Why OpenAI's June 12 memory-summary controls matter operationally. * Why deleting visible memories is not the same as deleting past chats or every source. * Why a partial memory summary creates a partial-ledger problem. * How Developer mode and model retirement add inspection and version-receipt pressure. * A forty-five minute Memory Summary Exit Check operators can run this week. * OpenAI ChatGPT release notes: https://help.openai.com/en/articles/6825453-chatgpt-release-notes [https://help.openai.com/en/articles/6825453-chatgpt-release-notes] * OpenAI Memory FAQ: https://help.openai.com/en/articles/8590148-memory-faq/ [https://help.openai.com/en/articles/8590148-memory-faq/] * OpenAI Codex browser docs: https://developers.openai.com/codex/app/browser [https://developers.openai.com/codex/app/browser] * OpenAI Lockdown Mode: https://help.openai.com/en/articles/20001061-lockdown-mode [https://help.openai.com/en/articles/20001061-lockdown-mode] * OpenAI memory product post: https://openai.com/index/chatgpt-memory-dreaming/ [https://openai.com/index/chatgpt-memory-dreaming/] * YouTube AI labels update: https://blog.youtube/news-and-events/improving-ai-labels-viewers-creators/ [https://blog.youtube/news-and-events/improving-ai-labels-viewers-creators/] * Podnews AI disclosure guidance: https://podnews.net/update/ai-disclosures [https://podnews.net/update/ai-disclosures] AI-assisted tools were used in parts of the research and production workflow. Final editorial judgment, risk posture, and release approval stay human-led. This is operational guidance, not legal advice.

AI Change Desk | EP031: Memory Control Plane Check

AI memory is becoming more useful, but usefulness creates a new operating surface. If the system can carry context forward, teams need a memory control plane: summary, source, correction, deletion, sensitive-work mode, and disclosure. * Why better memory is not just personalization; it is source-of-truth pressure. * What OpenAI's June 4 memory rollout changes for operators. * Why memory summaries, source tracing, correction, and deletion paths matter. * How Lockdown Mode fits sensitive browsing and hostile-input workflows. * Why audience disclosure still belongs in the release workflow. * A 45-minute memory-control-plane check for Monday teams. What would have to be true for your team to trust remembered AI context in production work? * OpenAI memory rollout: https://openai.com/index/chatgpt-memory-dreaming/ [https://openai.com/index/chatgpt-memory-dreaming/] * OpenAI Memory FAQ: https://help.openai.com/en/articles/8590148-memory-faq/ [https://help.openai.com/en/articles/8590148-memory-faq/] * ChatGPT release notes: https://help.openai.com/en/articles/6825453-chatgpt-release-notes [https://help.openai.com/en/articles/6825453-chatgpt-release-notes] * Lockdown Mode: https://help.openai.com/en/articles/20001061-lockdown-mode [https://help.openai.com/en/articles/20001061-lockdown-mode] * YouTube AI labels: https://blog.youtube/news-and-events/improving-ai-labels-viewers-creators/ [https://blog.youtube/news-and-events/improving-ai-labels-viewers-creators/] * Podnews AI disclosure guide: https://podnews.net/update/ai-disclosures [https://podnews.net/update/ai-disclosures] 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 | EP030: Always-On Agent Control Check

Microsoft and OpenAI moved agent work closer to persistent identity, internal apps, and publishable work surfaces. The operator question is who owns the standing permission before an agent keeps acting in the background.

AI Change Desk | EP029: Agent Reliability Evidence Check

Date: 2026-06-01 Agents are getting longer leashes: remote work sessions, stronger coding/workflow behavior, and practical observability/test tooling are all moving at the same time. This episode turns that into an operator question: when an agent can do more, what proof comes back before the work is trusted? When the agent can do more, what proof do you require before you trust the work? Run one agent reliability evidence check this week: 1. Scope receipt: what can it reach? 2. Effort receipt: how long, how hard, and how expensively can it work before checkpoint? 3. Quality receipt: what tests or reviews prove the output is usable? 4. Drift receipt: what changed since the last good run? 5. Fallback receipt: who stops, reroutes, or explains it when it fails? * OpenAI ChatGPT release notes: https://help.openai.com/en/articles/6825453-chatgpt-release-notes [https://help.openai.com/en/articles/6825453-chatgpt-release-notes] * OpenAI Codex cloud documentation: https://developers.openai.com/codex/cloud/ [https://developers.openai.com/codex/cloud/] * Anthropic Claude Opus 4.8: https://www.anthropic.com/news/claude-opus-4-8 [https://www.anthropic.com/news/claude-opus-4-8] * AWS LLM observability: https://aws.amazon.com/blogs/machine-learning/comprehensive-observability-for-amazon-sagemaker-ai-llm-inference-from-gpu-utilization-to-llm-quality/ [https://aws.amazon.com/blogs/machine-learning/comprehensive-observability-for-amazon-sagemaker-ai-llm-inference-from-gpu-utilization-to-llm-quality/] * AWS deep-agent evaluations: https://aws.amazon.com/blogs/machine-learning/evaluating-deep-agents-using-langsmith-on-aws/ [https://aws.amazon.com/blogs/machine-learning/evaluating-deep-agents-using-langsmith-on-aws/] * AWS agent test-suite datasets: https://aws.amazon.com/blogs/machine-learning/build-a-test-suite-that-grows-with-your-agent-with-dataset-management-in-amazon-bedrock-agentcore/ [https://aws.amazon.com/blogs/machine-learning/build-a-test-suite-that-grows-with-your-agent-with-dataset-management-in-amazon-bedrock-agentcore/] * OpenAI May 28 model lifecycle note: 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 my opinions and are not representative of any organization.