GDP Ops is a mobile operations and control-plane client, not a mobile IDE. The current published Android surface helps you observe work and use a small set of bounded actions while arbitrary repository, terminal, patch, Git, and Browser Send authority stays elsewhere.
Navigate the current mission-control surfaces
The current published Android navigation is Home, Work, Browser, Agora, Inbox, and Settings. The app presents account-connected node and work state, bounded check evidence, collaboration context, action attention, control-plane summaries, and a first-class Browser Companion mission surface.
Use Work and Inbox to inspect tasks, failures, check outcomes, and items that need attention.
Use Browser to inspect bounded Browser Companion lane health and close-readiness without receiving private tab, conversation, URL, prompt, or response payloads.
Use Agora for operational collaboration; Commons remains social and is explicitly not evidence.
Use Settings for connection, device, updater, and read-only Flight Deck/control-plane information.
Use only the bounded mobile actions that have contracts
Current Android actions are narrow and product-specific rather than a generic command surface. They include safe flows such as canceling eligible waiting work, queuing one safe retry for an existing failed check, bounded Agora replies, device/session controls, and configured mobile-service actions.
Android does not expose a generic MCP runner, command composer, patch editor, repository browser, commit/push surface, or Browser Send control. Desktop or the appropriate execution node performs final local revalidation.
Read published capability separately from active development
The published 0.6.26 architecture includes the first-class Browser mission surface and bounded task-bound Browser Companion health. A broader task-unbound Browser Fleet Command Center is an active post-0.6.26 development cycle and must not be inferred as already published behavior.
Remote push delivery remains fail-closed until its dedicated credentials, enablement, and physical acceptance gates are satisfied.
Last-known mobile snapshots improve restart UX but never grant mutation authority.
Manual physical-device acceptance remains a separate release obligation from unit, screenshot, or build evidence.
A mobile control or summary never upgrades itself into repository, terminal, publication, or Browser execution authority merely because it is visible on the phone.
