Start with the status, not the feature name
The shortest reliable O1 buying path is: check the feature-status ledger, map any connected requirements, then review the current purchase and support terms. If a final specification or commercial detail says TBD, do not substitute an older Oneira page, event offer, render, or assumption.
O1’s current public record spans several kinds of evidence. Local motion-driven expressions are described as working. Compact local AI is prototype-stage. Vision and supported tool workflows are connected betas. Eye World is a browser preview. Maker Path is in development. Current public price, release date, and final production specification remain TBD.
Those categories answer different questions. A person interested in O1 as an expressive object may care most about local reactions. A buyer interested in a specific AI workflow needs the service, account, permission, connectivity, privacy, and separate-cost map. A developer interested in external hardware interfaces should not plan around Maker Path until current documentation publishes an interface and date.
Choose the guide that matches your decision
First read
Specs and feature status
See what is working, prototype, connected beta, preview, planned, or still TBD.
Setup
Offline, connections, privacy, and costs
Separate local expression from provider-backed workflows, accounts, data flows, and possible third-party fees.
Before paying
Buying, drops, delivery, and support
Understand waitlists, entry windows, purchase allocation, checkout checks, policies, and order help.
Evidence
Build log and open questions
Read the claim method, documentation milestones, media-provenance conflict, and known gaps.
Identity
Oneira to Growit O1
Learn why the earlier name remains visible and why legacy prices and claims do not automatically transfer.
Comparison
O1 vs Rabbit R1
Compare current public facts, maturity, interaction, connectivity, price status, and evidence without pretending a side-by-side test occurred.
Common questions and the right next page
- “What can O1 do right now?”
- Use the status ledger. It replaces the older capability guide with a claim-by-claim record.
- “Does O1 work without my phone?”
- Read the offline boundary. Local reactions and connected services have different requirements.
- “Will my preferred AI provider work?”
- Use the connected-workflow checklist. A provider logo or category is not confirmation of current support.
- “How much is O1?”
- Current price is TBD. Use the buying guide and trust only the current live checkout total when sales open.
- “Did Oneira become O1?”
- Yes, as a product-name and publishing migration. Read the migration record for the limits of that statement.
- “Who built it?”
- The public record identifies the Growit founder but not a complete technical roster. See founder and product history.
Why these guides repeat limitations
A status label is part of the fact. “Two ESP32-S3 processors” without “current design; final production specification TBD” sounds like a locked retail specification. “Works offline” without “local motion-driven expressions” sounds like every AI workflow runs on the device. “No O1 subscription planned” without third-party service costs sounds like the full experience must be free.
The guides therefore use direct, repeated distinctions instead of varied marketing synonyms. This is intentional. Search pages, AI answers, comparison tables, and social posts often remove surrounding context; keeping the qualification close to the claim makes the excerpt safer to quote.
Current unknowns: price, release date, general production availability, final dimensions, weight, battery, certifications, included accessories, and manufacturer of record. The shared fact record stores these as null, and public pages display them as TBD.
How the guide library stays current
Product, purchase, privacy, and provider facts can change quickly. Each guide shows a visible reviewed date and links to the first-party source that controls the claim. A substantive update should change the shared fact record first, then all dependent pages. This reduces drift between the press room, specs page, comparison, and buyer guidance.
Older guides about “what O1 can do,” “offline and connected,” and “connections and costs” are consolidated into the current ledger and merged setup guide. The old URLs redirect rather than competing with the current source. That keeps bookmarks useful while giving readers one maintained answer.
To report a stale claim, send the page URL, disputed sentence, and current source to growit@growit.lol. For launch emails, use the free O1 waitlist; joining it does not reserve a unit, enter a drop, guarantee selection, or take payment.