OttO MobileSoon

OttO Mobile connects to the OttO Core server running on your computer over your local network. Nothing goes through the cloud — the phone talks directly to your machine.

• View and manage the task queue, with live updates
• Explore the knowledge graph and add new nodes
• Chat with the agent grounded in your knowledge base
• Get a notification when a task completes

The phone authenticates to the core with a pairing token. Both devices must be on the same local network.

1. On the desktop, open Settings → Connections and find the Mobile Pairing card
2. On the phone, open OttO Mobile and tap Scan QR Code on the pairing screen
3. Point the camera at the QR code — pairing completes automatically

If your computer has more than one network interface, pick the address your phone can reach from the dropdown next to the QR code.

No camera, or scanning fails? Use manual entry on the pairing screen. The desktop pairing card shows both values you need:

• Address — e.g. http://192.168.1.20:47821
• Token — click it once to select, then copy

The connection is stored securely on the device (Keychain on iOS, EncryptedSharedPreferences on Android) and survives app restarts.

The app mirrors the desktop feature set in four tabs: Queue, Graph, Agent, and Settings.

• Tasks sorted by status: in progress → pending → done
• Swipe right to complete, swipe left to delete
• Add tasks with the + button (topic + optional description)
• Show or clear completed tasks from the top-bar menu
• Live updates via server-sent events — changes made from the desktop or an AI assistant appear instantly

• Interactive force-directed layout with pan, pinch-zoom, and tap
• Node colors by type: knowledge, inference, and plan; solid edges are sequential, dashed edges are semantic links
• Tap a node to see its full text, keywords, and source files
• Add knowledge directly from the phone with the + button

Ask questions grounded in your knowledge base. The agent runs on the core — the phone only streams the conversation.

• Provider and model picker: Ollama (local), OpenAI, or Groq — availability follows what you configured on the desktop
• Web search toggle for OpenAI and Groq
• Streaming responses with visible tool calls
• Save any assistant answer to the graph with “Add as node”

• Server status, core version, and active project
• Theme: System, Dark, or Light
• Disconnect to return to the pairing screen

The app subscribes to the core's event stream and fires a local notification when:

• A task is completed — by you, the desktop, or an AI assistant working through MCP
• The queue is drained (all tasks done)

Notifications require the app to be running and reachable on the same network as the core. Allow notification permission on first launch.

OttO Core listens on your local network so the phone can reach it, but every non-local request must present the pairing token:

Authorization: Bearer <pairing-token>

• Requests from the computer itself (loopback) are unaffected — the desktop app and local MCP clients need no token
• The pairing info endpoint (/api/pairing) only answers loopback requests, so the token is never exposed to the network
• LLM API keys stay on the computer; the phone never stores or transmits them