Privileged host
Filesystem, Git, PTY, SQLite, and keys live in-process for Electron — the renderer stays untrusted.
Release channel — CyberAI Dev
BUILD. REASON.
SHIP.
CyberAI Dev is a private AI development environment — Mission Control, a dense workbench, and a privileged host that never puts API keys in the renderer.
Only currently published installers are enabled
Workbench
Workbench
Click a region. Honest product surfaces — no invented latency.
Editor
Bundled Monaco with find, replace, replace-in-files, a resizable split, and Problems from real markers.
The workbench
The workbench
Six real capability tabs. Each pane demonstrates what CyberAI Dev actually does today.
// Files stay inside the approved workspace.
const selected = "middleware.ts";
Local explorer selection only — no filesystem request is made here.
Switch Explorer, Search, Source Control, Debug, and CyberAI from one rail — the same density as a professional workbench.
Workbench tour playing.
CyberAI Agent
CyberAI Agent
Ask, Plan, Edit, Agent, Debug, and Review — the real path a task takes end to end.
1
Request
Ask, Edit, or Agent mode receives your task, scoped to the open workspace.
2
Context retrieval
Relevant files and repository structure are gathered from the local workspace.
3
Plan
Agent mode produces a step-by-step plan you can read before anything runs.
4
Edit
File edits are applied on the privileged host and streamed back as diffs.
5
Validate
Problems markers, the debugger, and terminal output surface issues immediately.
6
Review
You approve or reject each diff before it is committed to your repository.
Model routing
Model routing
Tasks route by complexity and configured provider availability — no cost-savings claims, just routing.
CyberAI Dev picks a tier by task complexity and your configured providers.
Product facts
v0.3.0
Published version
3
Available installers
Host
Privileged host
0
Keys in renderer
Built for private work
Built for private work
Mission Control
Open or clone a folder, see host status and usage, then drop into a dense IDE.
Local-first
Workspaces stay on your machine. Pairing is for the browser companion, not the packaged desktop.
Honest download
Download actions appear only for configured local artifacts or published release assets.
Security architecture
Security architecture
The real path from UI to disk — no certifications claimed, just the architecture as built.
Renderer
The UI runs untrusted, with no filesystem, shell, or API-key access of its own.
Typed bridge
A narrow, typed IPC contract is the only path from renderer to host — no arbitrary calls.
Electron host
Filesystem, Git, PTY, SQLite, and provider keys live in the privileged main process.
Approved workspace
Filesystem and shell actions are scoped to the folder you explicitly opened or cloned.
The CyberAI ecosystem
The CyberAI ecosystem
CyberAI Dev is one product inside a single account — website, desktop, and dashboard share one identity.
CyberAI Website
Dev Product Page
Download
Desktop
Account / Usage / Billing
Web Dashboard
Download
Download CyberAI Dev for Windows, macOS, or Linux. Sign in with your CyberAI account after install.
FAQ
Common questions
No. It is an original CyberAI implementation — local-first IDE, repository control, and a privileged host.
Use the official download buttons on this page. A platform is downloadable only when the release feed or deployment configuration provides an artifact; unavailable platforms stay disabled.
Signed-in users can open /dev/desktop-handoff. A one-time code is exchanged for a hashed desktop session — no second OAuth app.
Not by default. Files, local paths, indexes, conversations, terminal history, and provider keys remain on your device. Selected context is sent when you invoke an AI provider or connected tool, and available account sync may send opaque workspace and usage metadata.
With bring-your-own-key providers, charges, quotas, and provider terms belong to the account whose key you configure. CyberAI Dev does not promise provider pricing or capacity. The dashboard shows cost only when verified pricing is available.
No. Generated code and commands can be wrong, insecure, destructive, or affected by third-party licenses. Review diffs, test in a safe environment, keep backups, and approve only actions you understand.