The 0x Gazette: Release Edition
An editor, an AI pair, GitHub, notebooks and an extension store, with nothing to install and no project to set up before you write the first line.
Try it now: 0x.vasuki.cloud
Most developer tools ask for an afternoon before they give you anything back. 0x Loom asks for a tab.
Open it, drag a folder onto the page, and you are editing with syntax highlighting, auto-closing tags and autocomplete. Your files stay in your browser, and a reload brings back your tabs, your unsaved edits and your open folders.
The goal of this first public release is simple: make the loop from idea to running code short enough that it works on a laptop, a borrowed machine or a phone. Python and Node run on a backend, HTML and SVG preview live beside the code, and a terminal handles npm when a project needs packages.
By the numbers
| 3 | project templates: Node.js, React (Vite) and Angular |
| 15 | extensions pre-installed on first run |
| 11 | colour themes in the marketplace |
| 600 | files loaded when you clone a repository |
| 0 | installs required |
An assistant that edits, not just chats
The built-in Gemini assistant reads your open file, your selection and anything you mention with @path/to/file. When it wants to change something, it doesn't paste a wall of code. It proposes a precise search-and-replace block, and you press Accept or Reject.
If the text it wants to replace is missing or ambiguous, the edit is refused, so nothing changes by accident.
Every suggestion arrives as a diff you can accept or reject. Nothing is applied behind your back.
Several API keys can sit behind the assistant. When one hits a rate limit, Loom moves to the next. An AI Billing screen shows requests and tokens per key, so you can see a quota running out before it does.
From first commit to a live site
Connect GitHub once, then clone a repository or create a new one from a Node.js, React (Vite) or Angular template. Loom scaffolds the files and pushes the first commit.
Changes are listed file by file before you push, and build output and node_modules are never sent.
When you are ready to share, one button publishes to GitHub Pages. For projects with a build script, Loom adds the deploy workflow, watches the build and hands you the live URL.
Notebooks and a vault
The Shell opens a Jupyter-style notebook with Python and Markdown cells. It reads and writes standard .ipynb files, shares variables between cells, and saves to your browser, to disk or to a private GitHub repo.
Secrets live in your Tijori vault and can be dropped into a file at the cursor, so keys stay out of your source.
Make it yours
Extensions are plain JavaScript with a documented API for commands, panels, status items, key handlers and the AI:
Loom.ui.command('Hello', 'Say hello', () => Loom.ui.toast('Hi from ' + ext.name));
Extension Studio gives you a code editor, a live README preview, version history and a safety scan that flags vault, network and file access before anyone installs your work. Publishing is tied to a key only you hold, and anyone else can fork instead of overwrite.
Also in this edition
- Command palette on
Ctrl/⌘ Kwith text, JSON, Base64 and npm tools - Code Map: every function and variable, with all references across files
- Light and dark themes, built for phones as well as desktops
- Docs for Vasuki Traffic and Tijori in one place
Open a tab. Start building.
👉 Launch 0x Loom at 0x.vasuki.cloud
I'd love feedback: what broke, what's missing, and which extension you'd build first. Drop it in the comments.
Top comments (0)