Xome
FeaturesHow it worksFAQJoin waitlist →
iOS · Android · open beta opening soon

A pocket AI that actually does things.

Local-first by design. Runs Gemma 4 on your phone. Plugs into Gmail, Slack, Notion, GitHub, and Calendar. Bring your own model when you need a bigger brain.

we'll only email when it's ready

The Xome app on a phone, showing a chat where the agent has searched Slack and created GitHub issues for each unread mention.
01 — WATCH IT WORK

One prompt. Five tools. Done.

Xomegemma-4-e4b · local
thinking…
▸ slack_search_messages
query: "@me", since: "today"
⏱ 312ms · ✓ found 3 mentions
▸ github_create_issue
repo: "team/inbox", title: "Sarah's bug from #launch"
⏱ 1.2s · ✓ #847
▸ github_create_issue
repo: "team/inbox", title: "Mike's question on auth"
⏱ 980ms · ✓ #848
▸ github_create_issue
repo: "team/inbox", title: "Priya's request for review"
⏱ 1.1s · ✓ #849
4 tool calls · 3.6s · 1 final answer
02 — THE PROBLEM

Your AI doesn't know your inbox.

Most AI on your phone is a chat box pointed at a cloud. It doesn't read your email. It doesn't see your calendar. It can't post to Slack. It forgets you the moment you close the tab.

Xome is different by design. The model runs on your device. It connects to the apps you actually use. It takes action with your permission, in the foreground or while you sleep. And when a task needs a bigger brain, you bring your own — Claude, GPT, or Gemini, with your key, on your terms.

"It's the first AI on my phone that's worth keeping the icon on the home screen."

03 — HOW IT THINKS

Plan. Call. Reflect. Repeat.

User inputwhat you askPlandecide which toolsCall toolwith your permissionReflectdid this work?Tool resultstructured backFinal answeror another loop

Every turn is a small loop. The agent plans the next step, picks a tool, calls it, looks at the result, and decides whether to keep going.

No magic. No hidden waterfall of LLM calls. Just a tight loop you can pause, audit, and approve at every write.

When a step needs a bigger model, the loop seamlessly hops to your cloud key and back — your data never sits on our servers.

04 — FEATURES

Built thoughtfully.

// 01 LOCAL-FIRST

Local-first by default.

The model runs on your device. Your inbox, calendar, and chats never touch our servers. Cloud is opt-in, with your keys, your bills.

cloudonly whenyou opt in
// 02 BYO MODEL

Bring your own brain.

Plug in Claude, GPT, or Gemini for harder tasks. Your key, your provider, your control.

claude-opus-4.7gpt-5gemini-2.5-pro
Xome
// 03 INTEGRATIONS

Five real integrations.

Gmail, Calendar, Slack, Notion, GitHub. Real OAuth, real scopes, real writes.

// 04 APPROVAL

Approval before every write.

Read freely. Write only with consent. You see the tool, the args, and a one-tap decline.

APPROVAL · gmail_send
to: sarah@team.io
subject: follow up
// 05 MCP

Speaks MCP fluently.

Point it at any MCP server and its tools become Xome's tools. Open ecosystem.

$ xome mcp add \
  --url https://my-tools.example.com \
  --name my-tools
✓ discovered 7 tools
// 06 VOICE

Voice in, voice out.

Talk to it like you'd talk to a colleague. On-device speech, no audio leaves the phone.

// 07 AUTOMATIONS

Background automations.

Triggers fire while you sleep. Push wakes the agent. Notification lands when work is done.

TRIGGER
New email from vip@…
ACTION
Draft reply, ping me on Slack
TriggerPush wakeAgent runsNotification
// 08 VISION

Vision input.

Snap a whiteboard. Get a structured summary. Local model, no upload.

// 09 HYBRID

Hybrid routing.

Easy task → local Gemma. Hard task → your cloud model. The router picks per turn.

easy → local Gemma200ms
hard → your cloud2.0s
// 10 OPEN SOURCE

Open by default.

Self-host the relay. Read every tool definition. Ship your own MCP server.

$ git clone github.com/xome/relay
# MIT · self-host in 30s
// 11 ENCRYPTED

Encrypted history.

Conversations stored encrypted with a key in your device's secure enclave.

// 12 PLATFORMS

iOS and Android.

One Flutter codebase. Native feel. No Electron, no React Native bridge.

05 — CONNECTS TO

// and anything that speaks MCP →
GmailCalendarSlackNotionGitHubLinear (soon)Asana (soon)Outlook (soon)Discord (soon)your own MCP server
GmailCalendarSlackNotionGitHubLinear (soon)Asana (soon)Outlook (soon)Discord (soon)your own MCP server
GmailCalendarSlackNotionGitHubLinear (soon)Asana (soon)Outlook (soon)Discord (soon)your own MCP server
GmailCalendarSlackNotionGitHubLinear (soon)Asana (soon)Outlook (soon)Discord (soon)your own MCP server

06 — PRIVACY

Your data doesn't leave the room.

The model that reads your inbox lives on your phone. Not on a server we run, not on a server anyone runs. The data path stops at your device.

When a task needs cloud, you bring your own key. Claude, GPT, Gemini — your provider, your bills, your audit log.

We don't keep a copy. We never see your messages. The relay that wakes background tasks carries nothing about you except a push token.

Local modelemailcalendarchatscloud (yours)via your API key
0

servers we run in the data path

100%

local model by default

your keys

your bills · your control

07 — UNDER THE HOOD

Six layers, one loop.

UI
ChatConnectionsHistorySettingsApprovals
Orchestrator
PlanCallReflectRepeat
Provider abstraction
GemmaClaudeGPTGemini
Tool layer
Native toolsMCP clientTool registry
Integration adapters
GmailCalendarSlackNotionGitHubon-device
Platform services
OAuthSecure storageDBPushBackground

All of it ships in one Flutter app. None of it is magic. All of it is open.

08 — WHERE THIS IS HEADED

Roadmap, in plain sight.

  1. Phase 0shipped

    Foundation

    Flutter scaffold, design system, model bench harness.

  2. Phase 1shipped

    Core architecture

    Plan/Call/Reflect loop, provider abstraction, secure storage.

  3. Phase 2shipped

    Gmail

    First integration end-to-end with read and write scopes.

  4. Phase 3in progress

    Calendar, Slack, Notion, GitHub

    Four integrations rolling out, full read + scoped write.

  5. Phase 4pending

    On-device tools and utilities

    Time, location, contacts, files. Real on-device.

  6. Phase 5pending

    Voice and vision

    Speech in/out, image input — all local where possible.

  7. Phase 6pending

    MCP client

    Point Xome at any MCP server, gain its tools instantly.

  8. Phase 7pending

    Background automations

    Triggers, schedules, push wake, audit log.

09 — COMMON QUESTIONS

Everything else.

The app and the local model are free. Cloud models cost what you pay your provider; we never see your bills.

No. The model on your phone reads them. We don't have a server with your inbox or your DMs.

Gemma 4 E4B by default. Switch to E2B for older devices, or FunctionGemma 270M for fast tool routing.

Use the cloud path with your own API key, or switch to the lighter E2B variant.

Yes, with admin-approved OAuth. We don't ask for any scope you wouldn't grant a normal client app.

Yes. Xome speaks MCP. Any MCP server you point it at becomes available as tools.

iOS background execution is constrained by Apple. We use silent push from a tiny relay we run, with periodic fallback. Real-world reliability is high but not 100%; we're honest about it.

Open beta opening soon. Join the waitlist for the invite — we're inviting in batches based on signup order.

Stop chatting.
Start doing.

we'll only email when it's ready

we'll only email when it's ready · and once when it ships