More Information

The senior care system faces converging pressures from an aging population, severe staffing shortages, and limited time for individual wellness programming. Existing technologies include reminder apps, fall detectors, voice assistants, and companion devices. Each of these addresses only one piece of the problem. This paper argues for a different paradigm: wellness, defined across seven interdependent dimensions, as the organizing principle for a new category of socially assistive robot. It introduces the Care Robot Autonomy Scale (CRAS), a six-level framework that measures autonomy across assessment, intervention, social intelligence, and care coordination. The paper reviews the technical capabilities such systems require, the clinical evidence gathered to date, and a phased roadmap toward higher autonomy. It closes with educational implications for care operators, researchers, regulators, and robot platform developers.

The creators of the hit, enterprise-friendly, open source OpenClaw variant NanoClaw are partnering with software supply chain management leader JFrog to launch a new, joint security integration they say will protect NanoClaw autonomous agents from malicious code injection.

“These agents are doing things that you cannot necessarily control, and you cannot necessarily train,” said Gal Marder, Chief Strategy Officer at JFrog, in an exclusive interview with VentureBeat.

Available immediately, the partnership hardwires NanoClaw agents directly to JFrog’s vetted software registries, ensuring that AI assistants can only pull scanned, safe dependencies.

The release addresses a rapidly growing blind spot in tech: autonomous agents frequently install packages in the background to extend their capabilities, often without their human operators’ knowledge or oversight.

“The people who are operating the agents are not necessarily developers, and they are not even aware of the implications,” explained Gavriel Cohen, creator of NanoClaw and CEO and co-founder of its new commercial services startup, NanoCo AI.

To secure the broader ecosystem, the partners are working to make it available completely free of charge for the open-source community, while enterprise organizations can seamlessly route their agents through their existing, commercially licensed JFrog environments.

The new technical capability enabled by this partnership follows NanoCo’s moves to add permissions dialogs across the apps in which it’s available via a partnership with Vercel, and a new partnership with Docker to allow NanoClaw agents to run more securely, isolated from other software environments directly inside Docker virtual containers.

The risk of current, personal autonomous AI agents

When an operator interacts with an autonomous system like NanoCo’s NanoClaw, they communicate at a high level of abstraction.

A user might simply send an audio file or a voice note, prompting the agent to independently figure out how to process it.

As Cohen explained, the agent thinks, “oh, I can’t understand voice notes, so let me go and grab a package and download something and install it and set it up and run it”.

This dynamic self-improvement makes AI agents incredibly powerful, but it also renders them highly susceptible to software supply chain attacks.

Bad actors are increasingly poisoning open-source registries with malicious packages. Because agents act autonomously to fetch what they need, they bypass human scrutiny.

The operators, who may not even be developers, are largely unaware of the security implications unfolding behind the scenes.

How NanoCo and JFrog are working to stop agents from running malicious code

The integration between NanoCo and JFrog acts as an automated immune system for these AI environments.

Under the hood, NanoClaw agents are now configured to route their requests for software packages, CLI tools, and Model Context Protocol (MCP) servers exclusively through JFrog’s registries.

If an agent attempts to download a compromised library—such as a vulnerable version of the popular Axios package—the JFrog registry intercepts the request.

It blocks the installation, returning a security policy error to the agent, noting that the request was “rejected by JFrog’s registry with a 403 security policy”.

Crucially, the system does not just stop at blocking the threat; it creates a dynamic correction loop. The agent is notified of the vulnerability and guided to automatically seek out and install an approved, non-malicious version of the requested package instead.

For large organizations, this integration solves a massive compliance headache. Marder notes that as enterprises adopt autonomous agents, they require absolute visibility.

Organizations need “a system of record, we need somewhere to track what agents that’s running by whom and consuming what packages and using what skills and using what MCPs,” he told VentureBeat.

Beyond visibility, the JFrog integration provides a foundational “trust layer” and strict governance over what these automated systems are permitted to access.

Licensing and accessibility

In the realm of software distribution, licensing and access parameters dictate adoption. The NanoCo and JFrog partnership utilizes a dual-track approach to serve both individual open-source developers and highly regulated enterprises.

For the open-source community, the integration is completely free. JFrog is providing open-source NanoClaw users with complimentary access to safe, vetted sources of artifacts, tools, and skills.

This allows individual developers to run autonomous agents locally without drowning in manual approval requests for every single dependency. Furthermore, as community members build and share new “skills” for the agents, these contributions are uploaded to the registry, scanned for malicious code, and cleared before anyone else can use them.

This infrastructure directly neutralizes the threat of poisoned community repositories.

For enterprise deployments, the architecture plugs seamlessly into an organization’s existing commercial environment. Rather than using the public open-source registry, corporate users point their NanoClaw agents to their own internal JFrog registries.

This ensures that all agent activity adheres to the company’s specific commercial licenses, internal security policies, visibility needs, and governance standards.

As AI continues to blur the line between human intent and machine execution, the infrastructure securing that execution must evolve. This partnership acknowledges a core reality: you cannot train an AI to perfectly recognize every zero-day vulnerability; instead, you must build an environment where the agent simply cannot reach the vulnerability in the first place.

Anthropic’s troubles with the US government do not seem to be easing. The company has now been ordered to suspend access to Fable 5 and Mythos 5 for all foreign nationals, including foreign national Anthropic employees working inside the United States.

Anthropic said it received the directive on June 12 and is disabling the two models for all customers to comply. Other Anthropic models are not affected. The government has not publicly explained the full national security concern, but Anthropic says it understands the order is linked to a reported method for bypassing, or jailbreaking, Fable 5’s safeguards.

A fresh clash after the Pentagon fight

This is not Anthropic’s first serious standoff with Washington. Earlier this year, the company was caught in a dispute with the Pentagon after it refused to remove restrictions preventing Claude from being used for fully autonomous weapons and mass domestic surveillance. That fight led to claims of blacklisting and legal action, putting Anthropic’s safety-first position directly at odds with parts of the US government.

The latest directive puts Anthropic back in a familiar position. Officials are worried about access to powerful AI systems, while Anthropic argues that its safeguards are being misunderstood or judged by an unrealistic standard.

Why Fable 5 became a concern

The concern around Fable 5 is tied to Mythos 5’s advanced cybersecurity capabilities. Anthropic has said Mythos-class models can discover and exploit software vulnerabilities, and Mythos 5 was reportedly tested by the NSA and other government-linked evaluators before wider release. While those capabilities can help security teams identify and fix weaknesses, they also create national security concerns if they are used for offensive or malicious purposes.

Fable 5 was released only a few days ago as a public version of Mythos 5 with stricter guardrails. Anthropic said it was designed to block or redirect sensitive cybersecurity and biology-related queries to Opus 4.8.

Anthropic says the reported bypass only surfaced minor, already known vulnerabilities and that other public models can do similar things. Still, with a topic as sensitive as cybersecurity, caution is not unreasonable. If Mythos 5 is capable of identifying software vulnerabilities at a high level, then its guardrails cannot be merely good enough. They need to be airtight. Anthropic may argue that the reported jailbreak was narrow, but the government’s concern this time is easier to understand. In this case, “better safe than sorry” may be the government’s most defensible position.

Meta CEO Mark Zuckerberg’s internal announcement on Friday about a “large” companywide AI hackathon next month quickly sparked frustration and disbelief among employees.

In internal messages seen by WIRED, some workers wrote that added responsibilities in the wake of recent mass layoffs at the tech giant had left them with little time to join such ancillary activities. Others said they felt discouraged from participating because of what they viewed as low morale and declining trust in management across the company.

“I’m literally preoccupied with keeping the lights on for my team,” one employee wrote on Friday. “I have no incentive to participate, let alone have the time to do so.”

In a post shared to Meta’s roughly 70,000 employees, Zuckerberg framed the hackathon as a way for staff to build camaraderie at a time of widespread internal unrest. Ime Archibong, a vice president of product management at Meta, later shared additional details about the event, which he said would take place from July 14 to July 16 and focus “exclusively on AI Innovation.”

Archibong’s post drew swift pushback from several employees, who responded with angry messages and sarcastic memes. “I’m not sure that this company supports a hackathon culture anymore,” one employee wrote in a comment that drew more than 200 thumbs-up and heart reactions. “People are being asked to cover more work with less support while their colleagues get laid off, while also trying to avoid the risk of causing SEV1s [serious technical errors] with incautious AI use.”

The same employee alleged that hackathon efforts would not count toward performance evaluations, fueling frustration among the workers about the prospect of setting aside other projects to participate.

Dozens of people also reacted with laughs and thumbs-up to a meme inspired by the comedy film We’re the Millers, stating, “You all have the time for a hackathon?”

“I honestly don’t have the time to focus on this, and I’m expected to be 100% devoted” to regular work, another employee wrote. “I’ve participated in previous hackathons but this no longer feels like an option alongside pod sprints in my corner of the company.”

A third staffer called out what they described as “a disappointing change in culture” because “I don’t believe there is sufficient feeling of safety to spend time on hackathon innovations.”

Meta declined to comment for this story.

Meta has long hosted internal hackathons, but two sources tell WIRED this is the first companywide one to take place since 8,000 people were laid off last month.

A Meta software engineering veteran responded to some of the employee complaints by saying that everyone is encouraged to participate. But the message still didn’t quite land. “Every org I know has super aggressive goals, with efficiency gains expected and significantly less staffing,” an employee commented back. “There’s less time for focusing on other axis.”

The hackathon was one of several initiatives Zuckerberg laid out on Friday to reenergize his workforce and address internal criticism about the recent layoffs and other concerns. He said budgets for team offsites would increase and that the concept of hot desking, or workers only in the office part of the time having to share desks, would be done away with in some offices.

Last year, some workers banded together to survey colleagues about the removal of their desks and the chaos and lost productivity they believe it caused, according to a person familiar with the efforts who sought anonymity to describe sensitive discussions. The group urged management to return to every employee having their own space. The layoffs appear to have opened up room, while leaving less time to hack.