openeditorcode.devFIELD MANUAL / 0.2.41Español
index.md DOCUMENTATION

00 — Getting started

All of OEC, documented.

From the first file to Git history. Guides, commands and technical decisions, checked against the editor’s source.

v0.2.41Source review ·
On this page
100action records
44documented properties
21reference chapters
01

All commands

OEC actions, palette, dialogs, basic Vim and inherited keys. Search by name, key, context or configurable ID.

02

Installation and updates

Choose a channel for Windows x64 or Linux x64 glibc, including a compatible WSL distribution.

03

Complete configuration

Defaults, properties, scopes, application and valid global/project configuration examples.

04

Git history and branches

Explore commits and revisions without switching the working branch.

05

OpenCode 2 plugin

From chat to file: installation, real screenshots, local Git, diff tabs, Markdown, images and the integrated editor's complete shortcuts.

Your first session

  1. Install OEC and run oec from your project folder, or pass a path as the only argument.
  2. Explore with ↑/↓ and Enter. Ctrl+N creates a file; F2 renames the selected entry. Ctrl+Shift+→ focuses the editor.
  3. Edit and save with Ctrl+S. Markdown and SVG open in preview; F4 enters source or reviews unsaved changes.
  4. Use Ctrl+F for context-sensitive search, Ctrl+Alt+F for project text, and Ctrl+P to discover actions.
  5. Ctrl+Alt+B opens Git; Ctrl+Q ends the session and handles modified tabs.

Three ways to read

  • Guides: follow a task end to end in Explorer, Editor, Search and Git.
  • Reference: look up a shortcut, an action without a key, a CLI argument or a configuration property.
  • Under the hood: understand architecture, distribution, tests, limits and analysis findings.

A versioned reference

Standalone editor reviewed for 0.2.41, commit b5770842; its sources are pinned to that commit. The OpenCode 2 plugin is published separately: version 0.3.4, commit 84643031, with independent sources and verification. Updating the plugin does not advance the standalone editor reference.

Coverage is based on implementation and inspected tests, not certification of every terminal. Diagnostics separates code facts from static findings not yet reproduced.

Chapter sources

Links pinned to the reviewed commit; they do not follow main.

Static documentation · ES / ENView coverage ↗