Get Started with Console on Mobile

Connect the mobile app to your Console workspace, inspect a first task, and understand approvals and offline behavior.

Outcome: sign in to the intended Console deployment, inspect one known business record with the Assistant, and verify its tool result before using mobile for ongoing operations.

The mobile app lives in stateset-console/stateset-console-mobile and uses the Console backend. Set up your organization’s backend and connections first using the web Console walkthrough.

1. Install your team’s build

Obtain the mobile build and intended Console environment from your administrator. The repository includes internal development and preview build profiles, including an Android APK profile. A production build profile is not confirmation of public App Store or Google Play availability.

For an existing build, confirm which backend it targets before signing in. The checked build profiles use https://console.stateset.app; your organization may provide a different deployment. A development phone and a production phone can display similar screens while accessing different data.

2. Sign in and find your tools

Use the supported email/password or Console access-token flow. SSO is available when configured by the backend. Complete verification and organization provisioning before attempting agent work.

The current navigation is:

Tab	Start here to…
Today	Review the mobile home view
Assistant	Submit a bounded task and inspect streaming responses
Runs	Inspect autonomous sessions
Activity	Review activity and analytics
More	Open Integrations, Calls, Notifications, Tools, Settings, or Support

Open More → Integrations and check the connection needed for your first task. If it needs configuration, use the supported setup flow for your deployment. A cached integration list is not proof that the backend currently has working credentials.

3. Verify one Assistant task

Open Assistant and send this prompt with a real test identifier:

Read only. Inspect [record ID] in [connected system] for this organization.
Report its current state and cite the tool result used to retrieve it.
If access is unavailable, explain the missing connection or permission.
Do not change data, send messages, issue refunds, or start autonomous work.

Inspect the response and tool-call cards; open tool details when the result is too long to read inline. Compare the identifier and returned state with the source system. If tools are missing, check organization connections and available tools before resending the same task.

Complete when: the app is connected to the intended deployment, the tool result identifies your test record, and the response agrees with that evidence. Save the conversation identifier when available so another operator can find the work.

4. Handle interruptions and approvals

The app persists data locally and queues messages when offline. A queued message has not necessarily reached an agent. Reconnect, keep the app active, and inspect the queue and response before retrying. Cached screens can be useful while offline but do not establish current server state.

Streaming pauses when the app moves to the background. Returning to the app or stopping the visible stream does not prove a remote task was cancelled. Check the existing conversation or run before submitting another action, especially if the first request could have changed data.

For approvals, inspect the target and requested action before approving. Review the resulting execution status afterward: approval alone does not establish completion. Push notifications require permission and a correctly configured native build and notification service; a missing notification is not evidence that there are no pending requests.

Use More → Settings to configure the available app-lock options. Signing out clears local session data; use the server’s run controls to manage remote work.

Run the mobile app locally

For contributors, use Node.js 20.20.0+ and install from the mobile directory:

git clone https://github.com/stateset/stateset-console.git
cd stateset-console/stateset-console-mobile
npm ci

Set the Console backend in a local .env file. For an authorized hosted environment:

EXPO_PUBLIC_API_URL=https://console.stateset.app

This URL is public build configuration. Never put a server secret or access token in an EXPO_PUBLIC_* variable. For a physical phone accessing a local web backend, use your computer’s reachable LAN address and port instead of localhost. The backend must be running and reachable from the device. Production configuration requires an absolute HTTPS URL.

npm start

Use the repository’s native development workflow for platform features:

# Android: requires the Android SDK and the repository's supported JDK setup.
npm run android

# iOS: requires macOS and Xcode.
npm run ios

npm run web provides a browser development target; verify native storage, biometrics, notifications, and deep links in a native build. Follow the mobile repository README for build prerequisites and release configuration. Production builds also validate certificate pinning and other release settings; do not copy example pins into a deployment.

Troubleshooting

Symptom	Next check
Sign-in fails only on the phone	Build’s backend URL, device connectivity, and enabled authentication flow
Local backend works on the computer only	LAN reachability; phone localhost refers to the phone
Message remains queued	Network state, app foreground state, and queue retry status
Stream stopped after switching apps	Existing conversation and remote run state before retrying
Integration appears connected but tools fail	Fresh connection state, organization credentials, and tool configuration
Approval notification never arrives	Pending approvals in the app, device permission, and native push configuration

Use More → Support for the About/support surface and available diagnostics. Include the app version, deployment, time, and conversation/run identifier when reporting an issue; omit credentials.

Next: web Console setup, Desktop setup, or mobile architecture and behavior.

Source basis: the mobile README, package scripts, EAS profiles, tab layout, More screen, configuration, and streaming hook, reviewed 2026-09-20. This walkthrough was checked against source; installation and live backend execution were not performed.