other / agent

OpenMuse

A self-hosted personal agent app for iOS, Android and web with an agent browser, an optional Linux terminal, files and Gmail and Calendar adapters.

Repository owner CopilotKit

Not rated yet
0 comments

Like 0 Save

Published 11 Oct 2026Listing updated 12 Oct 2026

At a glance

Purpose: A self-hosted personal agent app for iOS, Android and web with an agent browser, an optional Linux terminal, files and Gmail and Calendar adapters.
Runs in: Web service
Operating systems: Not stated
Needs: Runtime: Node 24 LTS and pnpm 11.19.0; Needs internet: Yes; Needs accounts or API keys beyond your agent: Yes
Files and data: Reads files: Yes; Writes files: Yes; Sends data to other services: Yes
Tool type: Agent
Delivery: From GitHub
Version: Latest on the main branch
Access: Code on GitHub
Compatibility: According to the README: Node 24 LTS and pnpm 11.19.0; iOS, Android and web clients, with Xcode or Android tooling for the native builds; model providers OpenAI, Anthropic and Google, with openai/gpt-5 as the default model; Gmail and Google Calendar through Google OAuth; Chromium through Playwright for the browser worker; Docker for the optional Linux computer and the compose route; and Render for the one-click deploy.
External costs: According to the README, every deployment needs a CopilotKit Intelligence project key. Intelligence is a separate service and the README gives no prices for it. A model needs a provider API key, with openai/gpt-5 as the default and Anthropic or Google as alternatives. Gmail and Calendar need your own Google OAuth client. The Render blueprint deploys an API service and a private browser service on the Standard plan with disks, plus a static web site, and the README states no prices. Web search uses Parallel's free, keyless Search MCP by default, and the README says free access is rate limited. Your coding agent or model provider may charge for usage.
Permissions: The README shows pnpm dependencies, CopilotKit login/project selection and Intelligence/model server keys. The README describes Playwright Chromium, persistent browser-worker profiles and human takeover. The README describes an optional Docker Linux computer with Docker CLI/engine access, a persistent workspace and bounded terminal commands. The README describes Render API, web and private browser services with persistent disks; the browser service and its API settings can be removed. The README says background tasks and recurring public-page checks run while hosted. The README says web search defaults on; WEB_SEARCH_ENABLED=false on the API and separate task worker disables it. The README describes Gmail and Google Calendar read access and separately granted write access, with stored review for each email send and calendar event creation, update or deletion. The README warns approved in-flight requests may finish after pause/cancellation.
Usage terms: MIT License, as stated in the repository. See its LICENSE file for the exact terms. The README adds that CopilotKit Intelligence is a separate service and is not included in this repository's MIT licence.
Interface: web

Code on GitHub

CopilotKit/openmuse

MIT

TypeScript4,772 stars652 forksLast pushed 13 Oct 2026 UTC

A personal agent with a browser, terminal, files, and work that keeps going built with CopilotKit and AG-UI.

Public GitHub data fetched 13 Oct 2026 UTC · 0 days old

View on GitHub ↗

What it does

The README describes OpenMuse as a personal-agent application with visible work, rich results and its own server, task worker and browser worker. The README labels it alpha for self-hosting and building on, with CopilotKit React Native clients for iOS, Android and web.

The README describes persistent Chromium and an optional Linux workspace for public-page browsing, container commands, files and PDF transfer. The README says users can take over the browser or terminal. The README lists task plans, approvals, receipts, recurring page checks, PDF form workflows, transaction CSV summaries, Gmail and Calendar adapters, and editable memories.

The README says the local sample needs no model, Google account or Docker, but conversation persistence requires a CopilotKit Intelligence project key in every deployment. The README says graphical desktops and autonomous checkout remain future work and voice is on the roadmap.

Who it is for

Developers who want to self-host a personal agent app or build on its source.

Example tasks

Send 'Complete the permission slip' in Chat, supply fictional form values and review the saved PDF and prepared reply.
Create a built-in availability watch under Goals and Track, then change the built-in test page to trigger an alert.
Use Try example transactions under Finance to create a spending tracker.
Start the browser worker and a model, ask the agent to check out Hacker News, then use Take control to open its session.
Connect Gmail or Google Calendar with your own Google OAuth client and review each send or calendar change.

Getting started

The README's quick start needs Node 24 LTS, pnpm 11.19.0 and a CopilotKit Intelligence project key. Clone the repository, then run pnpm install --frozen-lockfile and cp .env.example .env. Log in and pick a project with npx copilotkit@latest login and npx copilotkit@latest project select, and set CPK_INTELLIGENCE_API_KEY in .env to the generated key. Keep the generated CPK_TELEMETRY_ID too. Then run pnpm dev and, in another terminal, pnpm dev:web, and open the local web address the README gives. The README also describes a Deploy to Render button, a browser worker, the optional Linux computer, model setup and Google setup. The README has the exact commands.

Limitations

The README requires Node 24 LTS, pnpm 11.19.0 and a CopilotKit Intelligence project key; the README says Intelligence is a separate service outside the repository's MIT licence. The README says real model use needs a provider key, Gmail and Calendar need a Google OAuth web client and live credentials, the Linux terminal needs Docker, and the browser worker needs Chromium. The README says native clients require Xcode or Android tooling and the PDF reader needs an Expo development build; build scripts do not produce signed app binaries. The README labels the project alpha and describes a one-owner deployment protected by a shared key rather than multi-tenant authentication. The README advises HTTPS and restricted network access for remote hosting and keeping the default local-data mode on loopback. The README says background work needs a running host, PGlite cannot be opened by separate processes, and operators should run one API instance. The README warns that Render needs persistent disks for database, PDFs and signing keys, that a 512 MB process runs out of memory, and that its blueprint does not start the Docker computer or Google integrations. The README says an approved in-flight request may finish after pause or cancellation and uncertain external writes require outcome reconciliation before replacement. The repository can change at any time; check its README before you install.

Data practices

The README says the embedded database, documents and signing key default to .openmuse/, and browser profiles to .openmuse/browser-profiles/. The README says CopilotKit Intelligence stores conversation threads, provider keys stay on the server, and Google credentials are encrypted at rest. The README says model calls use the configured provider. The README says default web search sends model-generated queries and context that may contain conversation or task information, plus a random per-chat or task identifier, to Parallel. The README gives WEB_SEARCH_ENABLED=false on the API and any separate task worker to disable search. The README says the CopilotKit SDK sends runtime telemetry through a shared sink to PostHog, tagged OpenMuse, and defaults to full capture subject to explicit SDK opt-outs and sampling settings. The README says CPK_TELEMETRY_ID allows runtime usage to be associated with completed Intelligence signups, and points to docs/TELEMETRY.md for setup and opt-out details without naming opt-out variables in the README.