This page introduces Mini App features and use cases. See Capabilities and progress for version support and release plans.
What you can build
- Professional workspaces: bring material scattered across platforms into one page where people and the Agent move the work forward on the same data, like the official Stocks Mini App.
- Dashboards and monitors: pages that need filters, charts, and live refresh, such as Token usage, Git history, or session trajectories.
- Business system front ends: connect authorized apps such as Notion or Jira, create, edit, and delete on the page, and sync changes back.
- Planning and generation: chain maps, search, and image generation into one flow, like the road trip planner.
- Working with the Agent: prepare context on the page and hand it to the Agent, or start an Agent session and approve and answer on the page.
- Small tools and games: a Pomodoro timer, a notes board, a divination app, anything you want close at hand.
Interface and windows
Full web interface
HTML, CSS, and JavaScript with any front-end framework or chart library: tables, drag and drop, live refresh.
Opens in the session sidebar
Open it from the panel’s ”+” menu, with @ in a conversation, or by the Agent; the page appears in the current session’s right panel.
Open a specific page
open with a path opens any address inside the plugin, such as a record’s detail page.Pop-out window
Pop the page out of the file panel into its own window, with its position remembered; the manifest declares size, always-on-top, transparency, and click-through, which suits floating widgets. Switching modes may rebuild the page, so save state first; see Page rebuild hints.
Window handle
The page reads and adjusts its own pop-out window: mode, position, size, always-on-top, click-through. The interface may change, so feature-detect before use.
Devices
Camera and system notifications require MiniMax Code v3.1.9 or later.Microphone and speech-to-text
Record audio on the page and pass it to the host with
speech.transcribe for transcription; microphone access must be declared and enabled.Camera
Declare
deviceAccess: ["camera"] to access the camera stream through standard browser APIs; users can turn access off in the permission panel.System notifications
Declare
deviceAccess: ["notifications"] to send system notifications from the page and let users know when results are ready.Backend and data
Node backend service
Export
start(context); the host assigns the port and handles start and stop. Push live updates over SSE or WebSocket.Backends in any language
The Node entry can launch Python, Go, or other services and reverse-proxy to them from the assigned port.
Persistent data
The host isolates a
dataDir for each plugin; data survives service restarts and plugin updates.Apps the user authorized
Host Connector calls Notion and other apps with the account the user authorized in MiniMax Code; the plugin stores no credentials.
CLIs, HTTP APIs, SDKs, local files
The Node service can call local command-line tools, third-party APIs, or files the user authorized.
Unified tool entry
context.tool lists and calls the host’s mounted MCP tools and Connectors with one API, judged by the user’s permission rules for the Agent.Working with the Agent
The Agent calls your tools
Managed MCP: the Node service exposes business capabilities as tools, so the page and the Agent work on the same data.
Hand off to the message input
The page puts prepared content into the current session’s message input; the user confirms, edits, and sends it.
Start Agent sessions from the page
The page runs an Agent turn, streams the reply, and renders tool approvals and questionnaires itself.
Run the Agent in the background
The Node service uses
context.agent to work on tasks and write results back; set a concurrency limit and extra calls wait in line.Hand off to the chat panel
open(sessionId) shows a Mini App’s Agent session in the chat side panel, where you follow it, approve, and answer.Choose models and agents
List the models you can use and the agents you configured; switch a session’s model or start a session as a specific agent.
Sessions
A Mini App’s service is shared per plugin and its pages are per session; see Mini Apps and sessions for the full rules.Starts when referenced
As soon as a Mini App reference appears in the input, the backend starts; the sidebar expands only after the page opens.
One service for every session
Each session has its own page, all backed by the same service and the same data.
Reopening keeps your place
If the service hasn’t restarted, the page hasn’t reloaded, and no explicit
path is supplied, selecting or opening it again in the same session reuses the tab and keeps the current route and state.Session list indicator
The session list marks sessions that have a Mini App open.
Local sessions only
Cloud, SSH, and Remote Control sessions never start or open Mini Apps on your machine.
Survives sign-in changes
Refreshing sign-in credentials doesn’t affect running Mini Apps; after signing back in with the same account, list the tools again and continue.
Building and distribution
Create from one sentence
With /miniapp-creator, the Agent verifies data access, writes the page and backend, publishes, and opens the app.
Screenshot acceptance
The Agent checks structure, text, and interactions in the built-in browser and reports what passed and what couldn’t be verified.
Install a finished package
Hand a Mini App directory or ZIP to the Agent; it inspects and publishes it without running bundled instructions or installing dependencies.
Plugin marketplace
Official Mini Apps install, update, and uninstall through the marketplace; official packages can’t be edited locally.
Open-source community
Share through a pull request to MiniMax-Code-MiniApps; the team regularly selects apps for the marketplace.
Other capabilities in the same package
Skills, ordinary MCP, and Apps in the package keep working whether or not the Mini App is running.
Operations
Starts on demand
Enabling a plugin never starts it; up to 3 different Mini App services run at once.
Publishing that rolls back
Stage, install, and start happen in steps, and a failed install restores the previous version.
Status and diagnostics
inspect shows the source, runtime status, and diagnostics for the latest run without starting the service.Stop and restart
Stopping ends only the service and keeps the plugin and its other capabilities; the toolbar offers a restart from the failed state.
Traceable startup failures
Startup failures go into the runtime log and are packaged with your feedback report to help pin down the problem.
Permission panel
Switch each of a Mini App’s permissions on or off from the plugin detail page; on by default, and switching one off immediately restricts new calls without a restart.
Security
Port authentication
Each run gets its own credential, so only the Mini App page and managed MCP can reach the service port; no plugin code changes.
Plugins and pages never handle credentials
The host makes third-party calls on the user’s behalf; host credentials, internal ports, and tool references never reach the page.
Explicit grants
Connector providers, Agent access, always-on-top, and click-through work only when declared in the manifest.
User confirmation
Handing off to the input always needs confirmation; Agent approvals are only “allow once” and “deny”, and a Mini App can’t write the user’s global permission rules.