Ocody
Ocody is a browser-based live coding partner. You share your screen, talk to it, and it answers out loud, powered by Google's Gemini 2.0 Flash multimodal live API. No install, no account to start, and a permanent free tier.
What is Ocody?
Ocody is a live coding assistant that runs entirely in a browser tab. Rather than pasting a snippet into a chat box, the user shares a screen — an IDE, a terminal, or whichever browser tab is misbehaving — and talks to the assistant out loud. The assistant answers out loud too: the response modality is audio, delivered through a prebuilt synthetic voice. A webcam feed can be streamed alongside the screen.
Underneath, the product is a thin layer over Google's Multimodal Live API. The console calls gemini-2.0-flash-exp through generativelanguage.googleapis.com, and the browser tab still carries the title of the Google sample it was built from, Multimodal Live - Console. Two tools are declared to the model: Google Search grounding, so a point can be looked up during the conversation, and a render_altair function that draws a Vega-Lite chart into the main pane on request. A settings panel exposes the voice, the response modality, the system instruction and the function declarations, all editable — but only before the session connects, as the panel itself warns.
The shipped system instruction casts the assistant as a patient coding-support specialist that reads a snippet, relates the question to it, and answers without asking follow-up questions. That deliberate patience is the positioning: the homepage promises guidance that adapts to the user's skill level and learning style rather than raw throughput, and describes the product as a partner available around the clock.
The surface area is deliberately small. Five routes exist — the homepage, the console, a plan-and-payment screen, sign-in and sign-up — and nothing else. Accounts run on Auth0, payment on a Stripe buy button, and feedback through an external Formbricks form reached by a link labelled "feedback plz". There is no documentation, no product tour, no blog, and no legal section of any kind.
Maturity deserves a careful read. The tool wears a beta badge beside its logo, the domain was registered on 6 June 2025, the first Wayback capture dates from 10 July 2025, the meta description is still the create-react-app default, and the Auth0 tenant is a development tenant. The site is a single-page React application served by Netlify and deployed through Windsurf, so any crawler requesting any URL receives the same empty 1,255-byte shell.
What it does
- Share your screen with the assistant in one click, whether it shows an IDE, a terminal or a browser tab
- Talk to it and get a spoken answer back, since the response modality is audio with a prebuilt synthetic voice
- Have a code snippet read and diagnosed while it is still on screen
- Add a webcam feed alongside the screen when something has to be shown physically
- Get a point looked up on the web mid-conversation, through the Google Search grounding tool declared to the model
- Ask for a chart and have it drawn into the main pane, through a render_altair function that outputs Vega-Lite
- Rewrite the system instruction and the function declarations from the settings panel before connecting
When to use Ocody / When not to
A quick filter to help you decide if Ocody is the right fit.
When to use Ocody
- Developers who are stuck right now and want an answer in seconds, without opening a ticket or waiting for a colleague to free up
- Solo developers, freelancers and one-person teams with nobody nearby to show their screen to
- Beginners and career changers, since the assistant is explicitly tuned to adapt its guidance to the user's skill level and learning style
- Students and interns, who can open the console and start working without creating an account or installing anything
- People who think better out loud than in writing: the assistant listens and replies in a synthetic voice, leaving both hands on the keyboard
When not to use Ocody
- Anyone working on confidential or client-owned code, because the tool asks for a screen share and offers no contractual commitment whatsoever in return
- Teams whose tooling must clear a legal or procurement review: there are no terms of service, no privacy policy, no DPA and no certification of any kind
- Developers who want the assistant inside their editor, since there is no VS Code plugin, no JetBrains plugin and no browser extension
- Anyone expecting repository-wide understanding: Ocody sees what the screen shows and hears what it is told, and never connects to a codebase
- Organisations that need a stable, supported vendor, given the beta badge, the unidentified publisher and a domain registered in June 2025
How to use Ocody
A typical end-to-end flow, from setup to results.
- Open 0cody.com and click "Start Coding Now", or go straight to the /app console
- Note that no account is required at this stage: the console opens for anyone
- Before connecting, open the settings panel if you want to change the voice, the response modality, the system instruction or the function declarations
- Set those options now, because the panel locks them once the session is connected
- Grant the browser access to your microphone, then start streaming
- Click the screen-share control and pick the window to broadcast: your IDE, your terminal or a browser tab
- Switch on the webcam instead, or in addition, if something has to be shown physically
- Talk to the assistant: ask about the code on screen, request a diagnosis, or ask for a chart to be drawn
- Listen to the spoken answer and watch any requested chart appear in the main pane
- For sustained use, sign in through Auth0 and pick a plan on the payment screen; use "feedback plz" to report anything broken
Pros & Cons
Pros
- Nothing stands between the user and a first session: no install, no download, no account, no API key
- Showing beats describing — screen sharing removes the whole ritual of reproducing a bug in prose or pasting the right lines
- The spoken exchange leaves both hands on the keyboard, which matters when the problem is being fixed while it is discussed
- The free tier is a permanent plan at 0 USD per month rather than a countdown, so the tool can be tested at no financial risk
- The system instruction and function declarations are exposed and editable, which is rare and genuinely instructive for anyone learning how these models are steered
- The underlying stack is real-time multimodal Gemini with web grounding, not a text-only wrapper
- The price grid is short, legible and free of any "contact us" tier
Cons
- No terms of service, no privacy policy, no legal notice: the contractual vacuum is total, which is disqualifying for professional use
- No email address exists anywhere on the site, so the only channel is an external feedback form
- The publisher is unidentified: no company name, no address, no named founder
- The marketing site is a single page with no documentation, no product page and no changelog
- The site is effectively invisible to search engines, since every URL returns an empty shell and the meta description is still "Web site created using create-react-app"
- The browser tab still reads "Multimodal Live - Console", the title of the Google sample the console was forked from
- Several signals point to a prototype rather than a product: an experimental model build, a development Auth0 tenant and a beta badge
Pricing & Plans
Ocody offers a permanent free plan at 0 USD per month, capped at 10,000 tokens per month. The cheapest paid tier is the Starter plan at 19.99 USD per month for 50,000 tokens, and the highest published tier is the Pro plan at 80 USD per month for 200,000 tokens. Billing is monthly and quoted exclusively in US dollars; no annual commitment is proposed and no time-limited free trial is advertised, the free tier being a standing plan rather than a countdown. These amounts appear only on the client-rendered payment screen, as the site publishes no static pricing page.
- 10
- 000 tokens per month
- basic API access
- community support
- 1 project
- 50
- 000 tokens per month
- full API access
- email support
- 5 projects
- 200
- 000 tokens per month
- full API access with higher rate limits
- priority email and chat support
- unlimited projects
- advanced analytics
- the "API access" mentioned in every tier is not backed by any published documentation or endpoint
- and appears to describe a quota of model calls rather than an API exposed to the customer
Data, GDPR & hosting
A consolidated view of how Ocody handles your data.
GDPR overview
There is no mention of the GDPR anywhere on the site, and this should be stated plainly rather than softened: a search of the complete first-party bundle returns zero occurrences of "GDPR", "RGPD" or "privacy policy". No privacy notice, no legal notice, no Article 27 representative, no data protection officer and no contact address exist. No list of processors is published, although the service demonstrably relies on at least three: Google for the model, Auth0 for accounts and Stripe for payment. Nothing is said about retention, deletion, international transfers or the use of user data for model training, and no opt-out is offered. The Auth0 tenant is moreover a development tenant, not a production one. For any European organisation, this is a blocking gap rather than a documentation detail.
Who owns the data?
Nothing is published on this point, and the silence is total. Ocody has no terms of service and no privacy policy: the /terms, /privacy and /legal paths all return the same empty single-page shell, and a search of the site's entire first-party JavaScript bundle returns zero occurrences of "terms", "privacy policy" or "GDPR". No clause states who owns the shared screen captures, the audio stream or the code discussed, nor what the publisher may do with them. In practice a third party is unavoidably involved, since the session streams to Google's generativelanguage.googleapis.com, yet the publisher discloses no processor at all. The site also lists no email address, so there is no channel through which to ask.
Reuse rights
There is no contractual framework in either direction. Because no terms of service exist, nothing grants the user a licence over what the assistant produces, and nothing restricts it either. Users cannot point to a clause permitting commercial reuse of the answers, snippets or charts they obtain, and the publisher has equally waived the chance to reserve any right. Anyone who needs a defensible position on the ownership of generated output should treat that vacuum as a risk rather than as permission.
Data retention & training
Hosting summary
The publisher declares nothing about hosting: the site contains no statement about where data is stored, in which jurisdiction, or under which safeguards. What can be observed from the outside describes delivery, not storage. The apex domain resolves to 63.176.8.218, an Amazon address in Frankfurt, Germany, and the response headers identify Netlify's edge; www.0cody.com redirects to 0cody.windsurf.build, showing the site was deployed through Windsurf. That German address is a content delivery node and must not be read as a data residency guarantee. The parts that actually process user content sit elsewhere again: the live session streams to Google's generative language endpoint, accounts are held by Auth0 on a US-region tenant, and payments run through Stripe. No region can be chosen, no data residency option is offered, and no processor is named by the publisher itself.
Things to keep in mind
Risks and trade-offs to weigh before adopting Ocody.
- A screen share exposes far more than the code in focus: API keys, access tokens, customer names, email notifications and every other window you forget is visible
- Nothing in writing says what becomes of those captures, how long they are kept, or whether they feed model training
- The session streams to a third party, Google, that the publisher discloses nowhere, so users cannot know who processes what
- There is no way to request deletion of anything, since the site publishes no email address and no privacy contact
- An endlessly patient partner available around the clock can quietly erode the habit of reading a stack trace and searching for yourself
- The deliberately encouraging tone makes a wrong answer feel reassuring, which is hardest to detect precisely for the beginners the product courts
- An experimental model build and a beta product mean unstable answers and a service that could disappear without notice
Setup & Integrations
Technical difficulty
Setup is as light as it gets. There is nothing to install, nothing to download and no API key to supply: a browser is the whole requirement, and the console opens directly. The only permissions involved are the browser's own, for the microphone, the screen share and optionally the webcam. The advanced settings — system instruction, function declarations, voice — are optional, but they must be set before the session connects, since the panel locks them afterwards. An Auth0 account and a payment card are needed only to move onto a paid plan.
Deployment
Supported languages
Behind Ocody
Resources
All the official URLs gathered for verification and reference.
Frequently asked questions
Do I need an account to try Ocody?
Which model does Ocody run on?
How do I show the assistant my code?
Does it really talk?
What does it cost?
Is there a free trial?
Is there an IDE extension or a mobile app?
What does the publisher say about my data?
Who is behind Ocody?
How mature is the product?
Should you pick Ocody?
Ocody is built on a genuinely good idea, and one that surprisingly few tools serve: when you are stuck, showing your screen and talking is faster than writing a careful description of your bug. The execution follows through on the interaction itself. The console opens without an account, the screen share works in one click, the assistant listens and answers out loud, and the settings panel exposes the system instruction and function declarations in a way most products hide.
What it does not do is build much of its own on top of Google's building block. The console is recognisably the Multimodal Live API sample, and the seams show: the browser tab still carries Google's title, the meta description is still the create-react-app placeholder, the Auth0 tenant is a development tenant, and the model is an experimental build. The marketing site is one page, and every other URL returns an empty shell.
The blocking issue is elsewhere. This is a tool that asks to watch your screen, and it publishes no terms of service, no privacy policy, no retention rule, no processor list and no contact address. The publisher is not identified. A screen share exposes far more than the file in focus — API keys, tokens, client names, whatever else is open — with no written commitment in return. That asymmetry, not the beta badge, is what should decide the matter.
The reasonable position is therefore split. As an experience, Ocody is worth twenty minutes on a scratch project, and the permanent free plan means it costs nothing to judge. As a working tool, it belongs nowhere near confidential code or client work, at least until the publisher identifies itself and publishes the documents any service handling a live screen feed should have had from day one.
- Choosing a selection results in a full page refresh.
- Opens in a new window.