Skip to content

Roadmap

ssobol77 edited this page May 12, 2026 · 2 revisions

Roadmap

🌍 English · Polski · Français · Deutsch · 中文

What's done, what's in progress, what's next. The authoritative engineering roadmap lives in docs/planning/roadmap.md; this page is a user-friendly summary.

Current: 0.1.x (Preview)

ECLI 0.1.3 is the first complete public release across all platforms:

✅ Linux (Debian/Ubuntu, Fedora/RHEL, generic tar.gz) ✅ FreeBSD (native .pkg) ✅ macOS (Universal2 DMG, x86_64 + arm64) ✅ Windows (NSIS installer + portable EXE) ✅ PyPI (pip install ecli-editor)

Features stabilized in 0.1.x:

  • Core editor with curses-based TUI
  • Tree-sitter syntax highlighting (70+ languages)
  • LSP client integration
  • Git panel
  • AI panel (Anthropic, OpenAI, Ollama, HuggingFace)
  • Plugin system (Python)
  • TOML-based configuration
  • Multi-platform packaging with CycloneDX SBOMs

Planned: 0.2.x (Stabilization)

Focus on quality, security, and operator features:

  • OIDC Trusted Publishers for PyPI (replace static API token)
  • macOS notarization (eliminate Gatekeeper friction)
  • Windows code signing (eliminate SmartScreen friction)
  • PyPI Markdown rendering for AI panel responses
  • Multi-cursor editing
  • AI cost tracking inside the editor
  • Configurable shell sandboxing for shell-integrated workflows
  • ARM64 Windows support
  • ARM64 Linux support (Raspberry Pi, AWS Graviton)
  • Telemetry opt-in (anonymous usage stats, off by default)

ETA: end of 2026.

Planned: 0.3.x (Extensibility)

Focus on community plugins and language ecosystems:

  • Plugin marketplace / registry
  • Theme marketplace
  • Snippet system with language-aware expansion
  • Project templates (ecli new --template python-cli)
  • Workspace concept (multi-folder projects, like VS Code's workspaces)
  • Remote LSP (run LSP servers in containers or over SSH)
  • Linting integration (Ruff, ESLint, golangci-lint, clippy auto-detection)
  • Debug Adapter Protocol (DAP) client — visual debugger

ETA: mid-2027.

Planned: 1.0 (Stable API)

The 1.0 milestone marks API stability commitments:

  • Plugin API frozen — no breaking changes without major version bump
  • Config schema frozen — backward-compatible migrations only
  • Documented stability guarantees for embedded use
  • Performance benchmarks published per release
  • Security review completed (third-party)
  • Accessibility audit (screen reader, high-contrast themes)

ETA: 2028.

Beyond 1.0

Long-term ideas (no commitment, exploratory):

  • Collaborative editing (CRDT-based, local-first)
  • AI training feedback loop (user corrections improve model selection)
  • Cross-editor protocol (interop with VS Code remote sessions)
  • Mobile companion (iOS/Android terminal client)

How priorities are set

Decisions follow this order:

  1. Critical bugs and security — always top priority
  2. User-reported pain points — collected via Issues and Discussions
  3. Strategic infrastructure — release pipeline, CI quality, supply chain
  4. New features — prioritized by user demand and engineering effort

Maintainer's discretion on tradeoffs. Major changes are discussed in GitHub Discussions before implementation.

Status of long-running tracks

Track Status
Linux native packaging ✅ Stable (DEB, RPM, tar.gz)
FreeBSD native packaging ✅ Stable (.pkg)
macOS DMG ✅ Stable (ad-hoc signed)
macOS notarization 🟡 Planned 0.2
Windows installer ✅ Stable (unsigned)
Windows code signing 🟡 Planned 0.2
PyPI distribution ✅ Stable (ecli-editor)
PyPI OIDC Trusted Publishers 🟡 Planned 0.2
AI provider integrations ✅ Anthropic, OpenAI, Ollama, HF
Plugin API 🟡 Beta — stable in 1.0
LSP integration ✅ Working, expanding language coverage
Tree-sitter highlighting ✅ 70+ languages
Git integration ✅ Read + basic write (stage, commit, push)
Git advanced features 🟡 Planned 0.2-0.3 (rebase, cherry-pick UI)
Multi-cursor editing 🟡 Planned 0.2
Documentation site ✅ ecli.io
Wiki ✅ This page :)

How to influence the roadmap

  • Open an issue describing your use case and what's missing.
  • Comment on existing issues to express demand (👍 reactions count).
  • Start a discussion for larger design questions.
  • Contribute a PR for features you need — the fastest path to inclusion.

Detailed planning

For engineering-level details:

Clone this wiki locally