I’d be willing to bet Amazon makes more money when you use the app. Grocery stores make more money when you walk the cash wrap. Airlines make more money when they scare you into buying insurance. Dark design patterns and consumer usage data make money. They don’t want to give that up for some chat bot deciding what the cheapest red shoes are

I led engineering at Google DeepMind. Today, I'm proud to introduce Fo to give personal AI something no lab ever has... Humans. Other personal AI's pretend AI can do everything. Fo employs humans to do tasks that AI cannot. - 2x better at real-world task completion (beats other agents by 69%) - 94% trust rate (4x less likely to leak private info vs Muse, Instinct) Sign up for free: wajo.ai/join-wajo

I’ve seen a couple of posts about this so wanted to demystify. Today, every Muse user gets a free computer in the cloud. It's a real computer, and we’ve designed the security architecture of the Muse Secure VM carefully so you and your Muse can do almost anything you could with a computer sitting under your desk while keeping you and the system safe from threats like prompt injection. We wrote about this at length in our security blog post – security.muse.ai. Activity in the “runtime cell”, which you share with your Muse is unfettered, but sensitive actions are all overseen by the Sentinel, which runs outside of that cell. Similarly, all sensitive secrets - like the passwords you enter into Muse’s secure credential storage - are also stored outside the runtime cell. The runtime cell gets its own root filesystem (including a full Ubuntu linux image) separate from the host filesystem where your other more sensitive data lives. Because it is isolated from the sensitive stuff that runs on the same box, this means that we can, and do, offer users full visibility and control over the files in the runtime cell. Just as you can when you install Linux on your home computer, you can poke around and see all the files that make the system work - both debian system files and the binaries and data files that implement the parts of Muse which run in the runtime cell. This was a very deliberate choice - your Muse Secure VM truly is your own computer in the cloud. You can install software in it, write and compile code, use the browser to surf the web: it is your own Linux box that you can operate as you choose with your Muse. Poking around in this computer doesn't give you any privileged access to Meta infrastructure, or to other people's data If I may geek out a little here for a second… As a kid I loved to take things apart to see how they worked. As a teenager I got into computers and soon found myself drawn to C:\WINDOWS\SYSTEM and the system registry, later Slackware’s /dev/, /proc/ etc – I could see how the system was laid out and as I explored what DLL files and .so files actually did, I gradually became able to meld the computer to my own will. We’re really proud to be able to put a real computer in millions of people’s hands with a similar level of transparency. We built a file explorer right into the Library tab of the UI. We want you to be able to see the markdown files Muse writes while it thinks about how to serve you better, and explore the internals of the system if you’d like to. So, when you ask your Muse to show you its entire filesystem, and receive gigabytes of files you’re seeing the full contents of the runtime cell. It’s yours to explore and enjoy! If you’re not a geek like me, or simply want to download the data that you personally have created directly with your Muse, we added a feature for that too in Settings > Data controls > Download your agent data.

what if copy/paste was smart? powered by @typesafeai jev it feels like every computer interaction will get rewritten

The argument was always “no way will they waste time vibing their own version” but when their own devs have nothing to do because Claude is already set up to fix, merge, deploy… folks are gonna start looking for other things to do to justify their roles.

We’re open sourcing dbt Charts. Build interactive dashboards in YAML, keep them alongside your dbt models in Git, and give humans + agents the same development workflow. See what we’re building and learn more at #dbtSummit: dbtcharts.com/blog/charts-bu…

Claude Managed Agents can operate in a sandbox you control, on your own infrastructure or with any provider you choose. Today we added new guides for @blaxelAI, @e2b, @googlecloud, @namespacelabs, and @superserve_ai, so you can choose the best fit for your use case.