Editor's note
Today showed AI pulling two ways at once — toward more agents, and toward pacing the speed. OpenAI put the Codex harness behind an API and Salesforce lined up role-specific agents, while Anthropic's CEO called to pace development and rival leaders agreed. Meanwhile a maximum-severity Adobe Commerce/Magento zero-day keeps being exploited even after patching, and browsers grind out quiet optimizations. For SMBs, the job is to hold two habits with equal weight: trial new agents in small steps, and never neglect the basics like patching known vulnerabilities.
WebSansec
Critical Adobe Commerce/Magento zero-day (CVE-2026-75650) still exploited after patch
A maximum-severity flaw (CVSS 10.0) in Magento and Adobe Commerce lets unauthenticated attackers run arbitrary code by abusing the template engine, and it has been exploited in the wild since early September. Adobe shipped an emergency hotfix on September 7, but attackers keep changing payloads daily, and stores compromised before patching may still harbor backdoors. Cloudflare added an emergency virtual-patching rule on September 10.
Context
The bug, dubbed StyleSmuggler, injects and runs malicious PHP through Magento's template feature. A patch stops new intrusions but does not remove backdoors already installed or credentials already stolen, so patching alone is not recovery. Even rotating the encryption key does not invalidate secrets an attacker may already hold, which complicates cleanup.
HaLVision's take
For SMBs running online stores, this is an act-now item. For clients on Magento we recommend not just patching but a full pass — hunting for suspicious processes and web shells, and rotating API keys and payment credentials. A WAF from Cloudflare or others buys time, but it is not a reason to skip checking whether you were already breached.
Read source ↗AIOpenAI
OpenAI opens Agents API in public beta, exposing the Codex harness via one API
On September 10, OpenAI launched the Agents API in public beta, putting the harness that runs Codex behind a single API. Developers can build long-running cloud agents without writing their own orchestration, context management, or sandbox layers. There is no extra fee — you pay for the tokens and tools the agents use.
Context
Building autonomous agents has meant assembling the plumbing yourself — session handling, context compaction and recovery, and isolated execution environments. The Agents API has OpenAI manage that plumbing, and it supports your own tools and Model Context Protocol servers. Several sandbox providers, including Vercel and Cloudflare Dev, are named as launch partners.
HaLVision's take
It lowers the bar to building agents, but it also deepens how much of the foundation sits with one vendor. We would prove out behavior and safety on small internal automations first — with guardrails against runaway loops and cost — before extending to client work. The lock-in that comes with the convenience is worth pricing in before you adopt.
Read source ↗AIAxios
Anthropic's CEO Amodei urges pacing AI development; OpenAI's Altman and Musk agree
On September 12, Anthropic CEO Dario Amodei published a long essay arguing that the pace of capability gains should be held to what risk prevention can keep up with. As a unilateral step, he said Anthropic would give third-party evaluators employee-level access to independently verify its safety commitments. OpenAI CEO Sam Altman and Elon Musk voiced agreement within hours.
Context
The worry that safety verification cannot keep pace with fast-moving frontier models has been raised repeatedly across the industry. What stands out here is that several leading figures, including rivals, briefly aligned around the idea of managing the pace. How much real teeth independent verification is given will determine what the pledge is worth.
HaLVision's take
Where regulation and self-imposed rules head affects how we fit which models into real work. Regardless of the vendor, we judge such pledges by whether independent verification actually has teeth. Avoiding both doom and hype, we simply fold each provider's safety and governance posture into our selection criteria.
Read source ↗AISalesforce
Salesforce unveils seven named, job-ready AI agents in Agentforce
On September 11, Salesforce added seven named AI agents to Agentforce — Casey, Paige, Carter, Hunter, Marshall, Piper and Fin — each designed for a function such as sales, service, commerce or IT/HR. Six are generally available; the outbound-sales agent Hunter is in pilot with general availability planned for November. Salesforce also showed a long-horizon runtime that pursues goals over weeks.
Context
Shipping role-scoped, ready-to-use agents rather than a general chatbot aims to cut the friction that stalls adoption. Each agent is said to handle concrete work — returns across voice and chat, or IT/HR requests, for example — across multiple channels. A runtime that continues work over weeks, not a single conversation, is what makes real-world operation viable.
HaLVision's take
For SMBs, being able to trial role-specific agents without building from scratch is practical. We would start where the cost of failure is low — first-line inquiries or internal help — and carefully wire agents into existing CRM and workflows. A vendor's polish means little unless your own data and permissions are sorted out first.
Read source ↗WebMozilla
Firefox 156 arrives September 15 with up to ~45% faster PDF viewer startup
Mozilla is releasing Firefox 156 on September 15. The headline is a built-in PDF viewer that starts up to about 45% faster, alongside improved memory and CPU use when displaying large JPEGs scaled down to fit a page. On macOS, Firefox can now be set to open automatically at startup, among other tweaks.
Context
The browser is the substrate for how SMB sites render and for daily work, so rendering and memory-efficiency gains translate directly into perceived speed. Viewing PDFs — order receipts, handouts — is common in practice, so faster startup quietly trims users' waiting. It is worth noting as one of the optimizations that accumulate release over release.
HaLVision's take
It is not flashy, but for teams like ours that test across many sites, a faster browser helps daily throughput. We check our builds across multiple browsers including Firefox, and we track behavior differences in new versions early. Visitors' environments vary, so not optimizing for a single browser is the point.
Read source ↗