PixelOkayBROWSER IDE AI COPILOT
Tools

DEVELOPER TOOLS / BUILD & PREVIEW

Browser IDE

Import a project ZIP, navigate and edit source, preview browser code, and work with a supervised AI coding agent. Run a local model with WebGPU—or explicitly connect your own endpoint.

On-device workspace◇ Sandboxed live preview✦ Review-before-apply AI⇩ ZIP / JSON export
⌘Starting…
index.htmlHTMLBrowser previewLn 1, Col 1
PREVIEWNot running
Sandboxed previewindex.html
CONSOLE0
PixelOkay project console. Type help for commands.

Build without the setup.

Make small websites, interactive demos, experiments and learning projects. Your code runs in a restricted iframe — not on PixelOkay's server.

HTML / CSS / JavaScriptOptional local AIReviewable AI editsES modulesProject autosaveNo uploads

About package support

When network access is enabled, pinned ESM packages can load from esm.sh. This is not a complete npm or Node.js environment: filesystem APIs, native binaries, arbitrary shell commands and local build tools are not included.

Preview code is untrusted. Only run code you understand; enabling networking allows it to communicate with outside services.

Does the AI Copilot need an account or paid API?

No account or paid API is required for the optional local WebGPU route, but your device needs a supported GPU and browser. The open-source model and engine download on demand. You can also configure a trusted custom OpenAI-compatible endpoint; provider requirements, costs and privacy policies belong to that endpoint. The assistant never applies edits without your approval.

What information can an external AI endpoint receive?

Only after you explicitly authorize it, the selected source context, your prompt and a bounded portion of the earlier chat are sent to the URL you entered. Files with common secret-like names are excluded, and common credential patterns are masked in source and chat. This is not comprehensive data-loss prevention; review the exact outgoing messages before sharing. Review code before sending. API keys are not saved in project files or local storage.

Can AI write, debug, test, complete and refactor a project?

Yes, the optional assistant can propose complete text-file edits, explain code, suggest fixes and tests, produce documentation and discuss security or accessibility. Suggestions must be reviewed and applied manually; no generated code is automatically executed. Local diagnostics work even with AI disabled.

What can the Browser IDE run?

HTML, CSS, regular JavaScript, and ES modules with local relative imports. Python, Java, C/C++, Go, Rust, PHP and many other text languages can be edited and searched, but not executed or compiled here. Use external ES modules by explicitly enabling network access. TypeScript/JSX compilation, Node APIs, shell access, server-side code, and package installation are not supported in this baseline.

↑ ↓ Navigate · Enter Open · Esc Close · Ctrl+P Files · Ctrl+Shift+P Commands

Local checkpoints

Project-operation snapshots saved in this tab for quick recovery. Not Git history; close the tab or reload and these snapshots are lost. Export ZIP for a durable backup.

New file

Use a relative path such as components/button.js.

Packages & sandbox

Pin a package to an exact version (e.g. lit@3.2.0). Available only when explicitly allowed below.

Confirm

Using Browser IDE

Edit a small multi-file text project and preview HTML in a browser sandbox. Export a ZIP/JSON backup, or optionally ask for a proposed code change and review each file diff before applying it.

  1. Create or import a text-code project, then browse, search and edit its files in the workspace.
  2. Preview HTML with network access disabled by default; if using an optional AI workflow, choose the provider, review what context is sent and inspect proposed file diffs before applying changes.
  3. Export a ZIP/JSON project backup and save a separate copy of important work.

Example: Import a small landing-page project, find and edit its navigation CSS, preview the result with networking disabled, then export a ZIP backup after reviewing the changed files.

Limits and privacy: This lightweight IDE has no shell, Git, Node runtime or full language server; it is not a general development environment. Binary archives and very large files exceed its text-project support. Preview networking begins disabled; enabling remote packages changes that boundary. Optional WebLLM downloads external model files and needs compatible WebGPU, while a consented remote chat provider receives the selected reviewed context. Real model inference and durable IndexedDB persistence remain unverified.

Related tools

LOCAL AI SETUP

Set up AI on this device

First, a model needs to be loaded on your device

Browser IDE AI runs on your device. The first setup may download hundreds of megabytes of model files. Later visits can reuse cached files, but the model still has to load into memory.

  1. 1. Check device
  2. 2. Download / cache
  3. 3. Set up assistant
  4. 4. Start coding

Device & model resources

Measurements may be approximate
Device RAM / model memoryChecking device information…

Live system RAM, model RAM and GPU memory are not reliably exposed in browsers.

Browser website storageChecking storage…

Site-wide estimate; includes other PixelOkay tools and is not RAM.

ONE ACTION · ALL RECOGNIZED AI MODEL DOWNLOADS

Free AI model storage across PixelOkay

Scan this website origin for WebLLM and Transformers.js model caches, plus recognizable model files in other cache buckets. This includes caches from other PixelOkay tools, not only Browser IDE. No site data or browser databases are cleared automatically.

Run a scan to see how many model caches can be cleared together.

Browser-native models and unknown IndexedDB/OPFS or private runtime caches may remain. Unknown application/user storage will not be deleted. Other running tools might redownload caches; close their tabs first.

Having trouble downloading or loading AI?

Old or incomplete AI model downloads may be using your browser's storage. First refresh the storage meter or try a smaller model. If setup still fails, inspect and remove recognized AI model caches with confirmation, then download again.

Only model caches are targeted. Other PixelOkay tools may need to redownload their models. Never clear all website data without exporting important chats and projects first.

Select “Check device” to see whether the current model can run.
CROSS-TOOL MODEL CACHE CLEANUP

Delete all recognized AI model downloads?

Deleting these caches will cause other PixelOkay tools to download their models again. Loaded AI sessions in other tabs may be disrupted. Unidentified model caches and browser-managed models may remain.

Data-loss caution: This action does not intentionally delete saved chats, projects, drafts, localStorage or IndexedDB. Do not clear website data unless you have backed up work; clearing all website data may permanently erase saved work.