A desktop workspacefor format-aware editing.
ReveLith is a 0.x local-first desktop workspace with nine modules: Docs, Sheets, Slides, PDF, Markdown, HTML, Forms Builder, Tasks, and AI Draw. Each editor uses its own renderer and format-specific paths; AI and automation are optional surfaces.
Source inventory, CI, and release evidence.
1,609 tracked TypeScript test files · 9 desktop modules · GitHub v0.11.2
At GitHub main commit 32f80d8 (2026-10-18), the repository tree contains 1,609 tracked TypeScript test files across apps and packages (1,596 .ts and 13 .tsx). The root npm test command delegates to workspace test scripts, and the repository also tracks Playwright end-to-end scenarios. The latest CI run for this main commit completed successfully on 2026-10-18. GitHub lists v0.11.2 as the latest published release; it is not marked as a prerelease.
1,596 .ts and 13 .tsx files at main commit 32f80d8
Root command delegates to package test scripts; Playwright E2E is tracked separately
GitHub Actions completed successfully for 32f80d8 on 2026-10-18
Published 2026-10-18; GitHub does not mark it as a prerelease
Docs, Sheets, Slides, PDF, Markdown, HTML, Forms Builder, Tasks, and AI Draw
Windows, macOS, and Linux; releases include multiple architectures
EVIDENCE_NOTE:: The 1,609 figure is a source-file inventory, not a count of test cases or passing tests. The CI result is specific to commit 32f80d8 on 2026-10-18; later commits need their own result. GitHub's v0.11.2 release tag and the 0.10.100 version declared by package.json on main describe different source points.
Complex files, editor fidelity, and AI data flow need to be considered together.
An editor can alter file details it does not model when it rebuilds a document. Provider-backed AI can also receive prompts and relevant file context. ReveLith combines local editing paths with format-specific patching where implemented, while keeping provider-backed operations as a separate, optional path.
Patch what changed. Keep what works.
Each editor has its own implementation and save behavior. Some engines patch selected changed structures; others use their own serialization or export path. ReveLith is a 0.x release, and file fidelity varies by format and feature.
One shell, separate editing and service paths.
This is a conceptual map of the implemented boundaries. The shell routes files to editor surfaces; each module owns its format-specific logic. Provider calls and automation are separate paths, and not every module supports the same operations.
Ordinary file open, edit, and save operations do not require an AI provider.
Window, tabs, file routing, and app lifecycle.
Module renderer with sandboxed, validated bridges.
Module-specific parsing, model, patch, or export path.
Source file, working data, and saved output on device.
Used only when an AI feature is invoked.
The active feature assembles its supported context and typed tool contracts.
Streams requests and results across the renderer/main-process boundary.
May be local or remote. Remote requests send the prompt and relevant context to that service.
Provider streams and tool results return over IPC to the active editor; users can review changes before saving the local file.
Automation is bounded by the selected interface and supported module operations.
Uses shared engines for supported read, edit, conversion, and render commands.
Disabled by default; when enabled, it binds to 127.0.0.1 without authentication and must not be exposed beyond the local machine.
CLI MCP supports stdio; separately configured HTTP can use a bearer token. Headless export covers listed targets, not every desktop feature.
Two paths through the system.
These traces describe specific code paths, not a promise that every format or generated result has identical fidelity.
DOCX: open, edit, patch, save
The ordinary document workflow stays local. AI assistance is an optional branch within the Docs editor.
- 01OPEN
The shell routes a .docx file to the Docs editor surface.
- 02PARSE
The DOCX engine builds a block model and maps source XML offsets for supported structures.
- 03EDIT
User edits update the local model. If Docs AI is invoked, its tool operation also returns through the editor's IPC path.
- 04PATCH
The engine targets dirty OOXML structures and keeps untouched package data where its patch path supports that.
- 05SAVE
The updated document is written to a local path. Unsupported or imported features may not round-trip identically.
AI Draw: prompt to editable scene
The provider proposes structured diagram input; ReveLith's local compiler turns that input into editable canvas elements.
- 01REQUEST
When AI diagram creation is invoked, the prompt and relevant context go to the configured model provider.
- 02STRUCTURE
The model returns arguments for a named diagram tool, such as a flow or sequence diagram.
- 03COMPILE
AI Draw compiles the structured input locally, checks geometry constraints, and creates editable canvas elements.
- 04REVIEW
The diagram remains editable in the board; the available checks help inspect structure and geometry but do not guarantee a correct diagram.
- 05SAVE / EXPORT
The board can be saved locally as a .draw document or exported to supported image formats such as SVG or PNG.
AI Draw's generated raster-image feature is a separate provider-backed path; it does not use the same native editable-diagram compiler.
Nine desktop modules. One shared shell.
The ReveLith Shell hosts these modules with tabs, recent and starred files, local folders, shared settings, and file open/save flows.
Word documents with selective OOXML patching
The DOCX engine tokenizes OOXML into a block tree, tracks XML offsets, and targets supported changed structures. Pagination, tracked changes, comments, equations, and ink are represented in the document surface, but fidelity still depends on the file and feature path.
Spreadsheet analysis with a native calculation path
The Sheets surface combines an in-house Rust calculation engine with an XLSX sidecar, dynamic charts, pivot tables, slicers, formula tracing, conditional styling, and edit/save coverage.
Presentation editing on the real OOXML model
Custom PPTX parsing and patching cover master and layout inheritance, shape transforms, image cropping, connectors, SmartArt, tables, notes, animation, and layout snapping paths.
Direct page-content editing
The PDF surface includes page-content editing, text updates, form filling, visual signature and annotation paths, page operations, and export behavior.
A technical writing surface with plain-text truth
Block-based rich editing stays synchronized with Markdown, supports images and slash commands, and exports to DOCX and PDF while retaining a transparent source format.
Source editing beside a live preview
Edit HTML alongside a live preview, refine selected elements, inspect the layer tree, and export a single HTML file or Word and PDF output.
Local forms with offline response collection
Build forms with validation, conditional fields, branching, calculations, and scoring. Keep drafts locally, export responses, or create a standalone HTML form for offline collection.
Project boards stored on the device
Organize work with configurable columns, labels, dependencies, sub-tasks, saved views, and activity history. Export boards to Markdown, CSV, JSON, or iCalendar.
Editable diagrams and visual work
Create diagrams with editable shapes, grouping, layout tools, annotations, and isometric or perspective views. Prompt-based image generation requires a compatible configured provider.
Patch supported structures; keep format limits visible.
File fidelity is format-specific. Where an engine supports targeted patching, it preserves untouched structures and writes supported changes into the original container. Imported or unsupported features may not round-trip identically, so keep a backup of important files.
Format engines and shared runtime services.
OOXML tokenizer, block tree, offset mapping, delta patching, fidelity fixtures, and round-trip verification.
Presentation parser, layout inheritance, transforms, media, tables, charts, notes, SmartArt, animation, and canvas rendering.
Multi-format text and metadata extraction that feeds searchable, context-aware AI operations.
Tool-schema contracts, streamed provider requests, multi-turn loops, skill dispatch, compaction, cancellation, truncation handling, and mutation snapshots.
Resilient streaming abstraction for local and hosted model backends, with provider settings and normalized response handling.
Web search, documentation lookup, image generation, link display, and context tools exposed to the copilot.
Shared design tokens, localized UI, validated IPC, navigation guards, safe external URLs, atomic writes, and desktop utilities.
Privacy is a runtime property.
Ordinary file operations run locally. Provider-backed requests can send prompts and relevant context to the configured service, and official packaged builds with analytics credentials send anonymous usage events by default. The privacy policy says analytics excludes document content, names, and paths; users can turn it off under Settings > General. Privileged operations remain behind narrow IPC contracts.
Ordinary file reading, editing, and saving happen locally; an AI provider is not required for those operations.
Invoked AI, search, image, and media features can send the prompt and relevant context to the configured provider. The provider's own data handling rules apply.
Official packaged builds with Google Analytics credentials send anonymous usage events by default. Events include app, platform, session, and file-extension data, not document content, file names, or paths. Users can opt out in Settings > General; source builds without packaged credentials send no analytics.
Electron renderers are isolated from privileged capabilities; system actions are exposed through narrow, validated bridges rather than arbitrary access.
Main/renderer requests use typed channel contracts, schema-checked payloads, sender/session validation, and explicit operation handlers.
External navigation and remote image retrieval validate protocols, reject private or link-local targets, and follow redirects under policy.
Same-directory temporary files and rename retries protect saves from crashes, antivirus locks, indexers, and partial writes.
Original binaries remain the source of truth for supported patch paths; intentional dirty structures are the units targeted for mutation.
Quality checks follow each implemented layer.
Engine-level tests cover OOXML patches, slide transforms, tables, media, charts, typography, Markdown nodes, agent loops, AI providers, and utility contracts.
Pagination baselines, Word fidelity scripts, visual comparisons, theme-color checks, fixture generation, and third-party license checks protect regressions.
Playwright scenarios cover onboarding, file tabs, Markdown, Sheets editing and save flows, insertion galleries, theme pipelines, and visual desktop behavior.
CI runs quality and workspace test partitions; the release workflow builds and publishes platform-specific installers.
Three OS families, multiple architectures.
v0.11.2 includes x64 and ARM64 .exe installers.
v0.11.2 includes Intel and Apple silicon .dmg and .zip builds.
v0.11.2 includes x64 and ARM64 AppImage, .deb, and .rpm packages.
Node 22.12+, npm 10+, Rust cargo, workspace scripts, targeted app dev servers, and full-suite build commands.