Skip to content

Milestones

List view

  • TUI counterpart to milestone #8 (GTK ShellApp Event Dispatch). Migrate src/tui_main from the hand-rolled run()/event_loop() (~2,100 lines) onto quadraui::ShellApp + tui::shell_runner::run_with_shell, deleting vimcode's copy of raw-mode bootstrap, terminal construction, frame timing, and the outer loop. Carved out of #7 Platform-Neutral to keep that milestone bounded. Tracked by epic #595; Stage 0 (dormant TuiShellApp scaffold) landed 2026-07-23.

    No due date
    12/14 issues closed
  • Carved out of #7 Platform-Neutral: the #448 Relm4→ShellApp::handle(UiEvent) migration and its regression follow-ups. Tracks #448 (parent), #540 (phase C, merged/needs closing), #544 (D — click bugs), #553 (F — tab click), #554 (G — scroll invert), #555 (H — breadcrumb), #556 (I — taskbar icon), #557 (J — activity bar icon). Closed: #538, #539, #552.

    No due date
    8/8 issues closed
  • Eliminate vimcode's per-backend code (src/gtk/, src/tui_main/) by adopting shared quadraui APIs and deleting bespoke implementations. The vimcode-side counterpart to #5 (Cross-Platform UI Crate builds quadraui itself; this milestone consumes it). North star: GOALS.md.

    No due date
    67/76 issues closed
  • Host the claude-coordinator pipeline board inside vimcode via a shared quadraui Board component; drive refine→plan→work→review→merge from either coord-tui or vimcode at parity, with in-editor code review as the differentiator. Design: docs/COORDINATOR_INTEGRATION.md

    No due date
    0/11 issues closed
  • Extract vimcode's UI layer into a standalone crate (working name: quadraui) with native-feel Windows, Linux, macOS, and TUI backends. See docs/UI_CRATE_DESIGN.md. Sibling to #45 (crate extraction).

    No due date
    65/76 issues closed
  • New editor features — terminal maximize, minimap, picker navigation, etc.

    No due date
    2/6 issues closed
  • vimcode.org improvements — screenshots, search console, directory submissions, launch announcements

    No due date
    0/8 issues closed
  • Extract vimcode-core as a standalone crate — hit regions, abstract event layer, proof-of-concept consumer

    No due date
    5/8 issues closed
  • Systematic Vim behavior testing — operator/motion matrix, Lua API, Neovim test mining, coverage audit, fuzzing

    No due date
    47/50 issues closed