Start a cloud workspace

Outcome: your agent can build and inspect your Android app in an Olef-managed workspace.

Before you begin

You need enabled Olef Cloud access, the Olef CLI, and a connected coding agent. You do not need a local Android SDK for this workflow.

olef cloud login
olef cloud whoami

Complete the browser approval. whoami reports the signed-in account and access state. If your account is waitlisted, complete the access process before attempting to start a workspace.

2. Link an Android project

From the project’s root directory:

olef cloud link
olef cloud status

Review the upload preview before approving. Keep credentials and files you do not want uploaded out of the sync set. status helps you confirm which workspace this project is linked to before running commands against it.

3. Ask your agent to run it

Run this Android project on its linked Olef Cloud workspace. Build and
launch the app, show me the first screen, and report any setup or runtime
errors. Verify that you are using the intended workspace before changing it.

Olef provisions the managed environment and emulator for the workflow. The initial start can take longer while the environment becomes ready. Inspect the returned status if it fails rather than repeatedly creating new workspaces.

4. Try a change

Ask for a small change, then have the agent apply it and verify the resulting behavior. Use the viewer to try the running app yourself. Try it & make changes gives concrete prompts.

Starting without a local project

In the dashboard, New workspace offers the sources enabled for your account, such as a template, an empty hosted workspace, or GitHub. Choose a template to begin with an existing structure, or an empty workspace when your agent will create the project.

For teams, choose the right organization and project before creating the workspace. See Teams & collaboration.

Stop when finished

Use the workspace controls in the dashboard to stop the running session. Review usage and limits there. Stop releases running compute; it is not the same action as deleting your workspace.

For CLI lifecycle operations, consult the cloud command reference. For access, capacity, or connection failures, see troubleshooting.