Browser IDE
Review and steer an agent session from a browser with the small IDE venom serve hosts at /v1/ide, and what it can and cannot do.
venom serve hosts a small IDE at /v1/ide. It runs in your browser on the machine that runs the server, over the same HTTP and SSE API every other client uses.
export VENOM_SERVER_TOKEN=$(openssl rand -hex 32)
venom serve --root ~/work # prints "browser IDE at http://127.0.0.1:8790/v1/ide"Open the address, paste the token, then pick a running session or start one in a directory under a --root.
Panes
| Pane | What it does |
|---|---|
| Files | The session's workspace, folders first, one folder at a time. .git is hidden. |
| Editor | A plain text editor (Ctrl or Cmd+S saves). UTF-8 text files up to 512 KiB. |
| Agent edits | After each turn, the files the agent changed, from the turn's checkpoint. Click one for a line diff. Accept keeps the edit (it is already on disk); Reject puts the old text back, or deletes a file the agent added. |
| Terminal output | The shell commands the agent ran and their output, live. Read only. |
| Agent | The chat, streamed from the session's events. Send a message (Ctrl+Enter), steer while it works, or stop it. |
Permission questions appear in the chat as a card with Allow once, Allow for session or Deny. The answer goes to POST /v1/sessions/{id}/approvals/{approvalId}, the same call a script would make.
Security
- The page holds the token in memory only and sends it as a bearer header. It never goes into a URL, a cookie,
localStorageor a log; a reload asks again. - The server binds
127.0.0.1unless you pass--host. The page itself needs no token; every API call does. - One HTML document with inline CSS and JavaScript, system fonts, and a Content-Security-Policy that allows only its own origin. Nothing loads from a CDN.
- File endpoints take workspace-relative paths and refuse
.., absolute paths, symlinks out of the workspace and anything under.git(403 path_outside,path_protected). - The session's permission rules apply: reading needs an
allowread verdict, so secrets and denied paths stay out of the page. Saving, rejecting and deleting need a write verdict other thandeny.
API
Besides the session, events, approvals and changes endpoints, the page uses these (marked x-venom-browser: true in the OpenAPI file, with no method in the Python or TypeScript clients):
| Method and path | What |
|---|---|
GET /v1/ide |
The page (no auth). |
GET /v1/sessions/{id}/files?path= |
One directory: {path, entries: [{name, type, size?}], truncated?}. |
GET /v1/sessions/{id}/file?path= |
{path, content, size}; 413 too_large, 400 not_text, 403 read_denied. |
PUT /v1/sessions/{id}/file |
{path, content} returns {path, size}; 403 write_denied. |
DELETE /v1/sessions/{id}/file?path= |
Delete a regular file. |
Limits
It is a review-and-steer surface, not a full editor: no syntax highlighting, no language server, no multi-file search, no terminal input. Keeping it a single dependency-free page means it works with the network unplugged.