Skip to content
Independent guide · Dots Bot

Features & How Dots Work

See how cloud work, connected devices, memory, messaging, and reviews fit together.

Updated 4 October 2026 · Independent of OpenAI

Features & How Dots Work — Understand what happens between chats
Visual guide to Features & How Dots Work

The cloud computer lets a dot continue without your laptop. App connections provide specific tools; messaging channels let you reach the same dot. Memory and task context help it follow ongoing responsibilities.

See how cloud work, connected devices, memory, messaging, and reviews fit together. Think of this as a small research or drafting assignment. Source, date, uncertainty, and a review point make the outcome usable.

Editorial route

Follow one task across its surfaces

A cloud computer, local computer, saved note, message channel, connected app, and schedule are separate parts of the experience. They may interact, but one does not automatically grant the others. For example, a message from your phone can reach a dot while a local laptop task still waits for that laptop to be online. The feature guides below help you understand each boundary by tracing a specific task through it.

Choose a route

Guides in this section

Pick the specific page that matches the work in front of you. Each guide has a flat URL, a concrete review point, and links back to this overview. If the request spans several guides, finish one bounded piece before adding the next.

Define the task

How to use this section

Put one task, available apps and devices in the request, with permission limited to the relevant source. This makes it easier to correct a wrong answer without adding unnecessary access.

A useful deliverable

A map of capabilities and boundaries. If the evidence is mixed, show the disagreement rather than forcing a false certainty.

Worked situation

How this plays out in practice

Imagine asking for a weekly client digest. The cloud computer handles work, a connected app supplies source material, Activity shows progress, and you decide whether to share the draft. This case tests whether a draft notices the important constraint rather than flattening everything into a summary. Gather the known facts first, then decide what else to verify.

Trace each stage separately so you know where context came from, which permission allowed access, and what requires approval. If the work is repeated later, its inputs and open questions should still be intelligible.

A practical sequence

Run a bounded first pass

1. Establish the starting point

Before acting, confirm the identity and date of one task, available apps and devices. A result built on the wrong version is difficult to repair downstream.

2. Request a reviewable draft

Follow one task from a request through connected sources, background work, a draft result, Activity, and an approval point. Each component has its own permission boundary. Request a short evidence list with the draft so the most important claim can be verified quickly.

3. Decide the next action

End with feature availability varies by account and platform. If the work needs another person’s decision, make that request specific and dated.

Editorial judgment

Where a plausible answer can fail

A feature list can make separate surfaces look interchangeable. Cloud work, local computer access, messaging channels, and scheduled tasks have different requirements. If the supporting material is incomplete, a qualified answer is stronger than a confident invention.

Do not assume a connected app creates a scheduled task, that a phone can run local desktop work, or that a preview image is a real product screenshot. The output can stop at a draft if the remaining step depends on your authority or private information.

Where to go next

Connect this result to the right follow-up

If you are new to the product, Get Started & Trust helps establish the account and permission basics before you use this section as a working plan. A change of source, audience, or consequence is a sensible point to open a new guide.

For a closely related outcome, open Dots Cloud Computer and Browser. That guide focuses on understand the separate cloud computer and browser your dot can use. 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, Background Work, Recurring Tasks and Follow-Ups is a better fit: understand assigned ongoing work, schedules, events, and proactive research. A new deliverable should have its own date, owner, and acceptance check.

Before you reuse this result elsewhere, look at Get Started & Trust 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

Which guide should I open first?

Open the child guide closest to the result you need: a map of capabilities and boundaries. Start with its inputs and review gate, then come back to this overview for adjacent tasks.

What information matters most for features & how dots work?

Start with one task, available apps and devices. The cloud computer lets a dot continue without your laptop. App connections provide specific tools; messaging channels let you reach the same dot. Memory and task context help it follow ongoing responsibilities. Give the exact source or account where a decision depends on it.

How do I combine two related workflows?

Define separate results and approval points. Do not assume a connected app creates a scheduled task, that a phone can run local desktop work, or that a preview image is a real product screenshot.

What would a useful result look like here?

A map of capabilities and boundaries. 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?

A feature list can make separate surfaces look interchangeable. Cloud work, local computer access, messaging channels, and scheduled tasks have different requirements. 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.