Apps
Three ways to use codai — the desktop app, the browser at app.codai.ro, and the Android app — and which one to pick.
codai runs where your work is. The desktop app does things on your computer (files, shell, browser, Windows apps). The web app at app.codai.ro is the same interface in a browser tab — chat anywhere, and drive a desktop that is signed in with the same account. The Android app uses your phone for you: it reads the screen, taps, types and asks before anything risky.
All three speak the same shared-sessions protocol, so one conversation can be watched or steered from any of them.
Desktop
Windows installer with signed auto-updates; Linux packages. Files, shell, browser, computer use, a code workbench.
Web (app.codai.ro)
Sign in with your codai account, chat from any browser, run agents on a connected desktop.
Android
APK from GitHub or Google Play. Phone control through the Accessibility service, on-device model optional.
Verify downloads
Checksums and minisign signatures — what is actually signed, per platform.
FAQ
Safety, costs, leases, REMOTE badges, permissions.
Which one should I pick?
| You want to… | Use |
|---|---|
| Edit code, run commands, review diffs before they land | Desktop (Developer skin) |
| Chat with codai and occasionally ask it to do something on your PC | Desktop (Assistant skin), or Web with the desktop open as a host |
| Use codai from a machine where you cannot install anything | Web — chat only until a desktop host is online |
| Let codai use apps on your phone, read notifications, set alarms | Android |
| Start a task on your PC while away from it | Android or Web → dispatch to the desktop |
| Watch a task that runs on your phone from a big screen | Desktop or Web (the session shows a REMOTE badge) |
What they have in common
- One account, one key per device. Signing in mints a
codai_key for that installation; signing out revokes it. Every device is listed in hub.codai.ro → Security → Devices, where you can revoke one you no longer recognise. - Ask before acting. Shell commands, file writes, browser actions, messages and payments show an ask card first. Anything that is not a clear "yes" counts as a deny.
- Shared sessions. Exactly one device executes (it holds the lease); the others follow the live transcript. Roles are owner / editor / viewer.
- No analytics SDK in any of the three apps. What leaves the device is what the model needs: your request, the conversation, tool results, and the step mirror for your other devices.
- Open source (Apache-2.0): codai-desktop, codai-phone, codai-protocol.
Prefer the API? Everything the apps do goes through the public gateway. The apps are clients, not a separate service.
Scopes and claims
Every scope auth.codai.ro issues, what the user sees on the consent screen, which claims and resources each one unlocks.
Desktop
Install codai desktop, sign in, pick a skin and an autonomy level, use computer control, serve as a host for your phone and the web app, update and uninstall.