> ## Documentation Index
> Fetch the complete documentation index at: https://altostrat.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Studio Remote

> Pair Studio Remote on iPhone, iPad, or Android with a Studio desktop to continue conversations, add on-site context, and handle approvals away from your desk.

Studio Remote is the mobile companion to Altostrat Studio. Pair an iPhone, iPad, or Android device with one running Studio desktop, then continue conversations, send context from the field, follow active work, and respond to supported approval requests away from your desk.

The paired desktop remains the execution bridge to local hosts, tools, sessions, and stored credentials. Studio Remote gives you a focused chat and approval surface; it does not recreate the full desktop workspace on your phone or tablet.

<Note>
  Studio Remote is available for both Apple and Android devices:

  * [Download for iPhone and iPad from the App Store](https://apps.apple.com/us/app/altostrat-remote/id6786571787)
  * [Download for Android from Google Play](https://play.google.com/store/apps/details?id=io.altostrat.studio.remote)
</Note>

## Before you pair

* Update Studio to the current production release.
* Sign in to the correct Altostrat organization on the desktop.
* Keep the desktop awake, online, and connected to the networks its tools need.
* Install Studio Remote on your Apple or Android device.
* Treat every paired mobile device as an authenticated control surface for that Studio desktop.

## Pair a mobile device

<Steps>
  <Step title="Open Studio Remote on the desktop">
    Select the phone control in Studio's status bar. The pairing panel opens.
  </Step>

  <Step title="Install the mobile app">
    Select **iPhone** or **Android** in the pairing panel if Studio Remote is not already installed.
  </Step>

  <Step title="Generate a pairing code">
    Studio shows a QR code and a short text code. If a code expires or is exposed, select **New code**.
  </Step>

  <Step title="Scan or enter the code">
    In Studio Remote, scan the QR code or enter the displayed code. Wait for the desktop to list the new current connection.
  </Step>

  <Step title="Verify scope">
    Confirm the paired desktop, available channels, and recent conversations on the mobile device before using it for live work.
  </Step>
</Steps>

## What you can do remotely

After pairing, Studio Remote can:

* Switch between personal and shared channels, browse recent conversations, continue a chat, or start a new one.
* Follow running conversations, use prompt suggestions, and queue or steer a follow-up while Copilot is working.
* Send prompts with slash commands and mentions for existing hosts, connectors, procedures, files, and tools.
* Add on-site context from files, the photo library, or the camera.
* Dictate prompts with the device microphone.
* Read conversation messages, generated-artifact references, and usage details.
* Pin, rename, archive, and update the status of a conversation.
* Approve once, allow for the session, or reject supported tool requests when those choices are offered.
* Receive notifications when an approval needs attention or a chat completes.
* Request that a specific paired desktop wake and claim the mobile work.

Availability can differ by conversation state and desktop capability. If the desktop cannot execute a tool locally, pairing does not make that tool available.

## What stays on the desktop

Studio Remote is deliberately execution-focused. Use the desktop app for:

* Signing in, switching organizations, and managing account settings.
* Opening terminals, remote desktop sessions, procedure runs, diagrams, files, and full generated-artifact panels.
* Creating and managing hosts, credentials, connectors, procedures, and other workspace resources.
* Any task that needs the desktop's local network path, helper process, or stored credentials.

The mobile app stores a scoped delegated token in secure device storage. It does not copy your desktop credentials to the mobile device.

## Approvals from a mobile device

An approval has the same operational consequence whether accepted on the desktop or a mobile device. Before approving remotely:

1. Read the tool name, target, detail, and proposed action.
2. Confirm the desktop is connected to the expected organization and network.
3. Prefer a one-time approval over **Allow for session** when you cannot see the full desktop state.
4. Reject ambiguous actions and continue from the desktop.

<Warning>
  Do not approve a state-changing action from a lock-screen preview or notification alone. Open Studio Remote and inspect the full request.
</Warning>

## Manage connections

Open the Studio Remote status-bar panel on the desktop to see **Current connections**. Refresh the list to update status. Select the remove control beside a connection to revoke access immediately.

Revoke a connection when:

* A mobile device is lost, replaced, repaired, or handed to another person.
* You paired a temporary or test device.
* The displayed connection is unfamiliar.
* The current desktop session should no longer accept remote actions.

Generate a new pairing code if a code was copied or displayed where someone else could use it. A new code does not replace the need to revoke an already-established connection.

## Troubleshooting

| Symptom                                  | What to check                                                                                                                                                               |
| ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The phone control does not appear        | Confirm you are using the current production desktop app, not Studio in a browser or a staging build.                                                                       |
| A pairing code fails                     | Generate a new code and confirm both devices have network access. If the QR code points to a private Studio endpoint, connect the mobile device to the same network or VPN. |
| Chats are visible but tools fail         | Keep the paired desktop awake, signed in, and connected to the target network.                                                                                              |
| A file or photo is not included in full  | Try a smaller supported file. Large or unsupported attachments may be sent as metadata only.                                                                                |
| Notifications do not appear              | Allow notifications for Studio Remote in the device settings, then reopen the app while paired.                                                                             |
| An approval never appears on mobile      | Refresh the conversation and current connections; handle the request on the desktop if it is time-sensitive.                                                                |
| A mobile device should no longer connect | Revoke it from **Current connections** on the desktop.                                                                                                                      |

## Related

<CardGroup cols={2}>
  <Card title="AI Copilot" icon="sparkles" href="./ai-copilot" arrow="true" cta="Understand approvals">
    Review the modes and tool approval model that Studio Remote carries to mobile.
  </Card>

  <Card title="Security and privacy" icon="shield" href="./security-and-privacy" arrow="true" cta="Secure access">
    Review credential boundaries and connection-revocation practices.
  </Card>
</CardGroup>