Matrix OSMatrix OS

Apps

Use built-in Matrix OS apps and ask your agent to create new tools for your work. Learn how apps run and how to inspect the results they produce.

Maintained by the Matrix OS team. Product instructions are updated with the supported workflow.

Apps contains the personal web apps installed on your Matrix computer. Some are built in. Others can be created by Matrix in Chat when you describe what you need. Creating an app keeps it in your workspace; it does not publish it.

You do not need to write code to get a useful app. Ask for the outcome, review what Matrix builds, and keep using or improving it.

Public website deployment is available from a current Matrix runtime. See Publish an app as a website for public URLs, visitor forms, and owner submission controls. This is separate from marketplace distribution.

For organization members using the same live records, see Build a collaborative app. You can create a new team app or adapt an existing one while preserving its saved data.

Apps are real tools

Matrix apps can have multiple screens, forms, tables, charts, and saved state. Start with Web Canvas, Web Desktop, or Electron Desktop, where supported apps can use the Matrix database bridge. Review the result before relying on it.

Where Apps Work

Web Canvas, Web Desktop, and Electron Desktop support apps that use the Matrix database bridge. Web Mobile is the phone-browser presentation of your workspace; check that each app fits the smaller screen.

Native Mobile is in early access. Its Apps screen lists installed apps and can open web previews, but it does not yet provide the Matrix database bridge used by these apps. A preview opening on a phone does not establish that records save or reopen correctly. Use Web Canvas, Web Desktop, or Electron Desktop for apps that depend on that bridge until native app data support has been tested and released.

See Web Mobile and Native Mobile for the distinction.

Shared app capabilities are awaiting release

The updated app bridge is being prepared for Web Canvas, Web Desktop, Electron Desktop, Web Mobile, and Native Mobile. It adds shared connected-service access, supported AI completion routes, and native app database requests. These capabilities require matching runtime and client releases. The current Native Mobile limits above remain in effect until that release has been installed and verified.

What You Can Build

Personal Trackers

Habits, budgets, subscriptions, workouts, medications, books, recipes, home inventory, travel plans, and routines.

Work Tools

Lightweight CRMs, task boards, invoice trackers, meeting follow-ups, project dashboards, checklists, and internal request forms.

Creative Tools

Content calendars, script planners, moodboards, portfolio managers, campaign trackers, idea libraries, and publishing checklists.

Learning Tools

Flashcards, study planners, reading notes, spaced repetition helpers, class dashboards, and quiz apps.

Family And Life Admin

Chore boards, shared plans, event lists, meal planning, school reminders, moving checklists, and emergency info.

Games And Fun

Simple games, puzzles, party tools, scorekeepers, interactive stories, and custom dashboards for hobbies.

Built-In Apps

Matrix ships with a growing set of default apps, including:

  • Notes and writing tools.
  • Task and board-style planning.
  • Profile and social surfaces.
  • Calculator, clock, weather, Pomodoro, and utility apps.
  • Games such as Solitaire, Chess, Backgammon, Snake, 2048, Minesweeper, and Tetris.
  • Whiteboard and visual workspace tools.

These default apps are bundled into the Matrix host bundle so every user starts with a useful workspace.

Utilities groups everyday text, data, PDF, image, and developer tasks in one searchable app. It is included in the upcoming Utilities runtime release; some advanced tools open on the free-tools website. Its working sessions are temporary, so copy or download results before closing it.

Asking Matrix To Build An App

Good app requests include:

  • what the app is for;
  • what information it should track;
  • what views you want;
  • whether it should be simple or polished;
  • any style preferences;
  • whether it should use connected services.

Examples:

"Build me a budget tracker with monthly totals, categories, recurring expenses, and a simple chart."

"Create a CRM for my wedding photography leads. Track client name, event date, budget, status, notes, and next follow-up."

"Make a study planner for my biology exam with flashcards, topics, confidence ratings, and a review schedule."

"Build a family chore board with recurring tasks, assignees, points, and a weekly summary."

Connected Services And AI

Apps can be designed to work with a connected service, such as Google Drive, and use a supported AI route for summaries or other generated text. The shared capability update described above must be released before relying on the same behavior across all five presentations.

Connect an account to Matrix once. Visible personal apps built for you by Matrix can use that connected service immediately; there is no second authorization step for each trusted app. The app still discovers the actions currently exposed by the connection and must select the intended account instead of guessing when several accounts are connected.

You can apply an owner restriction to limit or revoke a trusted app's integration access. Imported, community, shared, hidden, or otherwise untrusted apps do not inherit connected services automatically. Provider consent, account scopes, and Matrix's existing safeguards for important actions continue to apply.

Matrix keeps service credentials and AI credentials in the trusted host and gateway. Apps use Matrix's bridge; they should never ask you to paste Google access tokens, provider keys, or your Matrix sign-in token into app code.

A useful request is:

"Build a reading app for my Google Drive project folder. Use my selected Drive account, discover the supported read actions, and let me choose an available AI route for summaries. Check loading, saving, and errors on Web Canvas, Web Desktop, Electron Desktop, Web Mobile, and Native Mobile."

Discover What Is Available

The builder must inspect the actual connected accounts, supported actions, and action parameters. A connected OAuth account does not guarantee that every action or document format is supported. Drive folder listings return file information; reading text may require a separate supported read or export action. Apps must also handle pagination and files that cannot be previewed.

For AI, the app must discover the owner's available completion routes and use the selected harness, account, access source, and model. A saved account or model name alone does not establish that a route can run. Disabled, unsupported, or otherwise unrunnable routes stay unavailable; the app must report that state without silently switching accounts or models. Managed AI calls remain subject to Matrix eligibility, model policy, and available funding.

When A Connection Does Not Work

Ask Matrix to inspect the app's launch, trusted app identity, runtime/client versions, connected account, required action, and any owner restriction. An app should show a clear unavailable or access-denied state and preserve any local edits when a request fails. A connection working in an app does not by itself establish access in the active Chat harness; Chat has its own authorization and tool wiring.

For developers, the shared app API exposes MatrixOS.capabilities(), integrations(), describeService(service), and service(service, action, params, label). MatrixOS.ai.routes() discovers completion routes; MatrixOS.ai.generate({ prompt, route }) returns a { text } result when the chosen route is supported and authorized. The older MatrixOS.generate(context) submits a Chat task and does not return a completion. Test these calls through a real Matrix app launch, including denied and unavailable cases.

App Data

Supported apps in Web Canvas, Web Desktop, and Electron Desktop can save structured data in your Matrix database. You do not need to manage the database yourself. Check saving and reopening with a sample record before adding important data.

When an app needs tables, Matrix records them in the app manifest and the gateway creates schema-per-app tables in the Postgres database inside your Matrix environment. Apps access that database through Matrix's bridge API, not by handling database passwords directly.

This means:

  • app data persists across reloads;
  • apps can have real lists, records, filters, and charts;
  • recovery can restore app data from snapshots;
  • app permissions and access can be enforced by Matrix.

Improving An App

You can keep iterating in plain language:

  • "Add a dark mode."
  • "Make the mobile layout cleaner."
  • "Add a status filter."
  • "Import this CSV."
  • "Add charts by month."
  • "Make it easier for my team to use."
  • "Change the labels to match my business."

Matrix can inspect the app it created, update the files, rebuild it, and keep the app in your workspace.

Matrix App Gallery is planned curated discovery for Matrix apps. The first release is intended to focus on reviewed, first-party examples. It is not yet a production public publishing or installation flow.

Your owner-built apps stay private by default. Creating an app does not authorize a public listing, demo, or access to your connected accounts. Owner-consented public listings, free community distribution, and paid creator apps are separate later steps. See Matrix App Gallery for the current scope.

For Developers

Developers can still inspect and edit app files directly. First-party apps live under the Matrix home as Vite + React projects with matrix.json, index.html, src/main.tsx, and vite.config.ts. For most users, Matrix handles those details automatically.

How is this guide?

On this page