Offline & connected · Buyer guide

What works offline on o1?

o1’s expressive reactions work on the device without a phone or internet. Connected AI experiences are optional betas with separate setup and connectivity requirements.

By Growit o1 Reviewed September 6, 2026 4 min read

The face responds without a phone

Picture the simplest o1 interaction: you pick it up, tilt it and watch its expression change. The working device handles its expressive reactions locally. The current product page explicitly says that tilting, shaking, carrying or setting it face-down changes its OLED expression without a phone or internet. That is the supported answer to whether o1 has an offline experience.

It does not follow that every experience shown on the website runs offline. The same page marks Sight, bringing your AI and connected tools as connected betas. Keeping those categories separate helps you decide whether o1 matches the way you actually plan to use it: as an expressive device, an interface to supported services, or both.

A practical connection map

Use the requirement for the specific experience
What you want to do	What is established	What to check
See motion-driven expressions	Works locally without a phone or internet.	Try the working device’s reactions.
Use owner-triggered Sight	Connected beta using a deliberately captured frame.	Compatible service, setup, permissions and internet.
Use a supported AI tool	Owner-configured connected beta.	Account, credentials, allowed actions and service fees.
Install updates or set up a beta	A phone, internet or setup may be required.	The instructions for that feature and hardware release.

“Works without a phone” is a statement about the local reactions. It is not a blanket promise of phone-free setup, offline AI provider access or a particular wireless connection method. Confirm those requirements against the supported experience you want.

Ask for two separate demonstrations

For the local experience, ask to see the device react to motion without a connected service. You are checking the behavior that o1 labels working today. Keep the observation concrete: which action changed the face, and did that part require the presenter to use a phone or browser? You do not need to infer unannounced battery life or other specifications from a short demonstration.

For a connected beta, ask the presenter to identify the service and show the setup requirements. Establish where the task is processed and which owner action starts it. This is especially useful for Sight: the stated design begins with your deliberate capture of one frame, followed by a compatible connected service. Ask for the current feature-specific explanation rather than assuming continuous capture or fully local vision processing.

Plan for the place you will use it

If you want the expressive face at a desk, in a bag or away from a reliable connection, the local reaction engine is the relevant feature. If you want a provider-backed task while traveling, connectivity and the supported service become part of the plan. An offline face does not provide the internet access required by a connected beta.

Before relying on a connected workflow, check how that specific experience handles an unavailable network, expired credentials or an unavailable provider. The current public materials do not establish a universal offline queue, retry policy or completion guarantee for every integration. Treat these as setup questions to answer for the actual beta, especially before asking a tool to change information in an account.

Local reactions do not describe every data flow

A local expression can work without sending a request to an AI provider. Connected features introduce a different question: what information does the supported service receive when you choose to use it? The o1 privacy notice covers the website and order services, and explicitly says device camera inputs, connected tools and third-party credentials need feature-specific explanations when offered.

That notice does not make a blanket promise that all connected-device information stays on o1. Before enabling a service, read its explanation of inputs, access and processing. Keep a shared Eye World nickname separate from personal information; its share URL can be seen by people who receive it. Website sharing, local hardware behavior and provider-backed processing are different activities with different boundaries.

Decide what needs to be connected

Write down one job you want o1 to do. If the answer is “respond with an expressive face when I carry it,” start with the working local behavior. If the answer includes reading from or acting in another service, check whether that exact experience is supported, what accounts it needs and how its permissions work. Avoid planning around Maker Path: external hardware interfaces and public developer tooling are still in development.

Use the connections and costs guide to check the extra requirements, or return to the feature-status guide for the complete distinction between working, beta and planned features. You can join the free waitlist to follow availability without paying or reserving a device. The separate Founders page explains the Arlington purchase plan.