A native Android client for OpenClaw and Orchestrator — monitor and control your AI agent sessions from your phone.

• Real-time streaming — token-by-token typewriter response via WebSocket
• Ed25519 authentication — full device pairing handshake with OpenClaw Gateway 2.13+
• Agent selector — switch between Main / Engineer / QA agents on the fly
• Markdown rendering — bold, italic, inline code, code blocks, headings, lists
• Chat history — local Room database, sortable, per-session
• Voice input — Android Speech-to-Text integration

• Session management — start, pause, resume, and stop Orchestrator sessions from your phone
• Live log streaming — WebSocket log tail with phase/error/checkpoint filters; auto-reconnect with exponential backoff
• Task progress — per-session task counts (pending / running / done / failed)
• Checkpoint management — view, load, and delete session checkpoints
• Human-in-the-loop interventions — approve, deny, or provide guidance when the agent pauses for operator input
• Background intervention polling — WorkManager job notifies you when any session is paused awaiting operator input
• Permission approval — review and approve/reject tool permission requests
• Replan flow — when a session fails, view the AI-generated failure summary, add operator feedback, and send it back to Project Architect to seed a new planning session
• Project & task explorer — browse projects, task lists, file trees, and task detail

• Offline banner — detects network drops; falls back to REST polling silently
• Dark theme — consistent slate/navy UI across all screens

app/src/main/java/com/user/
├── data/
│   ├── OrchestratorModels.kt   # All Orchestrator API response models
│   ├── PermissionModels.kt
│   ├── PrefsManager.kt         # Server URL, API key, gateway token, prefs
│   └── ...                     # Room entities, DAOs, database
├── repository/
│   └── OrchestratorRepository.kt
├── service/
│   ├── OrchestratorApiClient.kt    # All Orchestrator REST calls
│   ├── WebSocketManager.kt         # Live log streaming with reconnect
│   ├── InterventionPollService.kt  # WorkManager background poller
│   ├── PermissionPollService.kt
│   ├── GatewayClient.kt
│   ├── Ed25519Manager.kt
│   └── OpenClawService.kt
├── ui/
│   ├── activities/
│   │   ├── MainActivity.kt
│   │   ├── SessionsActivity.kt
│   │   ├── SettingsActivity.kt
│   │   └── OnboardingActivity.kt
│   ├── tasks/
│   │   ├── SessionDetailActivity.kt   # Live logs, interventions, replan
│   │   ├── ProjectDetailActivity.kt
│   │   ├── TaskDetailActivity.kt
│   │   ├── TaskListActivity.kt
│   │   └── CheckpointsBottomSheet.kt
│   ├── permissions/
│   │   └── PermissionsActivity.kt
│   ├── components/
│   │   ├── OfflineBannerView.kt
│   │   └── StatusBadgeView.kt
│   └── FailureSummary.kt, MarkdownRenderer.kt, OutputHighlighter.kt, ...
└── viewmodel/
    ├── SessionViewModel.kt
    ├── TaskViewModel.kt
    └── ...

ClawMobile
  │
  ├─── Chat/voice ──────────────────────> OpenClaw Gateway (:18789)
  │                                           └── OpenClaw agent runtime
  │
  └─── Session control / monitoring ──> Orchestrator API (:8080)
           ├── Projects, tasks, sessions
           ├── Live WebSocket log stream
           ├── Human-in-the-loop interventions
           ├── Permission approvals
           └── Replan flow

Both connections run through Tailscale or LAN. They are independent — the Gateway token is for chat; the Orchestrator URL + API key are for session control.

ClawMobile can read provider metadata from Gateway/Hermes through GET /providers/status after the Gateway connection is configured. Android stores only the Gateway/Hermes connection settings needed to authenticate to your server. OpenAI, Anthropic, OpenRouter, and other third-party provider API keys stay server-side behind Gateway/Hermes and are not stored in the Android app.

• Android Studio Hedgehog (2023.1.1) or newer
• JDK 17+
• Android SDK API 29+ (Android 10+)
• OpenClaw running locally or on a server
• Orchestrator running (for session management features)

Recommended — Tailscale

Orchestrator URL: http://<tailscale-ip>:8080
Gateway URL:      http://<tailscale-ip>:18789

SSH tunnel (emulator or different network)

ssh -N -L 8080:localhost:8080 -L 18789:localhost:18789 \
    -o ServerAliveInterval=30 USER@YOUR_SERVER_IP

Same WiFi

Orchestrator URL: http://192.xxx.x.xx:8080
Gateway URL:      http://192.xxx.x.xx:18789

Gateway token:

cat ~/.openclaw/openclaw.json
# Copy gateway.auth.token

Orchestrator API key:
Settings → API Keys in the Orchestrator dashboard.

./gradlew assembleDebug
# APK → app/build/outputs/apk/debug/app-debug.apk

Or Run → Run 'app' in Android Studio.

1. App opens Settings if no token is set
2. Enter Gateway URL + Token → Save (for chat)
3. Enter Orchestrator URL + API Key → Save (for session control)
4. First Gateway connection shows Device Pairing Required:

openclaw gateway call device.pair.list --json
openclaw gateway call device.pair.approve --params '{"requestId":"<id>"}' --json

5. Restart → ● Connected

• All messages stored locally on device via Room
• No analytics, no cloud sync, no third-party SDKs
• Only outbound connections are to your own OpenClaw and Orchestrator servers

Consider giving it a star — it helps others discover the project and keeps us motivated!

MIT