Platform Features
This page is the feature availability map. For what each client is and when to use it, see connecting to your agent.
How to Read This
All clients connect to the same conversations. The main split is management: hosted agent management is available broadly; self-hosted setup and control is Desktop or CLI.
Capability Matrix
| Capability | Mobile | Desktop | Web | CLI | Terminal Chat |
|---|---|---|---|---|---|
| Chat with users and agents | Yes | Yes | Yes | Yes | Yes |
| Voice messages | Yes | Yes | Yes | Text-to-speech send | No |
| Images and files | Yes | Yes | Yes | Yes | No |
| Reactions and forwarding | Yes | Yes | Yes | Yes | No |
| Message search | Ask the agent | Ask the agent | Ask the agent | Yes | Ask the agent |
| Interactive cards | Yes | Yes | Yes | No | No |
| Live calling | Yes | Local self-hosted agents | No | No | No |
| Live activity signals | Yes | Yes | Yes | No | No |
| Create hosted agents | Yes | Yes | Yes | Yes | No |
| Edit hosted profile, instructions, voice, sharing | Yes | Yes | Yes | Partial | No |
| Chat with online self-hosted agents | Yes | Yes | Yes | Yes | Yes |
| Create or run self-hosted agents | No | Yes | No | Yes | No |
| Configure self-hosted model, workspace, or tools | No | Yes | No | Yes | No |
| Configure local models for an agent | No | Yes | No | Yes | No |
| Manage self-hosted API keys | No | Yes | No | Yes | No |
| Manage who can message the agent | Yes | Yes | Yes | Yes | No |
| Manage scheduled prompts | No | Yes | Yes | Yes | No |
| Open conversation workspace manager | No | Hosted and local self-hosted | Hosted only | No | No |
Agent Modes and Tools
Hosted agents are the default. You can create one from mobile, web, desktop, or CLI, then manage its profile, instructions, voice/language, and sharing from Mutiro. From the CLI, profile and sharing are direct commands, instructions sync via mutiro agent files, and voice is set at creation — changing voice later is done in the apps.
Hosted agents start with a broad default tool set — files, uploaded images/documents, messaging, memory, recall, scheduling, cards, web search, and web fetch — and owners can turn individual tools on or off per agent from the agent's Tools tab.
Use self-hosted Genie when you want to choose the model or provider (hosted agents run on Mutiro's managed models), need a workspace on your own machine, or need the tools that require one: shell/process/coding tools and git tools. Desktop is the easiest route; CLI is the manual route. Once a self-hosted agent is online, every chat client can talk to it.
Conversation Features
- Text, images, files, replies, reactions, forwarding, read receipts — normal messaging features across the main apps.
- Voice messages — mobile, desktop, and web can record; the CLI can send a synthesized voice message from text (
mutiro user message send-voice). The agent receives the transcription. - Agent voice replies — the owner configures the agent's voice and language.
- Interactive cards — supported on mobile, desktop, and web, including interactive submits; not rendered in CLI or Terminal Chat.
- Live calling — available on mobile when enabled for the agent; on desktop, for self-hosted agents running on that computer.
- Presence and activity — see who is online and what an agent is doing in clients that support live signals.
- Finding past messages — the apps have no search box; ask the agent instead ("find where we discussed the contract") and, when you are the owner, its conversation-search tools do the digging. The CLI also has
mutiro user message searchfor direct lookups.
Agent Capabilities
These capabilities are attached to the agent and conversation, not to only one hosting mode.
- Scheduling — a scheduled message sends already-written text later; a scheduled prompt gives the agent an instruction later and starts a fresh turn to carry it out. Owners create prompts in the agent's Schedule tab on web or desktop. Agents with scheduling tools can create outgoing messages through chat. See Scheduling for setup, timing, conversation context, and tailored follow-ups.
- Clearing context — send
/clearin a conversation to start fresh: the agent stops carrying earlier messages as context from that point on. Older messages stay stored and visible, and the agent can still look them up deliberately with its conversation tools. - Memory — the agent can save durable facts for its current workspace when memory tools are available. Ordinary users have separate workspace memory; owner and developer conversations share the owner workspace's memory. See Agents, Conversations, and Workspaces for the difference between chat context, memory, and shared files. The workspace manager shows hosted agent files in web and desktop; for local self-hosted agents, use desktop on the computer running that agent. Its Agent section exposes files such as
MEMORY.mdandAGENTS.md. - Recall — the agent can search earlier conversation history for relevant context.
- Working memory — current-task state for advanced/self-hosted setups when explicitly enabled; not a separate user interface.
Current Limits
- No direct agent-to-agent messaging.
- No group conversations with multiple agents.
- No message-search box in the apps — search by asking the agent, or use the CLI.
For hosting choices, see runtime modes. For self-hosted tool configuration and security implications, see self-hosted configuration and sharing and security.