Editor and local development

The desktop Editor opens a local VS Code workbench powered by code-server, with an Escanor theme and bundled extension. It opens in a separate window and runs on your computer, with your files and development tools.

Prerequisites and first run#

Install a released desktop package for your OS/architecture, choose a project directory you can access, and allow internet for the initial editor download. The editor is fetched separately from a pinned platform manifest and checksum-verified before extraction. The desktop installer does not include the full editor, so its archive needs additional disk space.

Open This computer > Editor, follow the install progress and choose a folder. The workbench starts locally with Escanor branding. Existing installations with the expected checksum marker are reused. Opening the editor does not install your project's language runtime or package manager.

Platform availability#

The editor is available for Linux (x64 and arm64), macOS (Intel and Apple silicon) and Windows (x64), on whichever of those the desktop app itself is released for. If an editor download is missing, returns an HTTP error or fails verification, the installation stops; do not substitute another platform's archive.

Local API and tools#

The editor's service and extension API bind to loopback with launch-specific credentials. Do not publish its port to the internet or share its credentials. Shell/file operations still depend on the computer's capability and caller permissions.

Use project version control before asking an agent to edit files. Ask for a bounded change, inspect the diff and run the project's actual checks. Written files do not tell the assistant whether a local build passed.

Practical workflow#

1. Open a small test repository in the editor.
2. Read its README and check required runtimes.
3. Ask the assistant to explain one file without edits.
4. Request a specific change with an acceptance criterion.
5. Review the approval and diff, then run tests/build locally.
6. Commit only the changes you intend to keep.

Phone requests can ask the computer to open the editor, subject to permissions. Pairing does not give the phone unrestricted editor or file access.

Troubleshooting#

• Download error: check connectivity and the error status, then retry.
• Checksum mismatch: the installer discards the downloaded file; do not bypass validation.
• Unsupported architecture: use the build for your computer's architecture. Running another architecture's build under emulation is not supported.
• Workbench fails to start: inspect executable/path access and desktop logs.
• Project tools absent: install the project's documented runtimes. The editor bundle does not supply them.

The editor synchronizes the bundled extension when it starts. Desktop updates and the pinned editor version have separate maintenance paths. Related: Updates and installation, Permissions.