Talking to MeghaOS
How to phrase requests, the fast-path commands, and how the agent decides what to do.
Everything in MeghaOS starts with a request you type into the chat. There's no command syntax to memorize — you describe what you want and the agent figures out whether to render a widget, run a tool, kick off a workflow, or just answer.
The four things a request can become
| You ask… | You get… |
|---|---|
| "a 25-minute timer" | A self-managing widget (countdown) |
| "weather in Berlin" | A live data widget (live_weather) |
| "email this summary to sam@acme.com" | A tool action (SEND_EMAIL) |
| "research X, summarize it, and post to Slack" | A multi-step workflow |
| "open Cursor and build a todo app" | A computer-control session |
Fast-path commands
A handful of inputs skip the LLM entirely and return instantly:
| Type this | Result |
|---|---|
df | Disk usage card |
free | RAM usage card |
ps | Top CPU processes table |
who is <name> · profile of <name> · bio of <name> | Generated profile UI |
telepath / demo | Telepath demo cards (append --cards=a,b to filter) |
Writing good requests
"a habit tracker for water, sleep, and reading" beats "a tracker" — the agent seeds the widget with your specifics.
"stock chart for NVDA" or "weather in Kyoto" — concrete entities route straight to the right live widget.
"search for the top AI papers this week and email me the list" becomes a two-step workflow automatically.
"show me how a 4-stroke engine works" yields an animated SVG diagram, not a wall of text.
Memory makes it personal
The agent remembers facts across sessions. Once you've said "I'm based in Tokyo" or "my work email is sam@acme.com", later requests like "what's the weather?" or "email the team" use that context automatically. See Memory.
Approvals for risky actions
Tools that could be destructive — or any plugin the agent wrote for itself — may ask for
confirmation before running. You'll see a confirmation card; approve or decline it. Trusted
built-in plugins (is_safe = True) run without prompting. See the
Plugin System.
Conversations & history
Chats are grouped into sessions you can revisit or delete:
| Endpoint | Purpose |
|---|---|
GET /api/chats | List sessions |
GET /api/chats/{session_id} | Open a session |
DELETE /api/chats/{session_id} | Delete a session |
Other ways to talk to it
MeghaOS also listens outside the desktop. With the right tokens configured, you can message it from Telegram, Slack, or Discord, and it can receive Google Chat / Teams webhooks. Replies come back through the same channel.