Muse Spark Open -- weights releasing today -- runs great on new Mac Studios thanks to work with @johnternus and Apple.

introducing muse wonder our new frontier model. state-of-the-art at personal agents and professional agents. our largest and most capable model yet—rivals the big bois

Introducing Muse Wonder, our new family of frontier models with state of the art performance for personal and professional agentic work.

One problem with transitioning from AI chatbot to AI agents is when you want chat, but get task execution instead I’ve been trying to consolidate all my ChatGPT usage into starting with my dot…my hypothesis is I’ll end up pushing dot farther and find its real power. But there are some clear instances where using dot feels like a regression. When I want more of a conversational experience, dot is more terse as intended for this format. I found myself wanting the verbosity of regular chat. So much so that I toggled out to get a much better response. Personal agents have a different post-training shape than personal chatbots. I assumed the former would be a superset of the latter, but I’m beginning to suspect there may actually be more mutually exclusive tradeoffs that had to be made.

Today we’re announcing Personal Agent Protocol — an open standard @Meta and @SierraPlatform are developing along with industry partners at @Genesys, @instinct, @RocketOTD, @Shopify, @stripe, and @Walmart. It will help define how personal agents interact with businesses and is open for anyone to implement. Read more: sierra.ai/blog/introducing-p…

Got @Muse running on the PSP that's been sitting in our house for over 15 years @alexandr_wang Had my agent port the gadget client to C so it runs natively on the PSP. Hold R, talk into the built-in mic. Muse answers, and OpenAI gives it a voice

My Personal AI escaped the chat window into Reach Mini !! Muse X Reachy Mini using Muse gadget sdk ! And yes with a wake word ! PR soon !

🚨 side project alert 🚨 Announcing Muse Gadgets, an open source ESP32 firmware and Linux sdk so that you can make hardware devices that work with Muse. Grab an API token from gadgets.muse.ai and point your favorite coding agent at the github repo to build your own peripherals for Muse.

i'm obsessed with this idea of "vibe coding physical devices" right now even hardware noobs (like me!) can now finally turn our weird little ideas into gadgets that actually work you just describe the gadget you want, then schematik (basically cursor for hardware) picks the correct parts, writes the code to run them and walks you through building it. for example, here are 10 templates you can start with and make your own: 1. a plant that throws a disco a soil sensor warns you when it’s thirsty. water it and the LED ring celebrates with rainbow lights and a victory tune lol 2. a morning receipt printer turn it on and it prints today’s forecast onto a little paper briefing, with optional calendar events and blank lines for handwritten to-dos. 3. a digital hair clip a tiny wearable screen that displays your own messages. press a button to cycle through them. 4. a weather display that tells you what to wear checks the weather over wi-fi, then tells you whether to grab a jacket, umbrella, sunglasses, shorts or scarf. updates every 10 minutes. 5. a tiny desk companion tap its face to change expressions, tilt it to move its eyes, and swipe through the clock, weather and stock price. 6. a lamp you control with your hand swipe sideways to change color, up or down to change brightness. it saves your settings for the next time you power it on. 7. a pet treat dispenser press a button and it weighs the bowl before opening the gate. it blocks another serving if the bowl’s already full or the cooldown hasn’t finished. 8. a live flight radar a tiny round display that plots nearby aircraft and their callsigns, using live flight data fetched over wi-fi every 5 seconds. 9. a dedicated touchscreen chess game tap pieces to move and play against a small chess engine running on the device. the screen and processor are already on one board. 10. an air monitor for your room measures CO₂, temperature and humidity, then tells you when rising CO₂ means it’s time to air out the room.

51. joshelman.medium.com/51-7fbf…

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.