Documentation

Everything you need to install, build, and contribute to Land.

Get Started in Minutes

The README walks you through installation, first build, and the fifteen-element architecture. No prior Rust or Tauri knowledge required.

Report a Bug or Request a Feature

Open an issue on GitHub. The team monitors daily and labels good-first-issue tasks for new contributors.

Rust API Reference

Browse generated rustdoc output for Mountain, Echo, Air, and 11 more Rust crates.

Start

Introduction

What Editor.Land is, how it is built, and what is source-backed today.

Getting Started

How to build and run Editor.Land from source on macOS or Windows.

Installation

Build requirements and source installation steps for macOS and Windows.

Quickstart

What you can do after a successful source build on macOS or Windows.

Architecture

Architecture Overview

How Editor.Land's elements fit together: Mountain, Cocoon, Sky, Air, and typed IPC.

Local-First Protocol

Air Daemon protocol design: discovery, sync, and conflict resolution.

Usage

Configuration

Settings, keybindings, themes, and language configuration in Editor.Land.

Development

Extension Development

Build and test extensions for Editor.Land using the VS Code extension toolchain.

API Reference

VS Code extension API coverage in Editor.Land: what works, what no-ops, and what is not yet implemented.

Community

Contributing

How to contribute code, documentation, or translations to Editor.Land.

Support

Troubleshooting

Common issues and their solutions when running Editor.Land on macOS or Windows.

Element

Mountain

The Rust + Tauri native shell for Editor.Land, with native services, IPC, and the Cocoon extension-host bridge.

Cocoon

The Node.js extension host that runs unmodified VS Code extension entry points through Effect-TS services and Vine IPC.

Wind

The Effect-TS service layer that provides typed workbench interfaces to Sky.

Sky

The Astro workbench UI that renders the editor interface inside WKWebView (macOS) or WebView2 (Windows).

Air

Rust background services for updates, downloads, integrity checks, authentication, indexing, health, and Vine IPC.

Echo

The work-stealing task scheduler embedded inside Mountain's Rust binary.

Vine

The protobuf schema and bidirectional gRPC transport layer connecting Mountain and Cocoon.

Grove

The Wasmtime extension-host path - capability-based security for Editor.Land extensions.

Common

Shared Rust and TypeScript contracts used across Editor.Land elements.

Mist

Local DNS, resolver, WebSocket, zone, and forward-security code for Land.PlayForm.Cloud service boundaries.

Rest

OXC-based TypeScript transform work for Editor.Land's output pipeline.

Output

The VS Code build transformation pipeline that adapts VS Code's compiled output for Editor.Land's native stack.

SideCar

Cross-platform Node.js binary distribution compiled per target triple.

Worker

Browser-worker support for cached assets and CSS import handling where the web shell needs it.

Maintain

The build orchestrator with Rhai scripting and deterministic output.

Technology

Why Rust

Memory safety without garbage collection, native speed, and fearless concurrency.

Why Tauri

The operating system WebView instead of a bundled Chromium runtime.

Why Effect-TS

Typed errors, structured concurrency, and dependency injection for TypeScript.

Why gRPC

Typed contracts at the wire: one schema for Rust and TypeScript callers.

Why WebAssembly

Capability-based extension isolation through a runtime boundary.

License

Why CC0

Public domain dedication: fork it, ship it, sell it, no restrictions.

How Land Replaces VS Code's Electron Stack

VS Code runs on Electron: a Chromium browser, a Node.js runtime, and an extension-host model. Land replaces those pieces with independent elements while preserving the VS Code extension API as the compatibility target. Browse individual elements in the Element section above, or explore the workspace on GitHub.

Mountain Cocoon Wind Sky Air Echo Common Vine Mist Rest Output Grove Worker SideCar Maintain

View all repositories ↗

Backend Services

Four Cloudflare Workers power the Land backend infrastructure:

Auth↗ - OAuth 2.0, JWT session tokens, and Auth0 integration
Download↗ - Binary distribution, release metadata, and update checks
Status↗ - Health checks and uptime monitoring
Analytics↗ - Privacy-first usage telemetry routed through Cloudflare Analytics Engine