Quick summary

Not too long ago, there was a time when Kindles were the default choice for electronic reading devices. Then came Kobo, which became fairly popular. A few upstarts also came along the way, with Onyx Boox being one of the boldest entrants in the segment. Well, Amazon played it safe with Kindle, and so did Kobo. 

These new names began experimenting with the form factor, and it started redefining what it actually means to have a reading gadget in your bag, or pocket. From a mini tablet, we reached massive slates with stylus support. And then, extremely pocketable e-readers that stick to the back of your phone. Somewhere in between, we got a whole class of e-readers that look exactly like your phone.

The DuRoBo Krono is one such device. It looks like a phone, but tries to stand out with a clever scrolling dial on the side. You get minimalist software, but it does not try to restrict you, thanks to full support for Android and the Google Play Store. It also has a few clever tricks that turn it into a neat AI-powered voice note-taker. 

The rest of the package is fine. The screen is decent for reading. The battery life is amazing. You can even look at it as a minimalist music streaming device. And it doesn’t cost an arm and a leg, either. Overall, if you are chasing a versatile device and have been dreaming of an e-reader that looks like a phone, this is a fantastic pick.

DuRoBo Krono design and build quality

The biggest appeal here is a phone-like form factor. If you’re someone who dreads the idea of carrying a mini slate for reading and wants something that feels natural in your hands, you pick the DuRoBo Krono. It’s almost as thick and tall as my iPhone 17 Pro, but lighter than the Apple flagship.

It’s a unibody shell made out of sturdy plastic, with a cylindrical metallic hump running horizontally near the top edge at the back. It looks like a metallic axis. Near the left edge, it has breathing lights, and on either end, you will find the power button and the metallic smart dial that looks like the crown wheel on the Apple Watch.

The Dial, as DuRoBo likes to call it, is pretty smart. Depending on what you are doing, it can handle volume adjustment, brightness levels, and, of course, going up and down the page you are reading. And when you long-press the dial, it enters the voice mode for the Spark AI, where you can instantly record some voice notes, while the AI helps you with transcription and even summarization.

Overall, the build quality is pretty sturdy. It doesn’t feel cheap. The plastic shell has a matte-like finish that makes the device a tad easier to grip, and it doesn’t get smudged either, especially if you have sweaty palms. What really grinds my gears is the thick bezels upfront, but we’ll get into it later. 

The position of the smart dial is also pretty thoughtfully executed. If you’re a right-handed person, depending on the size of your palms, you will have either your middle finger or your index finger within a comfortable reach of the dial for scrolling the page or adjusting the backlighting levels. And if you are left-handed, your thumb is naturally resting on the dial, and you don’t have to readjust the device in your hands.

The big appeal, as I mentioned earlier, is to have a device that is pocketable and doesn’t make you stretch out your palms, or make them hurt after an extended reading period. Nothing feels more natural than a smartphone in your hand, and that’s exactly what the DuRoBo Krono is after. It feels like a secondary phone in your pocket, and to a large extent, also works like it. 

Score: 8/10

DuRoBo Krono display 

Running the show on the DuRoBo Krono is an E Ink Carta 1200 HD display, which measures 6.13 inches across and offers a resolution of 824 x 1648 pixels, which translates to a pixel density of 300 ppi. That’s plenty of sharpness for reading text. And even if you fire up the occasional picture book and have the display quality set to quality or clarity modes, you won’t struggle with making out what’s on the screen.

As you switch to a new frame or have enabled the speed preset for scrolling pace, the transition will make those images look like a sea of black and gray dots, with plenty of shimmering to go with it. But overall, for reading, I have no complaints. During daytime or even in rooms with dim light, I barely ever felt the need to turn on the front light. With the brightness level set to zero, you get a pristine white canvas that tries to ape the look of real paper.

If you’re a night owl and prefer to read in the dark, the front light comes in handy. What I appreciate the most is that you can adjust the temperature of the screen, taking it from a bright white color to an amber shade that is a lot more comfortable to gaze at for binge reading. The only issue is the refresh rate, which is something no commercially available e-ink device has managed to figure out at the hardware level. 

So, when you’re reading an article or a book, and have shifted the pages to scrolling mode instead of the traditional slide-based page view, the scrolling animations are smooth, but as you try to zoom in and zoom out, you feel that visual jitter very clearly.  There’s no escaping that. 

For reading books or any text-first content, I would suggest sticking with the speed preset because the scrolling is a lot smoother, and you don’t see any text shimmer. Furthermore, if you switch to the quality or clarity preset, it doesn’t actually create any difference in the visual quality of the text appearing on the screen. It will only make the interactions feel unnecessarily slow. 

I got the job done by sticking to the speed mode. But there is a bit of an odd hiccup, and I blame it on the software rather than the hardware.

So, when I am using the built-in reader, which is simply named “Read” on the DuRoBo Krono, I cannot access the three-level refresh mode controls. It doesn’t work for the random article PDFs that I have saved on my system, nor does it work for the PDF books that I have downloaded on the device. But as soon as I switch to a third-party app, like the Kindle app downloaded from the Google Play Store, these three controls appear in the quick settings panel. 

I hope DuRoBo fixes this odd problem. But as far as the raw reading pleasure goes, I don’t have any fundamental complaints about it. The display is sharp, bright, and feels easy on the eyes. And if your ultimate goal is a phone-like device to handle your reading habits, you won’t be disappointed by the DuRoBo Krono.

Score: 8/10

DuRoBo Krono Software

The software is the most controversial part of the DuRoBo Krono experience. The company went with a minimalist UI, which I believe suits the purpose. On the home screen, you just get six core controls. You can customize it and place your most frequently used apps, or stick to the default options. It’s almost identical to what you get with Niagara and Mako launchers on Android.

Personally, I like it a lot. I’ve used a bunch of phone-like e-reader devices, and all of them have the same home screen launcher look as your average Android smartphone or an iPhone. And that familiar look takes away from the inherent appeal of a device that is intended for losing yourself in pages. 

Of course, you have full Google Play support, and you can download whichever app you want and put it right on the main screen for quick access. But this minimalism also comes at a cost. I almost feel like the company didn’t put any effort into creating a standout reading experience on the DuRoBo Krono.

It’s so bare-bones that you often find yourself frustrated by the lack of even the most basic controls and page customization options. For example, when you’re reading a book, the only two controls available on the screen are changing the reading mode and opening the content list. In the top right corner of the screen, you get the bookmark option, and that’s all.

Only when you long-press on a word or passage do you get access to some basic formatting controls like underline, highlight, annotation, and copy.

The only standout tool is the AI explainer, which itself feels pretty slow. I almost never used it after a few attempts at trying to find the meaning or context. Functionally, this AI tool works fine, but it’s just so slow that I forgot its existence. The answers you get after summoning it sound exactly like how ChatGPT or Gemini would tell you the meaning and context of a word or passage. 

There is no option to engage in a back-and-forth chat about it. Visually, when you tap on the expand button of the AI window, it takes you to a page that looks like a combination of a dictionary and thesaurus, with some added context in a conversational tone. It might come in handy from time to time if you’re trying to look up the meaning of a word or seeking background information on a name, location, or event. 

The built-in text-to-speech feature, on the other hand, is also bare-bones. The recitation tone is extremely mechanical, and the only control you get is the speed. That’s all. You can’t even change the voice of the reader. The only occasion where I used the built-in Read app on the DuRoBo Krono is when I just wanted to skim through an article or a research paper. That’s all.

But if you’re someone who is particular about having control over the reading experience, you will want a third-party app.  The Kindle app, for example, will let you play with different fonts, adjust their size, the spacing, the page layout, margins, text alignment, background color, enable page scrolling with the volume button, and pick between a whole bunch of custom themes that will save you plenty of time. 

The Kindle app is not the best reading app out there. But compared to the Read app that ships on the DuRoBo Krono, Amazon’s app feels like a quantum leap in terms of customization options and useful features. But that’s not the only issue I have with the software experience.

As mentioned above, the refresh mode controls are implemented haphazardly. Additionally, beyond brightness and backlight color controls, you don’t get anything else. For comparison, on the Onyx Boox series of e-reader devices, you get at least five levels of display refresh rate, dark color enhancement, and a light color filtering slider. And these are the core controls that are implemented universally across the software experience, not just the built-in reader app.

But I also have a counterargument to make here. Compared to reading on a seven-inch or eight-inch slate, or even a device with a more squarish form factor, you don’t really need as many controls on a smartphone-sized screen. You are predominantly buying the DuRoBo Krono because it looks and feels just like your phone, and you are basically chasing that form factor for reading books.

If that sounds like you, there is not a lot that you’re missing. As I mentioned earlier, you just might like this stripped-down, minimalist, and no-frills software experience. You simply unlock the device, fire up the reading app of your choice, and start scrolling through pages, without even tapping on the screen.

Of course, it runs Android, so there is no hassle when it comes to accessing your books and having to worry about supported formats. You just download the required app or the cloud drive apps like Google Drive or Box, and quickly access all your books and reading material. All you need to do is scan the QR code or type in the IP address in your web browser’s URL field to access the file transfer dashboard.

This is not your typical cloud sync system. Instead, it’s a locaI network that lets you quickly drag and drop the files stored on your laptop and access them on the DuRoBo Krono within a matter of seconds. You can move your local music files, pictures, books, documents, and more without having to worry about any sign-in hassles.

I would go as far as claiming that the DuRoBo Krono is a perfect device for people who are chasing a digital detox. If you’re worried about the constant barrage of notifications, this one offers a respite. You can simply move your music files and the reading material on the DuRoBo Krono and never have to worry about linking it to the internet at all.

Score: 7/10

DuRoBo Krono performance and AI 

The DuRoBo Krono comes equipped with an unspecified octa-core processor, paired with 6 GB of RAM and 128 GB of onboard storage. There is no microSD card slot on this one, which is a shame. You also don’t get a 3.5-amp headphone jack, which leaves the USB-C port as the only hardware-level interface available to you.

Now, for a reading device, the onboard hardware is more than enough. But as you download more Android apps, you might start to see some sluggishness. For example, if you’re trying to switch between different apps that are running simultaneously in the background, the jitters are noticeable. In hindsight, those slow UI interactions also have to do with the fact that this is an inherently slow screen, not even your usual 60Hz panel available on even dirt-cheap phones.

So, what you see in terms of slow transitions and animations can be blamed more on the screen than the processor itself. In general, the durable kernel felt pretty snappy to me, whether it was scrolling the Internet, checking my Feedly lists, reading a book, watching the occasional podcast video on YouTube, or listening to music on Spotify.

What sets the Turbo Chrono apart from other phone-like e-reader devices is the built-in integration of an AI-powered notetaker. DuRoBo calls it Spark. You can access it by long-pressing the dial. The broad idea is that when you get that creative spark, you don’t have to open a dedicated app or access a device. 

Simply press the button, record your voice note, and save it. The onboard transcription system turns your voice notes into text, and there is also an AI Summarizer at your disposal. As far as transcription accuracy goes, I would say it’s around 90% accurate at identifying the words. It mostly struggles with proper nouns or words that are not inherently a part of the English language lexicon. 

It’s just funny that the Spark AI misread the very name of the device and transcribed it as “durable kernel” in front instead of “DuRoBo Krono.” Would I trust it as a note-taking device for recording my interviews and getting them transcribed? I would say yes. It’s not quite as accurate as a dedicated solution like WisprFlow or Willow Voice, but it more or less gets the job done. 

Besides English, you also get native support for Dutch, German, French, Spanish, Portuguese, Chinese, Japanese, and Korean. Unfortunately, there is no option available in the Spark AI app to add additional language modules. For those that are not available, you can simply install any other third-party transcription app from the Google Play Store and get the job done. 

Score: 7/10

DuRoBo Krono battery life  

The DuRoBo Krono comes equipped with a 3,950 battery. That’s like half of what you get on a modern-age Chinese flagship phone these days. But when you pair this with a monochrome screen and modest processor, the per-charge mileage is downright amazing. 

My reading habits are rather haphazard. Some days I spent only an hour reading a book, while seated in a cafe or just slouching on my sofa. I shifted into binge mode and spent three to four hours reading in one go.

With that kind of use in usage pattern, combined with the occasional 15-30 minute interviews, the DuRoBo Krono went a whole week in my most recent endurance test, and still had about 24% juice left in the tank. 

Now, it’s extremely hard to specify just how many hours this device is going to last, and that’s because that would depend on a number of factors. Do you turn on the screen backlight? What is the brightness level? Do you use the device for listening to music, either offline or streamed through the Internet? How is your daily AI usage and voice note-taking within the Spark app? You get the drift. 

But if you’re solely looking at the DuRoBo Krono from the perspective of a reading device that looks like a phone, this one will easily go beyond a week, and even survive a couple. Even if it lasts one week with mixed usage, I’ll still call it a win.

Score: 8/10

Should you buy? 

The DuRoBo Krono is rather a straightforward pick. If you need a minimalist reading device that looks like your phone, offers a no-frills reading and scrolling experience, and takes you away from the digital noise of a regular smartphone, it’s an easy pick. The battery life is enough to support your marathon reading sessions, lasting days in a row. 

The display is versatile enough to suit daytime readers as well as night owls. On the software side, it takes an utterly minimalist route. But if you find that limiting, you can go ahead and download any app of your choice from the Google Play Store. That’s the flexibility that you don’t get with devices from the likes of Amazon. 

On the flip side, there are still a few rough edges with the software, but nothing that can’t be fixed. And, hey, it can also double as your dedicated AI-powered note-taking and transcription device, without burdening you with any subscription. So there’s that hidden perk. Overall, at its current asking price of $280, the DuRoBo Krono is a meaningful addition to your everyday carry.

Why not try? 

Boox Palma 2 Pro: Boox no longer officially sells the Palma 2, so your only option is either trying to find it from a third-party store or picking the BOOX Palma 2 Pro. Priced at $379.99, this one comes with a color e-ink panel, offers far more rewarding software, and even supports stylus input.

Bigme HiBreak: Priced at $250, the Bigme HiBreak is a full-fledged smartphone, not a dedicated e-reader. The perks of picking this one include a paper-like color display, a built-in camera, a hybrid slot for accommodating a 4G SIM, and a microSD card, alongside a faster screen refresh rate technology.

XTEINK X4: If you are chasing the ultimate minimalist heating device, you should try out the XTEINK X4, which only costs $80 in the US. It’s pretty small, attaches magnetically to the back of your phone, and offers a solid battery life for a device of its size. If you want the warm backlight convenience, the X4 Pro model will serve you well at $99 a pop.

How I tested 

I carried the DuRoBo Krono with me for a spell of four weeks and used it as my primary reading device. In that spell, I paired it with my smartphone via WiFi hotspot to occasionally download Android apps and add books to my library from the Kindle store and Google Drive. 

I also compared it against a bunch of devices from rival brands, including Onyx Boox and XTEINK, to gauge the display quality, reading experience day-to-day, software performance, and reading conveniences. I also tested a variety of files, including PDFs, TIFFs, WAVs, and EPUBs, to consume audio-visual content in different formats.

FAQ (Frequently Asked Questions)

What is the screen size on the durable DuRoBo Krono?

You get a 6.13-inch 300 PPI E Ink Carta 1200 HD panel on the device. 

What operating system does it run? 

The DuRoBo Krono ships with a heavily skinned version of Android 15 out of the box.

What are the key hardware specs?

The device comes equipped with an octa-core processor, 6GB of RAM, and 128GB. 

Is there a microSD card slot on the device?

No, there isn’t. All file transfers either happen in wireless mode or while connected via the USB-C port.

Does it offer cellular connectivity support? 

No. In order to connect the DuRoBo Krono to the Internet, you will have to join a Wi-Fi network or mobile hotspot.

Dark Matter is officially back on Apple TV, and its season 2 premiere picks up seven months after everything fell apart last season. We know Dark Matter Season 1 used up all the material that author Blake Crouch wrote in his original novel. In a way, that story was already over, though it left plenty unfinished for the people who are now displaced in its aftermath.

Had Crouch signed away the rights and walked off, I’d have written off this season as a cash grab riding the first season’s success. Instead, he wrote every new episode alongside Jacquelyn Ben-Zekry, pushing the story somewhere his own book never went.

Episode 1 of Dark Matter season 2 is mostly about the show setting the table. A lot happens as we see where everyone is and how they’re holding up, and the story so far is genuinely engaging. It also left me with a few things I can’t stop turning over.

Questions I’m hoping Season 2 will answer

The episode opens with agent Mitchel MacNamara staring down a pile of genetically identical corpses, confidently assuming it’s cloning. He’s obviously wrong, but watching him chase the truth is going to be one of this season’s ongoing threads.

So the first question is: how did all these other Jasons end up dead? Season 1’s finale gave us a chaotic pileup of doppelgangers converging on the same reality, but the show hasn’t spelled out whether these deaths came from Jasons turning on each other, or something more deliberate, like a version of Jason trying to protect the secret of multiversal travel by eliminating witnesses. It’s the kind of mystery that could go a lot of different directions, and MacNamara’s investigation seems built to drag us through all of them.

Advertisement

If every choice creates a Jason, what about everyone else?

Jason, Daniela, and Charlie have spent seven months building a normal life in the woods, and that doesn’t last long. Another Jason, desperate and unraveling, finds Daniela alone in the house, refuses to leave, and forces her to shoot him. Cleaning up the body drags them back into the box entirely, and once inside, nothing goes smoothly.

Every choice creates a new Jason. That’s the rule this entire multiverse runs on, and it’s why we have so many Jasons cluttering this multiverse in the first place. But Daniela and Charlie have now traveled through that same box too, just far less than Jason has. Does that mean a few other versions of Daniela and Charlie exist somewhere, shaped by choices we’ve never actually seen them make? The show hasn’t touched this yet, and I wonder whether the writers have plans to deal with this or just quietly hope nobody notices.

Here’s what we learned, though

Ryan and Amanda spend most of the episode assuming their box is dead weight. It’s been relocated to a different part of the city, and Amanda’s working theory is that the move itself severed whatever connection powered it in the first place. As far as they know, they’re stranded.

Except they’re not. When Jason briefly steers his family into that same world, the visit ends up creating a new, functional box that Ryan and Amanda can now actually use. I’m guessing the next episode will show whether they can actually put it to use, which would confirm that moving a box doesn’t necessarily kill its connection to a world. As long as someone out there is still thinking about that world, the link holds. That’s bad news for the Dessens, who are hoping to disappear for good by destroying the box once they find their next favorite world.

My thoughts on the Dark Matter season 2 premiere

One episode isn’t much to judge a season on, and I’m not going to pretend I have this show figured out yet. But Episode 1, “A Quiet Life,” did what a premiere is supposed to do: it made me care about where all these scattered pieces are heading. And I’m sticking around to find out what happens next. I just hope the show remembers to actually answer these questions before season 2 runs out of episodes.

Meanwhile, I’ve got one eye on Silo too, its season 3 finale, “Troy,” lands this Friday, September 4, and it’s finally set to reveal how the world actually ended.

Advertisement

Microsoft is investigating a widespread service issue causing authentication issues, connection problems, email delays and failures, and various other issues for Microsoft 365 customers.

It first acknowledged this incident (tracked under EX1464935 in the admin center) at 5:30 PM UTC, when it began investigating a stream of reports  from users on social media regarding multiple issues affecting Exchange Online.

However, while Exchange Online is the most impacted service, Microsoft revealed in a new incident report (MO1465074) that this outage also impacts multiple other Microsoft 365 services, including OneDrive for Business and SharePoint Online, Microsoft Teams, Microsoft Purview, and Microsoft Defender XDR.

According to outage tracking service Downdetector, tens of thousands of Outlook and Microsoft 365 users are affected and experiencing issues receiving emails via Outlook and accessing Microsoft cloud services.

Microsoft says the list of Exchange Online symptoms includes:

• Delays or failures when sending or receiving email messages.
• Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
• Authentication-related errors when accessing Exchange Online services.
• Difficulties accessing or performing actions within Exchange administration experiences.
• Intermittent failures affecting mailbox operations and message delivery workflows.

Although the company has yet to reveal which regions are impacted, it has classified this outage as an incident, which is typically used to describe critical service issues with noticeable user impact.

​”We’ve isolated a common failure pattern across affected Exchange Online requests that is associated with authentication and protocol connectivity,” Microsoft added in the latest admin center update.

“We’re analyzing service telemetry to identify the underlying source of impact and validate potential remediation options. Additionally, we’re continuing to assess the scope of impact and monitor for additional affected scenarios.”

Microsoft has addressed multiple Exchange Online outages in recent months, most recently in June, when it mitigated a widespread service issue affecting the mail flow pipeline for customers across North America, Asia-Pacific (APAC), and Europe.

In April, it also resolved Exchange Online mailbox access issues that had intermittently impacted Outlook mobile and macOS users for weeks, and an Exchange Online outage that prevented users from accessing their mailboxes via Outlook on the web, Outlook desktop, Exchange ActiveSync, and other Exchange Online connection protocols.

Update August 31, 14:29 EDT: Microsoft blames the outage on core authentication configuration issues.

“We’ve identified issues related to a core authentication configuration used by multiple internal services within the Exchange Online infrastructure,” Microsoft said. “We’re performing a manual test on the individual server level to reset to configurations to validate if this resolves the issue.”

Update August 31, 15:09 EDT: Microsoft now tracks this outage under MO1465074 and says the incident also affects OneDrive for Business and SharePoint Online, Microsoft Teams, Microsoft Purview, and Microsoft Defender XDR.

Overall prevention scores can hide what happens after initial access. Once attackers are using valid credentials, prevention drops sharply.

The Blue Report 2026 measures defenses technique by technique across 338 million simulations run in customer production environments.

Get the report

The viral fervor we saw earlier this year around OpenClaw, the open source AI harness that turns powerful language models into autonomous workers the user can message via their favorite channels (Telegram, iMessage, WhatsApp, Discord etc), has cooled off substantially from its peak in March 2026.

But over the weekend, OpenClaw’s creator Peter Steinberger and current team of co-developers gave the world — especially enterprises — a reason to look at it again, announcing OpenClaw 2.0, billed as the most significant update to the harness and surrounding platform yet.

OpenClaw 2.0 seeks to transform what began largely as a personal agent harness into something increasingly designed for teams, shared infrastructure and enterprise workflows.

OpenClaw 2.0 introduces a rebuilt browser interface that brings conversations, files, approvals, configuration and live agent activity into a common workspace. It adds shared cloud sessions and multi-user collaboration. And it expands the security model with stronger sandboxing, role-based permissions, approval controls, secrets handling and auditing.

Together, those additions move OpenClaw closer to being infrastructure that an organization could deploy for employees rather than simply a powerful agent an individual developer runs locally.

They also sharpen a competitive question surrounding the project: whether OpenClaw has addressed the security and isolation concerns that helped inspire newer alternatives such as NanoClaw.

The answer is increasingly yes at the capability level — but not necessarily by default.

OpenClaw wants to become the shared agent layer

Released under the official name of v2026.8.1, the update spans installation, messaging, memory, skills, models, automations, browser and native applications, plugins and security.

Steinberger described the development of OpenClaw 2.0 as an exercise in using the product to build itself.

“Two months ago, we started the mission to ‘build OpenClaw with OpenClaw,’” Steinberger wrote on X early on August 31.

Over that period, he said, OpenClaw gradually moved its team away from individual local coding harnesses and toward team.openclaw.ai, a shared agent environment aware of what team members are working on.

“Multiplayer coding + infinite compute with nodes and cloud sessions has been a game changer for how we build,” Steinberger wrote, adding that local harnesses now “feel like relics of the past.”

That claim points toward one of the more important changes in OpenClaw’s enterprise proposition.

The dominant model for AI coding agents has generally been individual: a developer runs an agent in a terminal, IDE or desktop application, gives it access to a repository and lets it execute work within that environment.

OpenClaw 2.0 is pushing toward something different. Agent sessions can become persistent workspaces that outlive a single terminal or employee. They can be shared with colleagues, executed across other machines or cloud workers, and supervised through a browser.

For enterprises, that potentially turns the agent from an employee-level productivity application into a shared operational layer.

A new UI could broaden OpenClaw beyond developers

The redesigned Control UI is central to that strategy.

OpenClaw has shifted away from an Overview-first web application and made conversations the primary interface. Threads sit in a sidebar, while the active conversation occupies the main workspace. Files, approvals, settings and ongoing agent activity remain accessible around it.

The design deliberately brings OpenClaw closer to the interaction model employees already know from OpenAI’s ChatGPT, Anthropic’s Claude, Google’s Gemini and other conversational AI products.

That lowers an important barrier to enterprise adoption. Open-source agent frameworks are often powerful precisely because they expose low-level configuration, terminals, tools and runtime controls. Those same characteristics can make them difficult to deploy beyond engineering organizations.

OpenClaw 2.0 attempts to preserve the underlying control while putting a conversational interface on top of it. An employee can ask an agent to perform work without treating the terminal as the primary product interface. But OpenClaw does not hide what is happening underneath. The Control UI can surface session files, terminal activity, Git-backed changes, pull-request state, browser activity and interactive dashboards.

The release also places more emphasis on observability during agent execution. Tool calls and results are paired more clearly, file changes can appear as focused diffs, command activity is easier to inspect, and long-running background tasks can remain visible alongside the conversation. That combination matters for enterprise use.

Employees get a simpler interface for delegating work. Technical users retain access to the artifacts and execution state behind the conversation. Administrators gain a centralized place to configure and supervise the system.

The redesigned Settings workspace now encompasses agents, memory, plugins, MCP servers, devices, communication channels and device pairing. OpenClaw also consolidates model-provider administration, including credential status and, where providers expose it, model availability, quota, account balance, budget and spending information.

Limited-access browser users can request administrator privileges rather than automatically receiving them, with another administrator required to approve the escalation.

These are not especially flashy agent features. For companies deploying AI systems to dozens or hundreds of employees, they may be among the most important additions in the release.

Multiplayer sessions turn agent context into shared context

OpenClaw 2.0 also expands the agent from a personal workspace into a collaborative one.

Shared cloud sessions allow another employee to enter work already in progress without discarding the context accumulated by the agent.

Multi-user Gateways — the service that connects users and agents to tools, files, credentials and other resources — can track who created a conversation and which prompts were submitted by identified participants.

Owners and administrators can determine whether another user can read a session, suggest changes, work in draft mode or participate directly.

The interface adds session ownership, participant attribution, presence and even typing indicators. For coding teams, that introduces a workflow closer to collaborative software development than traditional AI chat.

A developer could initiate a task and allow an agent to work on it remotely. Another engineer could inspect the resulting changes. A senior engineer or administrator could approve an operation requiring additional privileges. The work does not have to remain attached to the laptop or terminal where it started.

Sessions can also move execution to paired devices or cloud workers while maintaining the broader workspace.

For enterprises experimenting with long-running agents, that is significant. Persistent agents need mechanisms for shift changes, escalation, supervision and ownership transfer. Otherwise, organizations simply create fleets of personal agents whose state disappears into individual user environments.

OpenClaw is attempting to turn that state into collaborative infrastructure. Already, some teams outside the developers of the open source project are adopting it.

Colin Johnson, CEO of marketing metrics software firm Solvely, described a similar shift in his own development workflow in a post on X.

His team had already been using OpenClaw agents through Discord, where developers could assign tasks, run commands and interact with their development environment. But he said that model still felt like “messaging a bot”: developers could share access to an agent without actually sharing the agent’s working context.

The new multiplayer WebUI changed that, he wrote, because two developers could open the same live session, see the same history and artifacts, and add information without first exporting or reconstructing what the agent had already done. “We were working inside the same context,” Colin wrote.

In one example, another developer was taking over a project he had been working on; instead of preparing a traditional handoff document, Colin joined the developer’s existing agent thread and added the missing project context directly. “The session itself became the handoff document,” he wrote.

For enterprise teams, that is a useful illustration of why persistent multiplayer sessions may matter beyond convenience: agent context can become a shared work artifact rather than information trapped inside one employee’s private conversation.

Colin’s deployment also illustrates both the enterprise potential and the remaining security boundary. His team runs its OpenClaw Gateway on a development server reachable through GitHub authentication, Cloudflare Access and a Cloudflare Tunnel, with the Gateway itself listening only on the server’s loopback interface rather than an exposed public port.

But he explicitly cautioned that this does not make the shared Gateway a multitenant environment. The developers already trust one another with the repositories, tools and agent capabilities behind it. As he put it, Cloudflare controls who can enter the workspace, while OpenClaw tracks who created, owns or contributed to the work; stronger separation still requires separate infrastructure.

Security becomes much more enterprise-oriented

That shift creates a corresponding security problem: a shared agent can potentially act with broader organizational authority than one running on a developer laptop.

OpenClaw 2.0 responds with considerably more granular controls.

Approvals can now be tied to a specific request, command, session and person. Command permissions can be constrained to specific arguments and working directories. For script-backed execution, OpenClaw can verify that the script being executed still matches what was originally reviewed.

Sessions can operate under different permission levels, including read-only, guarded, workspace and full-access modes, with the highest level restricted to administrators.

Organizations can also define operator roles that require sandboxed execution for sessions created by specific identities. OpenClaw says those requirements cannot be bypassed using elevated execution or host overrides; if the required sandbox cannot be provisioned, execution fails rather than silently falling back to the host.

Credentials receive additional protection.

OpenClaw’s team-scoped Secret Store distinguishes protected secrets from ordinary environment data available to the agent. For supported requests, a protected credential can be substituted into a Gateway-hosted HTTPS request without exposing that credential directly to the model.

OpenClaw can also reference external systems including 1Password and Vault.

Auditing has expanded around execution identity, approvals, session actions and outbound messages. Plugin installation can trigger capability reviews associated with the specific artifact being installed.

Those controls address questions enterprises inevitably face when deploying agents: Who initiated an action? Which agent performed it? What resources could it access? Who approved the operation? And what happens to those permissions when work moves between people or machines?

NanoClaw still takes a different approach to security

OpenClaw’s changes also make the comparison with open source, enterprise-friendly rival NanoClaw more nuanced.

NanoClaw is one of several subsequent projects to emerge around the idea that AI agents need stronger isolation and simpler security boundaries. Its architecture places operating-system-level containment at the center of the design.

NanoClaw runs agents inside Docker containers, limits those containers to explicitly mounted filesystems and runs their processes as an unprivileged user. Sessions and agent groups can remain isolated rather than automatically sharing files and conversation history.

Its credential architecture follows the same principle. Supported outbound requests can pass through OneCLI’s Agent Vault, allowing credentials to be injected by a gateway rather than placed inside the agent container itself. NanoClaw also provides an optional egress-lockdown mode that puts agents on an internal Docker network and routes supported external traffic through the gateway.

OpenClaw 2.0 can now reproduce many elements of that hardened model. It supports Docker and Podman sandboxes, per-agent and per-session sandbox scopes, configurable read-only or read-write workspace access, role-enforced sandboxing, remote execution nodes and disposable cloud workers.

The key difference is the starting posture. OpenClaw’s documentation explicitly says sandboxing and execution approvals are off by default. Its baseline configuration assumes a trusted single operator and permits host execution unless administrators configure stronger restrictions. NanoClaw makes isolation more fundamental to how agent execution is structured.

So does OpenClaw 2.0 have security parity with NanoClaw?

In terms of available controls, it is much closer than before. In terms of defaults and architectural philosophy, no. An enterprise can configure OpenClaw into a substantially hardened environment, but it has to make that decision deliberately.

One Gateway is still one trust domain

Another limitation is particularly important for larger organizations. OpenClaw says a Gateway should be treated as a single trust domain.

Its new multi-user permissions are designed to govern collaboration among trusted users. They should not be treated as hard isolation between mutually untrusted tenants.

For organizations requiring stronger separation — between business units, customers or other security domains, for example — OpenClaw recommends separate Gateway instances, described as “cells,” with separate state, credentials and workspaces.

Fleet tooling for managing those cells remains experimental.

That distinction could matter significantly for enterprises considering OpenClaw as a centrally operated service.

Role-based access inside one Gateway may be sufficient for a trusted engineering department or internal team. It is a different proposition from a multi-tenant platform intended to isolate customers or users who should be assumed hostile to one another.

NanoClaw has its own configuration requirements and limitations, and even its stronger outbound-network lockdown remains optional. But its smaller architecture and container-centric execution model may appeal to organizations that want a narrower security boundary that is easier to reason about.

OpenClaw is optimizing for a broader problem.

OpenClaw’s biggest advantage may be the control plane

The tradeoff is product breadth.

NanoClaw emphasizes a relatively small codebase, container isolation and customization through code and skills. Its second-generation architecture supports owner, administrator and member roles, and a separate monitoring dashboard can provide visibility into deployments.

OpenClaw 2.0 is trying to build a much broader operational environment.

Its Control UI combines employee interaction, live execution, files, approvals, terminals, code review, model-provider configuration, devices and shared sessions.

That gives OpenClaw a potential advantage for enterprises that need not only secure agent execution but a usable control plane around it.

Security teams care about isolation. Platform teams also need deployment, authentication, model configuration, auditing and policy enforcement. Employees need an interface they can actually use. Managers need a way to understand what is running. Developers need access to the underlying files and tools when something goes wrong.

OpenClaw 2.0 increasingly tries to serve all of those constituencies through one system.

What is OpenAI’s role?

OpenClaw says 933 contributors, including 569 first-time contributors, participated in the release, which includes more than 16,000 pull requests — roughly half of all pull requests ever merged into the project.

Interestingly, the release was not shared by Steinberger’s employer, OpenAI. Recall that the Austrian developer announced on Feb. 14, 2026 that he was joining OpenAI to work on bringing agents to a broader audience, a move OpenAI CEO Sam Altman publicly confirmed the following day.

But OpenClaw was not folded into OpenAI. Steinberger said at the time that OpenClaw would move to a foundation and “stay open and independent,” while OpenAI would support the project. OpenClaw now says it is stewarded by the OpenClaw Foundation, an independent 501(c)(3), with OpenAI listed alongside Microsoft, GitHub, NVIDIA, Atlassian, Tencent and other organizations as partners.

Based on the available public information, OpenClaw 2.0 should therefore be understood as an OpenClaw Foundation release, not an OpenAI product or OpenAI software release, despite Steinberger’s employment at OpenAI and OpenAI’s financial and organizational support for the project.

Enterprise readiness now depends on configuration

OpenClaw 2.0 does not eliminate the security risks associated with autonomous agents, and its own documentation identifies limitations.

Secret Store values, for example, are not themselves encrypted at rest and rely on filesystem protections. Protected credential substitution does not cover every possible execution path, including some raw sockets, containers, remote nodes and provider-native harnessesIts multi-user permissions are collaboration controls, not hostile-tenant isolation.

Those caveats should prevent enterprises from interpreting OpenClaw 2.0 as secure-by-default agent infrastructure.But they also illustrate how much the conversation around the project has changed. The relevant comparison is increasingly not simply OpenClaw versus NanoClaw. It is a container-first, constrained system such as NanoClaw versus a deliberately hardened OpenClaw deployment that provides a substantially broader employee and administrator experience.

NanoClaw retains a strong proposition for organizations prioritizing a small attack surface, container-first execution and architectural simplicity.

OpenClaw is making another bet: that enterprises ultimately need an agent platform to function as both runtime and workplace.

OpenClaw 2.0 provides many of the primitives needed to build that environment — sandboxing, permissions, protected credentials, approvals, identity, auditing and isolated deployments — alongside a browser interface designed to make the system accessible to employees who will never configure an agent from a terminal.

The remaining caveat is important: enterprises have to turn those primitives into policy. OpenClaw 2.0 doesn’t automatically make OpenClaw enterprise-ready, but it does make an enterprise-grade OpenClaw deployment far easier out-of-the-box.

And as Steinberger’s description of OpenClaw’s own development process suggests, the long-term ambition may be larger still. Rather than giving every employee another AI assistant, OpenClaw is positioning the agent itself as shared infrastructure — a persistent layer where people, models and compute collaborate on the same work.

When Donkey Kong 64 debuted on the Nintendo 64 in 1999, Rare sent five Kongs on a quest to reclaim a thousand Golden Bananas, recover stolen riches, and deliver one very long rap. Rainchus, Ballaam, Killklli, Umed, and collaborators released DK64 Rekongpiled, also known as DK64 Recompiled, and the campaign now runs as a regular Windows, Linux, or macOS. You still need to point the software at a legally dumped US cartridge image. No assets are included with the download. After selecting one file, the original game code is executed on your computer rather than within an emulator.

Static recompilation is the way to go, as Wiseguy’s N64 Recompiled project works by reading ancient machine code, converting it to C code, and then compiling that C code for newer CPUs. RT64 handles frame drawing, allowing for higher resolution, refresh rate, and screen form than the original N64; it is no longer stuck in the 1990s. Gameplay speed stays the same even when the picture updates far faster than 30 frames a second. Objects, terrain, scrolling textures, screen effects, and the HUD all follow the higher rate. Default output matches the monitor’s refresh. An in-game slider handles the cap, because outside limiters can introduce stutter.

LEGO Super Mario Donkey Kong Arcade 72051

• BUILDABLE ARCADE CABINET – Relive the fun of playing an iconic arcade game with the LEGO Donkey Kong Arcade (72051) building set for adults ages…
• AUTHENTIC ARCADE GAME DETAILS – Create a Donkey Kong arcade level featuring Jumpman, Donkey Kong and Lady, including iconic details like the…
• WORKING JUMP AND DODGE PLAY – Pull the lever on the left side of the base to release one barrel at a time, then move Jumpman with the joystick and…

Widescreen and ultrawide layouts operate with any aspect ratio, and the effects are adjusted so that everything fits properly on a wide panel. The HUD elements on an ultrawide display can still be restricted to a 16:9 block. Any graphical flourishments that only make sense in 4:3 are left alone to avoid looking janky. The draw distance is significantly greater than it was on the original console, which is especially handy in the jungle and factory levels, which were typically packed. Cut scenes have also been revamped to take over the entire screen rather than being contained within a box.

Finally, the controls feel current. The keyboard and mouse are cleanly mapped. Controllers perform as intended. Gyro aiming is, as expected, an option, with a 1.0.One patch solved an issue that caused the axs to flip at once. You may configure the stick deadzones and axis inversion in a simple menu that saves your preferences across sessions. Input delay is kept to a minimum, so bonus games no longer seem like they’re up against the hardware.

System requirements are fairly modest. You only need a GPU that supports Direct3D 12 Shader Model 6 or Vulkan 1.2, which is pretty much any GPU built in the past 15 years or so. This comprises a GeForce GT 630 from 2012, a Radeon HD 7750, and an Intel HD 510 class GPU. If you’re using an x86 system, you’ll also require AVX. Just make sure your drivers are up to date. The 1.0.1 patch, released on August 29th, 2026, fixed a crash on an AMD Radeon 9070 XT running Windows.
[Source]

“The open ADB port plays the central role,” Plume researcher Gergely Eberhardt wrote in an email. “Combined with root access, a single pm install command can silently install any APK. This bypasses every one of Android’s default protections at once: signature verification, the “unknown sources” restriction, the permission-review dialog, and Play Protect scanning.”

Intruders at gates

The open ADB, along with the default presence of apps that have built-in proxy functionality, creates a dangerous mix that makes SuperBox a potent threat.

“This combination results in further infections involving additional residential proxies or IoT botnets, and the attackers are often the very customers of the primary proxy network,” Plume wrote. “The device owners get multiple bots they never asked for and are not aware of, all competing for the same hardware, and an IP address whose reputation now reflects whatever those bots utilize it for.”

Some of the proxy networking services that make use of SuperBox take measures to prevent their customers from accessing the local networks of SuperBox users. The recently disrupted Popanet, for instance, blocks local IP address ranges from outside the local network. Even then, Popanet users can access local IPs by specifying the special wildcard address 0.0.0.0, which Android then routes to the SuperBox IP 127.0.0.1. From that vantage point, proxy users can access the rest of the local network.

Monday’s post also reported that even the Popanet network was facilitating live exploit attempts. Plume wrote:

The internal-network protection issue that we described in the previous part isn’t just a theoretical concern. To confirm whether anyone is actually exploiting it, we ran a controlled experiment. We joined the Popanet network as a residential exit node and instructed the host that any connection coming through the tunnel targeting either port 5555 or 5858 (these are the most common ADB ports) would be redirected to our local honeypot. From the operator’s perspective, our node looked like any other regular residential endpoint serving customer traffic; from the inside, every attempt aimed to reach an ADB port through our node was captured.

We let the node run for over three weeks; over that period, the honeypot recorded 1,352 distinct attempts at reaching the ADB through the gap we identified earlier. All the attacks could be split into two families of loopback addresses targeting the local machine. The first is 0.0.0.0, supplied either as a raw address or embedded in a hostname via a wildcard DNS service such as nip.io. The second is 127.0.0.1, which the proxy blocked via isLoopbackAddress() as we explained earlier.

An email sent to info@mysuperboxtv.com seeking comment didn’t receive a response before this story’s publication.

from the tiny-little-coffins dept

When we just discussed the two recent deaths in Pennsylvania that came as a result of measles infections, we noted that there was very little information about the deceased. Some additional information has since been released, in particular the fact that one of those that died was a newborn child. This is the sort of fact that is heartbreaking to those of us with normal, functional brains.

Or, if you’re RFK Jr., it’s the kind of fact that causes you to drop the whole facade and go full on anti-vaxxer conspiracy clown.

On Tuesday, as news of the two deaths was breaking, Kennedy took to his personal X account to rail against the measles, mumps, and rubella (MMR) vaccine and posted a link to The HighWire, a hardline anti-vaccine and conspiracy site run by Del Bigtree, a prominent anti-vaccine propagandist and Kennedy ally.

Kennedy’s post also assailed Pennsylvania Governor Josh Shapiro, who has criticized Kennedy’s anti-vaccine rhetoric and activism. Kennedy went on to blame national declines in vaccination rates on the Biden administration.

On Wednesday, as news broke that one of the deaths in Pennsylvania was in a newborn, Kennedy turned to his official X account as US health secretary to allege that “the deaths may even have been altogether fabricated by one of the Governor’s hopeful staffers.” He cited a tweet from Josh Parsons, a Republican commissioner of Lancaster County, who claimed there had been “zero measles deaths” reported in the county. The claims appear to be another old play from the anti-vaccine handbook.

Advertisement

Okay, deep breath, folks. Let’s start that reacting to two bodies that haven’t even gone fully cold yet by spinning out on a conspiracy theory rant about the very damned thing that could have saved them is roughly as reprehensible a thing as I could think up in my head. It’s mean. It’s heartless. It’s evil. There are people suffering right now, including people that recently lost a newborn child, and there is no quarter given by Kennedy to express sympathy for any of them. Instead, it’s right back to the pet conspiracy theories that have been debunked over and over again. I don’t need to hear from anyone ever again that Kennedy is somehow not an anti-vaxxer, or that he actually promotes the use of the MMR vaccine.

But now let’s hone in on the claim that the reported deaths may have been “altogether fabricated.” Due to the coroner’s statement that they had measles deaths in the county, you may have read that as a claim that nobody actually died here and somehow state officials were just making the whole story up. That’s not the case. The game of confusion that Kennedy is playing is much more subtle and, ultimately, stupid.

If you recall back during COVID, there were plenty of misinformation acts out there on the internet claiming that COVID death counts were inflated. Much of that was based on what the cause of death listing was on death certificates. “No, this wasn’t a death from COVID,” the bad actor would claim. “This person is listed as having died from pneumonia.” The spoiler here is that COVID causes pneumonia that wouldn’t have occurred but not for COVID.

The same trick is at play here and it’s a trick Kennedy damned well knows is bullshit. The newborn in this case died from a ruptured spleen. That was the listed cause of death. But the cause of the ruptured spleen in a newborn that was also infected with measles is, well, measles.

Paul Offit, a vaccine and pediatric infectious disease expert at Children’s Hospital of Philadelphia, clarified that the measles virus can be passed on in the womb or shortly after birth. The virus can cause the spleen to enlarge and rupture at birth. Offit urged that if measles wasn’t the cause of the baby’s ruptured spleen, the coroner should provide an alternative explanation.

Unlike Diamantoni, Offit said he had been in touch with state officials regarding the deaths and, based on the information he had received, he concluded that “these patients would not have died were it not for measles.”

You can think of it this way. A death certificate or doctor’s report is going to list an acute cause of death, but that may not be originating and overall cause that led to the death. This is also how AIDS works. Nobody dies acutely from AIDS. They die from illnesses that wouldn’t normally have killed them if their immune systems weren’t severely compromised from AIDS.

Would it make sense to downplay the significance of AIDS? Of course not! AIDS is still the root cause of the death, even if it doesn’t make sense to list that on a death certificate.

Again, Kennedy knows all of this. He’s playing misinformation games on top of the graves of two Americans he helped into their caskets, including an infant. There’s a level of callousness at play here that is at best near-sociopathic.

From, mind you, the person that has the American people’s health as his charge.

Filed Under: anti-vaxxers, health & human services, infectious diseases, josh shapiro, measles, mmr vaccine, rfk jr.

Solar Team Eindhoven drove its solar ambulance Stella Juva more than 800km across Kenya with Amref Health Africa, and found it generated more energy than it used while running an X-ray machine, ultrasound scanner and vaccine fridge at a clinic with no electricity. The vehicle is returning to the Netherlands and funding is the obstacle.

A solar ambulance built by Dutch students drove more than 800km across Kenya and made more electricity than it used. Amref Health Africa ran the test with them.

It is not an ambulance in the usual sense. It carries an X-ray machine, an ultrasound scanner and a refrigerator for keeping vaccines cold, and it goes to the patient rather than the hospital.

The builders are 23 students from Eindhoven University of Technology and two other institutions, Digital Trends reported. The vehicle is called Stella Juva.

The route mattered more than the distance. It included hours on dusty clay roads and a clinic at Mosiro in the Narok region, which has no electricity at all.

The finding is the useful part. Parked, with every piece of medical equipment running at once, it generated more energy than it consumed.

“Stella Juva reacted even better than we had expected,” said Isabella Wanningen of Solar Team Eindhoven. Panels on the roof charge it while driving, and more fold out when it stops.

No patients were treated during the trial. The team and Amref estimated that around 200 people could have been seen over two days.

This is not the team’s first long test. TNW followed an earlier Eindhoven solar car through 1,000km of desert in Morocco.

The lineage runs further back than that. The team has been building solar vehicles since 2013, and five alumni went on to found Lightyear.

That company is the cautionary half of the story. It halted production of its €250K solar car to concentrate on a cheaper one.

Stella Juva now goes back to the Netherlands. The obstacle is not the engineering, it is who pays for the next one.

Europe has money pointed at roughly this. The Global Gateway package commits at least 2.625B euros to health in Africa, across vaccines, manufacturing and health systems.

None of it is aimed at a vehicle. A student team has shown the clinic can drive to the patient, and nobody has a line for that.