What changed

According to Replit's announcement, Replit created Amuse after challenging Replit Missions to replicate a leading personal AI assistant so users would not have to rent one or store memories, chats and logins on company servers. The project's changelog lists the initial public release as version 0.1.0, marked unreleased, and the announcement notes that Replit ran its Security Scanner to find and patch vulnerabilities before sharing the code.25

How it works

According to the README, builders can launch Amuse with Docker Compose, which bundles PostgreSQL and binds to 127.0.0.1, or run it from source with Node.js 22.9+, pnpm 10.26.1 and PostgreSQL 14+. The environment template defaults to gpt-6.2-sol for the main agent, gpt-6-luna for quick steps and gpt-image-2 for images, and lets operators set OPENAI_BASE_URL for a proxy or compatible endpoint. To curb API bills, the README says Amuse pauses background jobs and stops model calls at AMUSE_DAILY_LIMIT, which defaults to 2,000 usage units per day.13

In a typical browsing session, the security policy explains that Amuse injects saved credentials only into HTTPS authentication headers or password fields on the confirmed host, and scrubs secrets from page text before the model reads it. If the agent reads outside web content or email, it must ask before editing memory files or creating repeating schedules, which are capped at 20 active jobs running no more often than every 15 minutes.14

For local code execution, the security policy states that saved tools run inside a QuickJS WebAssembly sandbox with no network or filesystem access, a 64 MB memory cap and a 4 second time limit. Generated mini-apps, called spaces, render inside sandboxed frames with no same-origin access and cannot fetch external URLs or submit forms.4

The documentation highlights clear limits for builders. Because Amuse has no login, the security policy warns that exposing it beyond localhost gives anyone on the network full control of the agent and its credentials. The README adds that Amuse does not support MCP servers or phone push notifications, and that Chromium drops its own sandbox inside Docker unless AMUSE_BROWSER_REQUIRE_SANDBOX=1 is set. Finally, the security policy notes that prompt injection remains an open problem, so users must still review every approval card.14