❌

Normal view

Siri AI arrives with personal context, app actions, and a new privacy architecture

15 September 2026 at 21:39

Siri AI is beginning its public rollout as Apple transforms its familiar assistant into a substantially more conversational system built around personal context, onscreen awareness, web knowledge, and the ability to perform actions across apps.

The beta is available first in English on compatible devices running iOS 27, iPadOS 27, macOS 27, watchOS 27, and visionOS 27. French, Japanese, Korean, Portuguese, and Spanish support is scheduled for October. Availability remains more limited in some regions, with Siri AI initially unavailable on iPhone, iPad, and Apple Watch in the European Union and unavailable in China while Apple addresses regulatory requirements.

The release follows several years of gradual Apple Intelligence expansion, but Siri AI represents a more fundamental change. Instead of handling each request largely as an isolated command, the assistant can maintain conversations, find relevant personal information, understand what is displayed on a device, and combine those capabilities to complete multistep tasks.

A smartphone lock screen shows a Safari notification: “The Brian Tran Band Tour. An update was detected on this page.” Flashlight and camera icons are visible at the bottom of the screen, highlighting how personal context and privacy architecture work together to keep your notifications secure and relevant.
Image Credit: Apple Inc.

Siri AI can connect personal context with app actions

Personal context is one of the biggest differences between Siri AI and previous versions of the assistant.

The system can search across a user’s messages, email, photos, notes, and other information when responding to a request. Apple offers an example in which someone asks what a family member suggested doing during an upcoming visit. Siri can locate the relevant conversation, find a recipe previously sent by email, and then place the ingredients into a Reminders grocery list.

That combination of retrieval and action is central to the new design. Siri AI can draft an email, edit and share photos, create calendar events, manage reminders, control media, and perform other supported actions without requiring users to manually move information between applications.

Third-party apps can participate through Apple’s App Intents architecture. Existing integrations include tasks such as messaging through WhatsApp or playing an audiobook in Audible, with Apple also previewing deeper capabilities in applications including Microsoft Outlook, Notability, and Tripsy.

Onscreen awareness adds another layer. Siri can identify information currently visible on a device and act on it. Someone viewing a sports website, for example, can ask Siri to identify upcoming home games and add them to Calendar without manually copying dates.

Apple has also expanded Siri beyond voice. On iPhone, users can invoke the assistant with the side button, voice command, or by swiping down from Dynamic Island. On iPad and Mac, Siri AI is integrated into Spotlight, while systemwide context menus can send selected files, images, or text directly to the assistant.

A tablet screen displays a document titled “Intern Onboarding” with instructions on product photography for a summer intern named Marieke. Thanks to advanced privacy architecture, the onboarding materials are tailored using personal context without compromising confidentiality. The time shown is 9:41 AM, and the date is Wed Apr 1.
Image Credit: Apple Inc.

Siri AI gets its own app and conversation history

Siri AI is no longer confined to a temporary interface that disappears once a request is complete.

Apple has introduced a dedicated Siri app where users can begin new conversations or revisit previous ones. Conversation history can sync privately through iCloud across iPhone, iPad, Mac, Apple Watch, and Apple Vision Pro, allowing a discussion started on one device to continue on another.

Follow-up questions can retain the context of an earlier answer, giving Siri a more conventional conversational interface for longer exchanges.

The assistant also has access to broad web knowledge for questions that cannot be answered through personal information or local device data. Apple says Siri can retrieve current information for topics ranging from sports results to travel planning and nearby businesses.

Visual Intelligence expands alongside the assistant. On iPhone, a dedicated Siri mode inside Camera can identify and respond to objects or information in front of the user. A concert poster, for example, can become the starting point for questions about performance times followed by the creation of Calendar events.

On iPad, Visual Intelligence is integrated with screenshots. Mac users can select content on their displays through a keyboard shortcut, while Vision Pro users can ask Siri about app windows or physical objects simply by looking at them.

Writing Tools are similarly integrated across the system. Siri can generate drafts, revise existing text from natural-language instructions, and provide writing suggestions. In Mail and Messages, Apple says it can take a user’s typical communication style with a particular recipient into account, including tone and punctuation patterns.

An iPhone and Apple Watch display colorful health and fitness data, including activity rings and assessment results, on their screens. Enhanced by Siri AI to provide insights tailored to your personal context, the devices are set against a plain light background.
Image Credit: Apple Inc.

Siri AI runs across on-device and private cloud models

Siri AI is powered by a new generation of Apple Foundation Models developed in collaboration with Google using Gemini technology, marking a notable shift in Apple’s AI infrastructure.

The architecture divides processing between models running directly on the device and larger models operating through Private Cloud Compute. Apple says requests sent to Private Cloud Compute are processed without personal data being stored or made accessible to the company.

Core resources such as the Spotlight index and Apple’s App Toolbox can remain on-device, allowing Siri to retrieve local information and perform supported actions without sending every request to a remote server.

More capable devices can also use AFM Core Advanced, Apple’s highest-performance on-device model. It powers improvements including more expressive Siri voices and advanced systemwide dictation that automatically handles capitalization, punctuation, and formatting.

Compatibility varies by feature. Apple Intelligence supports iPhone 16 models and later, iPhone 15 Pro and Pro Max, M1 or later iPads and Macs, iPad mini with A17 Pro, Apple Vision Pro, and supported Apple Watch models when paired with a nearby Apple Intelligence-enabled iPhone.

AFM Core Advanced requires newer hardware, including iPhone Duo, the iPhone 18 Pro line, iPhone Air, iPhone 17 Pro models, qualifying M4 or later iPads with at least 12GB of unified memory, M3 or later Macs with at least 12GB, and Apple Vision Pro with M5.

A virtual window displays a digital article about lotus leaves in a cozy living room, featuring diagrams and text, with modern furniture and warm lighting in the background. Integrated Siri AI enhances the experience by offering personalized suggestions while maintaining robust privacy architecture.
Image Credit: Apple Inc.

Siri AI arrives with limits as Apple expands access

The initial Siri AI release remains explicitly labeled beta, and some of the surrounding Apple Intelligence features are scheduled for later updates.

Apple also confirms that features relying on server-side models can be subject to daily usage limits. That includes Siri AI, cloud-based photo editing, Image Playground, and AFM 3 Cloud models used through Shortcuts. Limits can vary depending on the feature, request complexity, system demand, and other factors.

Apple says expanded access to server-dependent features will eventually be available for a fee, introducing a future paid layer to parts of Apple Intelligence even as the core system remains integrated into supported devices.

Apple will also expand its intelligence capabilities on Apple Watch later in 2026. Planned Audio Intelligence features on Apple Watch Series 12 and Ultra 4 include Live Rewind, which can display text representing the previous 15 seconds of a conversation, and Siri Recap, which generates high-level summaries that can be reviewed later in the Siri app.

Those functions are designed around a hardware-isolated Secure Exclave on the S11 chip, with Apple saying raw audio is processed in isolation and immediately deleted rather than stored as recordings. Live Rewind and Siri Recap are scheduled to enter beta later in 2026, making the current Siri AI launch the beginning of a staged expansion rather than the final form of Apple’s new assistant.

The post Siri AI arrives with personal context, app actions, and a new privacy architecture appeared first on AppleMagazine.

Exposed Vite servers are being probed for AWS and Azure credentials

15 September 2026 at 15:22

Attackers have opened a new front in their war on software developers: Vite servers, which they are probing for sensitive data including cloud credentials, infrastructure configuration and environment files.

Vite was created as a build tool for Vue, a JavaScript framework for building user interfaces and web applications, but has now become a widely used development server and build tool across the JavaScript ecosystem.

F5 Labs reported that attackers sent more than 32,000 attempts to scan exposed Vite servers on its honeypot network, grouped into 807 attacks (or sessions), during August, a sharp increase from just 1,732 attempts over the previous three months.

“Rather than target a single file, the scanning fleet systematically cycled through extensive wordlists of environment files, AWS keys, Azure tokens, and Infrastructure-as-Code state files,” F5 threat researcher, Adam Metcalfe-Pearce, wrote in a blog post on F5’s blog.

F5 noted that Vite normally binds to localhost, but developers can expose it through the “–host” option, server configuration, container port mappings or other deployment mistakes.

Scans targeted a file-access bypass

The activity targeted a recently disclosed vulnerability that allows unauthenticated attackers to bypass Vite’s file-access restriction and retrieve files from the host system. Tracked as CVE-2026-39364, the flaw allows attackers to bypass the “server.fs.deny” deny-list protection used to prevent access to sensitive files.

“When specific parameters such as ?raw, ?import&raw, or ?import&url&inline are appended to a request, the server fails to enforce deny-list filtering and serves the target file with an HTTP 200 response,” Metcalfe-Pearce wrote.

Some requests also used double-encoded path traversal, which F5 said indicated an attempt to evade security controls such as reverse proxies and web application firewalls (WAFs).

Assigned a severity rating of CVSS 8.2 ,the flaw affects Vite 7.1.0 through versions before 7.3.2 and Vite 8 versions before 8.0.5.

F5 recommended updating Vite to a patched version, rotating potentially exposed secrets, ensuring development servers do not bind to external interfaces, and auditing Docker, Kubernetes and cloud configurations so development ports are not exposed to the public internet.

The blog also shared the curated directory and credential wordlists the attackers used during these attacks.

Vite was part of a broader scanning pattern

F5 also observed attackers combining CVE-2026-39364 with older Vite file access vulnerabilities, including CVE-2025-30208, CVE-2025-31125 and CVE-2024-45811. The same scanning infrastructure also probed for a Next.js middleware bypass, indicating that the activity is not confined to a single framework.

In its blog post the company also noted that, apart from CVE-2025-31125, none of these CVEs are yet listed in CISA’s Known Exploited Vulnerabilities (KEV) catalog.

While F5 saw a sharp increase in August in attacks on recently uncovered flaws in Vite, it didn’t make the top three CVEs attacked on the company’s honeypots, all of them much older. CVE-2017-9841, an almost decade-old critical remote code execution flaw in PHPUnit, remained top of the table with 4,201 recorded attacks, followed by CVE-2018-14028, a failure to verify WordPress plugins as valid ZIP files (4,102), and CVE-2018-20062, a ThinkPHP remote code execution in NoneCms (3,482).

15,000-Year-Old Stone Tool Experiments Shed Light on Mysterious Ancient Technological Transition

15 September 2026 at 13:55

Stanford University scientists say experiments on ancient Chinese stone tools, including 15,000-year-old hand axes, have solved a longstanding mystery about the critical technological transition from rudimentary hand tools to more versatile ground-edged tools, suggesting these new technologies enabled uses beyond food harvesting.

The research team behind the new analysis said the discovery of ground-edged sickles and knives in Neolithic North China, likely used for fiber production and harvesting, combined with their replica-based experiments, highlights the growing technological capabilities of the transition between Paleolithic and Neolithic peoples.

“The combined experimental and archaeological evidence from the site of Peiligang indicates that the emergence of ground-edged tools marked a significant step in technological specialization from the Late Pleistocene to the Early Holocene,” the researchers write in a paper detailing the work.

Mysterious Technological Transition Hidden in 15,000-Year-Old Stone Tools

According to lead author Ran Chen and colleagues, archaeologists widely regard ground-edged cutting tools like the modern sickle as “technological hallmarks of early agriculture in North China.” However, they note, the functional foundations of this advanced toolmaking capability “remain insuf­ficiently tested.”

The research team also noted that most analyses of the transition from the Upper Paleolithic to the Early Neolithic (ca. 15,000–8,000 BP) in ancient China have viewed tools through “the lens of food production.”

“Within this framework, cutting tools, including early flakes and blades and later ground-edged sickles and knives, are often interpreted primarily as implements for harvesting cereals through cutting stems and leaves,” they explained.

The researchers said these earlier findings made them wonder whether this “food-focused perspective” could have led researchers to miss the broader range of plant resource exploitation possibilities in some of the 15,000-year-old stone tools previously discovered, prompting their replica-based experiments.

“The development of stone tool technology in North China provides a framework for reassessing this long-term relationship between plant use and technological change,” they explained.

Experiments Reveal Ground-Edged Tools Were Multifunctional Implements

To test their hypothesis, Chen and colleagues analyzed 140 stone artifacts previously collected from the Peiligang site in Henan Province, China. This included some 15,000-year-old Upper Paleolithic flaked stone tools and several more advanced Early Neolithic flaked and ground-edged stone tools.

Rather than test irreplaceable artifacts, the study authors created realistic experimental replicas.

15000-year-old stone tools mystery
A researcher demonstrates the use of an experimental sickle replica to harvest velvet leaf (Image Credit: Ran Chen).

Testing the effectiveness of the oldest, most rudimentary stone flake designs and the more technologically advanced ground-edged tools for harvesting seed-bearing grasses, the researchers found little measurable advantage between the two designs.

However, when the researchers compared the 15,000-year-old stone flake tools against ground-edged tools made thousands of years later, they found the more technologically advanced tools were “significantly more efficient at cutting thick-stemmed weeds and fiber-yielding plants.”

“Upper Paleolithic flaked tools were multifunctional implements used for processing diverse plant and animal materials, and Early Neolithic flakes continued to serve similarly flexible roles,” the study authors explain. “In contrast, Early Neolithic ground- edged tools show marked specialization in plant- related tasks.”

More Advanced Tools Emerged Through Broader Functional Demands

When discussing the experimental results, the team noted that their findings were supported by microfiber and starch residues found on some of the ancient tools, suggesting that “ground- edged sickles and knives were used not only for plant foods but also for harvesting and processing fibrous plants.”

“These findings indicate that ground- edged cutting tools emerged through broader functional demands, including fiber production, and potentially vegetation clearance, rather than cereal harvesting alone,” they explained.

Beyond the food-harvesting uses of ground-edged tools, Chen and colleagues said their identification of non-food plant labor like fiber production as an important driver of technological evolution and specialization “reframes the emergence of ground- edged tools as part of a broader technological and economic reorganization in early Holocene East Asia.”

“These findings identify nonfood plant work as an important contributor to the adoption of ground-edged cutting tools and show that tools conventionally linked to early agriculture were shaped by broader demands than food production alone,” they explained.

Finally, the study authors suggested that their analysis of 15,000-year-old Chinese stone tools could “invite renewed attention” to ancient fiber-based economies and nonfood plant use during forager–farmer transitions and in early farming societies beyond China.

The study “Plant fiber exploitation contributed to the emergence of ground-edged cutting tools in North China” was published in Proceedings of the National Academy of Sciences. 

Christopher Plain has spent the last six years as Associate News Editor and Head Science Reporter at The Debrief. Follow and connect with him on X, learn about his novels at plainfiction.com, or email him at christopher@thedebrief.org.

The best IDE for agentic AI may not be an IDE at all

15 September 2026 at 10:00

Steve Yegge is not the shy and retiring type, so when he wants recommendations on how others are managing 10 to 20 (or more) coding agents, he posts the question on X. Specifically, he’s looking for an IDE because “I use Emacs, and I wouldn’t wish it on you.”

The replies (600 and counting) offer plenty of alternatives: Herdr, cmux, Conductor, the Claude and Codex desktop apps, and an impressive assortment of homemade software. For anyone hoping the industry had settled on a sensible way to work with agents, clearly we haven’t. Hence, Yegge’s question.

The most interesting data hidden in the replies, however, isn’t which IDE or IDE stand-in developers are using. Rather, it’s what developers have added to these tools to accommodate the technology’s shortcomings. These include shortcuts to find the agent that needs a decision, ways to recover an earlier conversation, and groupings that explain how a task fits into a project. In other words, despite the incredible intelligence we now have to help us write code, developers are still struggling with the simple task of automating their remembrance of what they asked AI to do.

We seem to have made it easier to generate work without making it easier to absorb and finish work.

Everyone’s building a workspace switcher

Mark Jaquith uses Herdr with a custom interface to jump to an agent needing his attention. Kai Backman has been working on a keyboard shortcut to take him to the “next most relevant place to take action.” Jacob Voytko built a workspace switcher that groups tasks within milestones and lets him jump to the corresponding tickets and pull requests. He wanted a visual sense of where the work stood, rather than an unstructured list. Another respondent, Basil, built a manager that helps him “find the session where we did x.”

Of course, developers have always customized their tools. Emacs users alone could supply scads of evidence. But, again, it’s not really about the fact that developers are tweaking their tools, but why. So much of the tweaking is intended to help cohere the developer’s intentions with the work that’s happening in several places at once. They’re not asking for better AI: They’re asking for AI to help them express their humanity, as it were.

The work comes back

Consider a developer who asks one agent to fix a bug, another to investigate a performance problem, and a third to update a dependency. While the agents work, she can do something else, which is what makes LLM-driven development so appealing—at least, until the agents return.

None of those agents does work that is fully isolated from the rest of the system. Think about it: The bug fix changes behavior someone may depend on. OK … we can address that! But wait, now we have the performance investigation offering three options, each with different costs. Hmm. Hold on a minute while I tackle this … except the dependency update isn’t waiting. It passes its tests, but the agent has also rewritten a configuration file. Better check that!

As this simple example shows, before the developer can move forward on any decision, she first needs to recover what she asked for, what the agent discovered, and what remains uncertain. And, no, adding more agents doesn’t solve the problem. It could instead compound the problem.

The agents may have saved hours. Hurray! But a list of completed sessions doesn’t tell the developer where to begin. Nor does a green test result answer the question of whether the change belongs in the application.

This is why the number of agents running tells us so little, even if it makes us feel cool. I mean, what are those agents doing, anyway? Yegge’s commenters provide some clues. For example, Anton describes using 30 terminal tabs with one active agent per project, so as to keep their work from overlapping. Jerry Combs says he generally keeps no more than three conversations going, with agents managing their own subagents as needed. Even those three conversations are difficult enough to follow.

Both approaches can make sense. The demands depend on how independently the work can proceed and how much human judgment it requires along the way. A developer with 20 agents may have fewer decisions to make than someone with three.

Gergely Orosz recently listed several observations worth considering together: developers spending less time in IDEs, code reviews becoming theater, and people working more despite AI’s productivity promises. His observations don’t establish that agent tools cause overwork or superficial review. They do make it worth asking whether we’re shifting effort into places our productivity stories neglect. Watching an agent produce a change is satisfying, but spending the afternoon reconstructing why six changes were made is less so.

But that work, however unsatisfying, is necessary if those changes are going to be understood and maintained.

Teach the tools to wait

Some of the plumbing already exists to alleviate these issues. For example, Herdr tracks agents as working, blocked, or idle and carries those states into its tabs and workspaces; cmux offers notifications and a shortcut to the workspace with the most recent unread notification. These are useful starts, but they do highlight just how much remains to be done. After all, the most recent notification may concern the least important task, and an agent asking a question may be perfectly capable of waiting while the developer finishes something else.

The next improvement should help developers make those distinctions. A task should retain its original purpose, the relevant decisions, and the evidence supporting its result. When it needs a person, it should explain the decision required and what happens if that decision waits. A summary can help, but it must lead back to the actual changes and test results. Otherwise, we’ve made it easier to approve work without understanding it.

Again, the best tools for agentic AI will be the ones that bring the human back into the loop and provide the information necessary to make decisions.

I’d like a tool that can tell me a task is ready for review because the requested behavior has been demonstrated, while keeping a separate, less urgent question out of my way. I’d also like it to remember that I rejected an approach yesterday, so I don’t have to discover it again in today’s proposed fix. Whether that tool calls itself an IDE seems secondary. Google introduced Antigravity 2.0 as a standalone agent application without an IDE, while recommending that developers use it alongside their IDE of choice. In other words, the editor still has a job, even when it is no longer where every task begins.

In 2022, I wrote about cloud convenience and the tendency to misunderstand what developers want from their tools. They have work to do and want fewer obstacles to doing it. We should apply that same standard to agentic development across the whole task, including the effort of returning to it.

Not that we can put all the onus on AI and its tools. Teams have a part to play here. If every task is urgent, the tool has nothing useful to prioritize. If nobody defines what counts as finished, the tool can only report that an agent stopped. Agreeing on those things and limiting the work that needs simultaneous human decisions will do more than adding another status badge.

Yegge’s readers are already building pieces of this future, one shortcut and homemade workspace at a time. The vendor opportunity is to make that convenience available without requiring everyone to maintain a side project. Give developers more work they can confidently put behind them and fewer conversations they need to keep alive in their heads.

❌