Meta Launches Muse AI Agent That Handles Tasks Autonomously, From Emails to Negotiations

·1 views

Meta introduced Muse in early September 2026, a personal AI agent designed to go beyond answering questions by actively performing tasks on a user's behalf, including sending emails, booking reservations, making purchases, and negotiating prices. Unlike conventional chatbots, Muse continues working in the background even after the user closes the app, managing both quick one-off tasks and long-term multi-step goals. The agent operates within a dedicated Linux virtual machine called Muse Secure VM, hosted on Meta's cloud infrastructure, giving each user an isolated environment for their data and agent activity. For payments, Muse uses Stripe's Link system to generate single-use virtual card numbers per transaction, ensuring the user's actual card details are never exposed to the agent. A separate security process called Sentinel acts as the sole gatekeeper for all outbound connections, with user consent requests sent directly to the user rather than through the AI model, specifically to guard against prompt injection attacks.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

LangGraph Multi-Agent Patterns: How to Build Supervisor-Worker Graphs Safely

LangGraph allows developers to build multi-agent AI systems as explicit directed graphs, where nodes are Python functions, edges define transitions, and a shared typed state flows through every step. A common pattern is the supervisor-worker model, where a central supervisor routes tasks to specialized agents such as a researcher or coder before deciding when to finish. Developers are warned that a hard step-limit counter is essential, as a supervisor that never outputs a stop condition can silently exhaust API budgets. For tasks that can run independently, LangGraph's Send primitive enables true parallel execution, with results automatically merged via Python's operator.add annotation before an aggregator synthesizes them. The article highlights that using a plain list annotation instead of the annotated reducer silently drops parallel worker results, making correct state typing a critical pitfall to avoid.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How iOS Developers Should Prepare Apps for Apple's Foldable iPhone Duo

Apple's anticipated foldable iPhone, referred to as the iPhone Duo, presents new UI and layout challenges for iOS developers. Unlike standard device upgrades, a foldable display dynamically changes the available screen space, making hardcoded dimensions and fixed layouts problematic. Developers are advised to shift from designing for specific screen sizes to building responsive, adaptive interfaces that adjust based on available space. Key areas to address include safe-area handling, flexible navigation patterns, and avoiding portrait-only or narrow-display assumptions. Experts recommend a screen-by-screen audit of existing apps to identify where fixed layouts may break before undertaking broader development work.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

ArchSpec gem enforces Rails architecture rules in CI to catch AI-generated code violations

Rails development teams are increasingly using AI coding assistants like Cursor, Copilot, and Claude, which generate code quickly but often ignore project-specific architectural conventions. ArchSpec is a new Ruby gem that lets teams encode their architecture rules in a file called Archspec.rb, defining what each layer of the application can and cannot do. These rules are then checked automatically in CI pipelines, causing pull requests to fail if any violation is detected, regardless of whether the code was written by a human or an AI. The tool uses Rubydex and Prism to index Ruby source files statically, meaning it never boots the application and delivers fast feedback. Currently at version 1.1.0, ArchSpec requires Ruby 3.2 or higher and is released under the MIT license.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer connects personal Next.js portfolio to GitHub, Hackatime, and Sanity APIs

A developer recently upgraded their Next.js 16 personal portfolio by replacing hardcoded placeholder content with live data from three real APIs. GitHub's GraphQL API was used to fetch pinned repositories, since the REST API does not expose manually pinned repos. Hackatime, an open-source WakaTime fork by Hack Club, was integrated to display real coding hours and language statistics on the about page. Sanity, a headless CMS embedded within the Next.js app, replaced a static blog array and now allows publishing posts without touching code. Key lessons from the process included the necessity of GraphQL for GitHub pinned repos, the importance of API response caching to avoid rate limits, and a non-obvious CORS flag required to prevent an infinite login loop in the Sanity Studio.

0 comments Read more at DEV Community