Skip to content
Independent guide · Features & How Dots Work

Dots on Desktop, Web and Mobile

Choose the right device for creation, review, and local work.

Updated 4 October 2026 · Independent of OpenAI

OpenAI says dot creation starts on desktop app or desktop browser. After initial setup, messaging is available through the mobile app when its supporting update is available; mobile web is not supported.

Choose the right device for creation, review, and local work. A concise result with a clear unknown is often the right starting point. Record where the decisive facts came from before acting on them.

Define the task

What to prepare before you begin

Specify desktop app or browser, mobile app version and the decision you are trying to make. That keeps the work from expanding into an unreviewable search.

A useful deliverable

Device choice matched to the task. Add a short list of unresolved questions so the reviewer can decide what needs a fresh source.

Worked situation

How this plays out in practice

Creation on desktop, a quick mobile reply, and local file work on a connected laptop are three different device stories. Notice how one changed detail alters the judgment. Keep that detail in the brief and inspect whether it survives into the final draft.

Use desktop for setup and detailed review, mobile for supported messaging, and cloud work for tasks that should continue while devices are off. Link a claim to the material that supports it so later corrections can be made without guesswork.

A practical sequence

Run a bounded first pass

1. Establish the starting point

Start with desktop app or browser, mobile app version. If a collaborator owns one source, identify the approved version rather than guessing from its filename.

2. Request a reviewable draft

Use desktop to set up the dot and manage detailed work. Use mobile to message and review work when your app supports it; use the cloud computer for work that should continue after devices are off. Ask the assistant to distinguish what it observed from what it inferred.

3. Decide the next action

Confirm the planned effect against do not assume every control exists on mobile. Ask for a change list if the next step would modify an external system.

Editorial judgment

Where a plausible answer can fail

Do not assume mobile web supports dot creation or that a disconnected laptop can run a local task. Check the current app surface. Inspect external effects separately from the prose. A good draft can still propose the wrong recipient or target.

A local Work or Codex task still needs its connected computer online. Check current release notes if a control is absent on your platform. Leave a deliberate pause for a decision that belongs to the owner of the account or document.

Where to go next

Connect this result to the right follow-up

The Features & How Dots Work hub gives you the broader route and neighboring tasks. Return there when the present job has produced a result, rather than adding an unrelated responsibility to the same brief. Keep the original decision distinct from follow-up work. That makes both results easier to review.

For a closely related outcome, open Track Activity and Review Results. That guide focuses on inspect work in progress, answer a request, and check results. It may use some of the same context, but you should confirm the source and the decision point again. If your next question is about a different angle, Dots Cloud Computer and Browser is a better fit: understand the separate cloud computer and browser your dot can use. A new deliverable should have its own date, owner, and acceptance check.

Before you reuse this result elsewhere, look at Dots Privacy, Memory and Permissions for the wider product or review boundary. Take forward the verified facts and leave behind any assumption that was specific to this example. If the source has changed since the draft was made, update the relevant claim first. The purpose of the link is to make the next step more precise, not to imply that every connected guide is needed for every reader.

Adapt this

Build your own task brief

Edit the bracketed information and any sentence that does not fit your account. This is a suggested workflow, not a promise that your dot has access to a particular app or feature.

Your review

Check before moving on

Tick what you have actually checked. Your progress stays on this device for this page and can be cleared at any time.

0 of 4 checked

Questions

Frequently asked questions

Where should I verify this feature?

Use the scenario on this page as a small test. Use desktop for setup and detailed review, mobile for supported messaging, and cloud work for tasks that should continue while devices are off. Keep a source and a date beside any detail that can change.

What information matters most for dots on desktop, web and mobile?

Start with desktop app or browser, mobile app version. OpenAI says dot creation starts on desktop app or desktop browser. After initial setup, messaging is available through the mobile app when its supporting update is available; mobile web is not supported. Give the exact source or account where a decision depends on it.

What changes when a connected app is involved?

A local Work or Codex task still needs its connected computer online. Check current release notes if a control is absent on your platform. The relevant access, audience, and consequences determine what you should approve.

What would a useful result look like here?

Device choice matched to the task. It should make assumptions visible and leave a trail to the source, especially for dates, prices, permissions, or changing product details.

What is the common failure in this situation?

Do not assume mobile web supports dot creation or that a disconnected laptop can run a local task. Check the current app surface. Review that issue in the actual output instead of treating a polished presentation as proof.

Where can I check the current details?

Follow the official source linked below and inspect your account where access matters. This page was revised in October 2026; availability, terms, and product behavior can change.

Source for current product details: official OpenAI documentation or announcement ↗. The worked situations and briefs on this independent site are editorial examples. Confirm current access and details in your account. Editorial policy.