Salesforce launches job-ready Agentforce portfolio plus a long‑horizon runtime

What changed: Salesforce announced a new portfolio of job‑ready agents (sales, service, commerce, HR/IT, supply chain and more) that connect to Customer 360 and ship with pre-built skills, actions, and data models, plus a new long‑horizon runtime that lets agents pursue goals over days or weeks. The release also highlights Agent Script (an open-source language for agent behavior), Multi‑Agent Orchestration (GA), and tooling to teach and continuously improve agents.

Why it matters: Founders and operators can start with ready-made agents instead of building from scratch, reducing time to value for CRM‑centric workflows and enabling multi‑step work (e.g., rescuing at‑risk deals) to run autonomously while preserving human control. The packaged approach also shortens integration work because agents are built to use existing Customer 360 context.

Try/watch: Pilot one job‑ready agent on a narrow, high‑value process (for example outbound lead qualification or returns handling) and measure cycle time and hand‑off rates; watch how Agent Script maps to your existing business rules and audit logs for compliance.

Moveworks model upgrade improves transparency for failed tool calls

What changed: Moveworks released a model upgrade that makes failed or empty tool calls return explicit failure/no‑results states and user guidance instead of appearing successful; the Standard rollout is dated September 14, 2026, with Frontier and Basic on nearby dates. The initial release targets Agent Studio Plugins.

Why it matters: Silent tool failures are a common source of reliability problems in agentic systems. Clear failure states improve troubleshooting, reduce user confusion, and let ops teams write safer retry and fallback logic for production agents.

Try/watch: Enable the upgrade in a staging environment, review agent traces to identify common failure modes, and update fallback messaging and monitoring alerts; note that deeper MCP (model context protocol) failure transparency is being handled separately.