Where GraphoOS
is going.

0.5 M Build on Linux (docker buildx bake ubuntu-noble) and Windows (VM or runner).

Binaries for all 3 OSes launch.

0.7 M Turn on CI in Empoorio/graphoos: fmt, typos, clippy on 3 OSes, build on 3 OSes, doc-tests.

Green badge in the README pointing at the real repo.

0.9 S Test the docs/building-from-source.md guide in a clean rust:1.98 container, following only the text.

Container log with a successful build attached to the repo.

0.11 S Clean up the project folder: delete _retirar/ (third-party products) once the owner confirms, and write a README explaining forks/, floem-main (Floem 0.2 for the future UI), floem-shadcn/tailwind and Website/.

du -sh projects/GraphoOS < 100 MB and a README at the root.

0.13 S GitHub Actions on the Empoorio account: every run ends in startup_failure after 0 s in the private repos (empooScan too since Sep 16). Review the account's billing and Actions settings; until then GraphoOS CI cannot run.

gh run list shows a CI run that actually executes jobs.

1.1 S Legal review of the inherited code's license (Apache-2.0) by Empoorio's counsel: which notices must ship in the packages (dmg, msi, deb, rpm) before the first public release.

Written opinion, and license files included in every installer.

1.6 M Own macOS signing: Empoorio Developer ID certificate, replace CODESIGN_IDENTITY in the Makefile, notarization with our own secrets in release.yml.

spctl --assess accepts the .app; Gatekeeper shows no warning.

1.7 S Domains: register graphoos.dev, docs., plugins., or move everything under graphoos.empoorio.org; update the 6 places in the code that use them.

All three hosts resolve and serve TLS.

1.9 S Check for a trademark conflict: "GraphOS" is an Apollo GraphQL product. Settle on the single spelling "GraphoOS" everywhere.

Trademark search in EUIPO/USPTO documented.

1.11 S Make the 13 GraphoOS repos public (private today) when the owner decides, and then remove git-fetch-with-cli and the token from CI.

Anonymous git clone + cargo build work.

2.7 M Assets for Linux and Windows (grammars, proxy, installers) from the release workflows once Actions works; today only macOS arm64 is built, on this Mac.

Releases with assets for all 3 platforms.

2.2 L Plugin registry. v0 done on Sep 21: a static registry generated by Website/registry/build.py from registry/plugins.toml and served at graphoos.web.app/api/v1 (list, latest, icon, readme, download → tarball in /dl); base URL configurable in graphoos_core::registry. Still missing: the plugins.graphoos.dev domain, real search, statistics, a publishing CLI and package signing.

Install a plugin from the panel and have it start its LSP (download and install verified by a live test).

2.3 M Remote proxy: publish graphoos-proxy per architecture (static linux x86_64/aarch64 with Alpine, macOS, Windows) in every release and fix proxy/remote.rs:350.

Connect over SSH to the Ailoos VPS and edit a remote file.

2.4 M Updater: point update.rs at Empoorio/graphoos and test the full cycle (detect, download, replace, restart) on macOS and Windows.

Update from one nightly to the next with no intervention.

3.1 L Complete release.yml: signed and notarized universal macOS build, MSI signed with signtool (it does not sign today), .deb/.rpm/AppImage, tarballs. Today: a manual nightly pre-release with a macOS arm64 DMG (ad hoc signature) + proxy.

Release v0.5.0-beta.1 with 10+ downloadable artifacts.

3.2 S Automatic nightly (the cron already exists) published as a pre-release and linked from download.html. Partial, Sep 22: the nightly pre-release exists and download.html links to it with the date; automatic publishing waits for Actions to work (0.13).

Yesterday's build available for download every morning.

3.3 M Package managers: Homebrew cask, winget, Scoop, Flathub (dev.graphoos → org.empoorio), AUR, copr.

brew install --cask graphoos and winget install Empoorio.GraphoOS work.

3.4 S Platform installers signed and published from the release channel.

Stable per-platform download on the downloads page.

3.5 M Clean-machine install per OS (macOS VM, Ubuntu, Windows 11) following only the website; open a real project and debug.

3-OS checklist with screenshots for each release.

3.6 S Windows portable build (graphoos-app/portable feature) published as a zip.

Runs from a USB stick without writing to %APPDATA%.

3.7 M Reproducible builds: tarball with cargo vendor (already supported) and a documented offline build.

Two builds of the same tag produce the same result.

4.1 L Unit suite for the buffer, selection, syntax, keymaps, palette and RPC (target > 300 tests), plus app↔proxy integration tests.

cargo test --workspace in CI, coverage published.

4.2 M UI tests with floem-test for the palette, tabs, splits and settings.

20+ automated UI scenarios.

4.3 M Audit the 347 .unwrap() calls on UI/proxy paths and the 14 unsafe blocks; turn them into recoverable errors.

Clippy with unwrap_used as a warning; every unsafe with a SAFETY comment.

4.5 M Large files: open 100 MB / 1 M lines / a 20 MB single-line JSON without blocking the UI; turn off syntax above a threshold.

Keystroke latency < 16 ms measured on those files.

4.6 M Large sessions: 200 tabs, 10 splits, 3 terminals, a 50 k-file project; measure memory and leaks over 8 h.

RSS table per scenario in docs/benchmarks.

4.8 L Benchmarks published and compared on the same machine against VS Code, Zed and Cursor: cold/warm start, idle RAM, indexing, global search, keystroke latency, scroll fps, battery over 1 h.

docs/benchmarks.md with a reproducible method and script.

4.12 M LSP/DAP client robustness against faulty or hostile servers: message size limits, per-request timeouts, fuzzing of the client's JSON-RPC parser; a crashed server is restarted with a notice and does not take the editor down.

A server that sends garbage or hangs neither blocks nor closes GraphoOS.

5.1 S Multi-cursor: Alt+click, select next/all occurrences, skip occurrence, cursors above/below/at line end and selection undo already exist (keymaps-macos/nonmacos). Missing: column selection by dragging and a test suite that pins down the behavior.

Suite of 30 multi-cursor cases green.

5.2 M User snippets: one file per language (TOML), nested placeholders, transformations, variables ($TM_FILENAME…), a management UI.

A custom Rust snippet works, tabbing across 3 placeholders.

5.3 M Rename with multi-file preview and global undo; refactors: extract, inline, organize imports, apply all fixes.

Rename a symbol used in 20 files and revert it in one go.

5.6 L Minimap (0 refs), real breadcrumbs (6 refs), indent guides, rulers, word wrap, configurable bracket colors.

Each one toggleable in settings, with a screenshot.

5.7 M Web support: Emmet (0 refs), HTML/CSS/JSX with tag closing, inline colors, preview.

ul>li*3 expands in a .html file.

5.8 L Full debugger on top of DAP: conditional breakpoints and logpoints, watch, stack, editable variables, console, launch configs per language; tested with codelldb (Rust), debugpy (Python) and Node. Progress Sep 22: until today NO plugin registered an adapter (debugging was impossible) and two inherited bugs blocked it anyway: the breakpoint layer sat below the line-number layer (no click got through; fixed with pointer-events) and ${workspace} reached the adapter unexpanded. Now the SDK exposes register_debugger_type, the Rust and C/C++ plugins register lldb → codelldb or lldb-dap (absolute path), and a session reaches initialize → launch → runInTerminal with a pid; on this Mac it stops at the system's "Developer Tools Access" authorization (the owner has to grant it once). Missing: python (debugpy), Node, conditionals, watch, variable editing.

Debug EmpooScan (Rust) and a Python script with conditional breakpoints.

5.9 L Full visual Git. Done Sep 21: inline blame for the cursor line (author, age, summary, commit; "Not committed yet"; hidden while there are unsaved changes; refreshed on save and when the repo changes; editor.enable-git-blame), tested in the app. Missing: file history, commit log with graph, branches/stash in a panel, pull/push with credentials, PRs.

Full branch → commit → push → PR flow without leaving the editor.

5.10 M 3-way merge conflict editor (0 refs today).

Resolve a real conflict from this ecosystem by accepting both sides.

5.11 M Local history / on-disk timeline per file, with diff and restore.

Recover a 2-hour-old version of an unversioned file.

5.12 M Terminal: profiles with a UI, splits, clickable links, search, shell integration (command markers, cwd), reuse for tasks.

Ctrl+click on an error path opens the file at that line.

5.13 M Tasks: detect cargo/npm/make/gradle, problem matchers feeding the problems panel, shortcuts for build/test/run.

A cargo build error shows up in Problems with a link.

5.14 M Diff: side by side and inline with hunk navigation, folder diff, diff against any commit.

Navigable diff of two EmpoorioChain branches.

5.15 M Explorer: multi-root workspace, drag and drop, git and problem decorations, compare selected, open with.

Open 3 projects from the ecosystem in one window.

5.16 M Settings: search, TOML editing synced with the UI, workspace settings (.graphoos/settings.toml), import from VS Code.

Change the theme from the settings search in < 3 keystrokes.

5.17 L Modal: Vim coverage (text objects, macros, registers, marks) and optional Helix/Emacs modes.

Partial vim-test suite (200 cases) green.

5.18 S Side Markdown preview (markdown.rs already renders hovers) and image/SVG preview. Done Sep 22: a "Markdown Preview" panel (⌘⇧V) using our own engine (headings, emphasis, highlighted code, bulleted/numbered lists — added to the engine — separators, quotes, local images), live updating verified in the app. Missing: opening image/SVG files in a tab.

Live preview of a README with images.

5.19 S Readable notifications and error messages: audit every anyhow! that reaches the user.

No error shows a Rust Debug dump to the user.

5.20 L Dev Containers: read devcontainer.json, build the image with Docker/Podman and run graphoos-proxy, LSP, DAP and the terminal inside the container while the UI stays native (the UI/proxy architecture is already designed for this).

Open a repo with devcontainer.json and build/debug inside the container without installing anything on the host.

5.21 L Tunnels: connect the editor to a remote proxy behind NAT through an Empoorio relay, in addition to SSH/WSL.

Edit on a VPS without opening ports or configuring SSH.

5.23 M Debugger: logpoints, hit-count breakpoints, a REPL evaluation console and variable editing (the DAP types already declare supports_conditional_breakpoints).

A logpoint prints without stopping and the console evaluates an expression in the current frame.

6.2 M API versioning with compatibility declared in plugin.toml, and conformance tests.

A v1 plugin still loads in v1.3 of the editor.

6.3 L Own registry with a website: catalog, search, icons, README, statistics, a graphoos plugin publish CLI, package signing, moderation.

Publish and update a plugin from the CLI in < 2 min.

6.4 L Language plugins maintained by Empoorio (top 10) with their own CI and automatic download of LSP servers.

Install Python and get pyright with no manual steps.

6.5 M Importer for VS Code color and icon themes (JSON) and a theme catalog.

Install "One Dark Pro" from its original JSON.

6.6 XL Explicit decision: a compatibility layer for VS Code extensions (Node host + API). It is XL and defines the product: Cursor/Antigravity/Windsurf have it because they are VS Code forks; Zed does not.

Yes/no decision document with scope; if yes, a prototype that loads one theme extension and one language extension.

6.7 L Extensions with UI: native declarative views (panels, trees, scoped webviews).

A plugin shows its own side panel.

6.8 M Tree-sitter grammars and queries installable as extensions without recompiling the editor.

Add a new language without touching graphoos-core.

6.9 M Per-plugin permissions (capability model): each plugin declares in volt.toml what it needs (directories, network, processes) and the user approves it on install; WASI already sandboxes by default, but today the proxy opens the plugin directory and full HTTP network access.

A plugin without network permission cannot download anything; the panel shows the granted permissions.

6.10 M Plugin watchdog: a hung or looping plugin does not block the editor (per-call timeout, plugin restart, user notice, without losing the other plugins' LSP).

A plugin with loop {} is detected and restarted, and the editor keeps responding.

7.26 M Chat: @symbol (definition via LSP), images in the message, mention autocompletion when typing @, and a real model dropdown.

Typing @ shows files and symbols; a pasted screenshot reaches the model.

7.6 L Multi-file editing with a reviewable diff: accept/reject per hunk, apply in bulk, full undo.

A change across 8 files is reviewed and applied hunk by hunk.

7.7 XL Agents: integrate the andromeda agent from the Ailoos CLI (file/shell/git/search tools, Landlock/Seatbelt sandbox, subagents, confirmations) into the editor via an ACP-style protocol. Done Sep 22 (foundation): andromeda --acp (JSON over stdin/stdout: hello/token/actions/confirm/tool_result/done) launched by the proxy in the workspace, Agent mode in the panel with a streaming response, a card per action with a diff and Apply / Apply and continue / Reject, the decision sent back to the agent, Stop that kills the process and closes the cards, history with the decision; verified with real andromeda and with a test ACP agent (create a file: applying creates it, rejecting does not). Missing: per-hunk diffs, per-tool permissions (read/write/execute/network), an auditable log, the Landlock/Seatbelt sandbox, subagents; and the 1B model does not follow the tool syntax (a model-quality issue).

The agent refactors a module, runs the tests and asks for permission before every command, all from the panel.

7.8 L MCP client: stdio and HTTP servers, per-user and per-workspace configuration, per-tool permissions, resource listing.

Connect a GitHub MCP server and use it from the chat.

7.9 L Semantic workspace index (local embeddings) for automatic context; incremental with notify.

A question about "where the extrinsic is signed" returns the right file without @.

7.12 L External agents (Claude Code, Codex CLI) over the same ACP protocol as andromeda, with streaming diffs into the editor.

Claude Code opens and edits in GraphoOS with reviewable diffs.

7.13 L Harness — validation gates: after each agent edit, the project's formatter, linter and tests run; if they fail, the error goes back to the agent in a repair loop with an iteration limit and a stop.

A change that breaks a test fixes itself in ≤3 rounds or stops with a report.

7.14 M Skills: reusable procedures in Markdown (e.g. "pallet tests", "schema migration") that the agent loads depending on the task, in addition to AGENTS.md and the project rules.

Invoking a skill changes the agent's behavior in a verifiable way.

7.15 L Parallel subagents with user-chosen isolation: inherit the workspace, their own branch in a git worktree, or shared; each with a clean context and a summarized result for the parent.

Three subagents touch three modules in worktrees and the parent integrates them.

7.16 M Evidence artifacts: the agent delivers a Markdown plan, a checklist with progress and proof (test output, screenshots) before the user merges anything.

Every agent task ends with its evidence artifact in the panel.

7.17 L Browser agent with Aephoron (Kinetoor engine, native to the ecosystem): end-to-end tests of the UI under development, with screenshots and recordings attached as evidence.

The agent opens the local app in Aephoron, clicks, and attaches the screenshot.

7.18 M Spec-driven flow: the agent reads and critiques the spec (invariants, acceptance criteria) before touching code; a spec template in the repo.

Given an incomplete spec, the agent asks instead of improvising.

7.19 M GraphoOS as an MCP server: expose the workspace, symbols, diagnostics, diffs and terminal to external agents with per-resource permissions.

An external agent lists the symbols of the open file via MCP.

7.20 M Defenses against prompt injection and tool poisoning: third-party content (issues, web pages, MCP output) marked as data, a list of destructive commands requiring confirmation, no secrets in the context, an auditable log of every action.

An issue with hidden instructions cannot get the agent to execute anything.

7.21 L Delegated cloud tasks: run the agent in a remote sandbox (graphoos-proxy in a container on an Empoorio VPS) and return a reviewable PR, without touching the local machine.

Delegate a task, close the laptop and find the PR.

7.22 M Structural tools for the agent: list_symbols, find_definition, references and diagnostics via LSP/tree-sitter instead of grep, with exact coordinates.

The agent locates a function by its symbol, not by text.

7.23 L Scheduled tasks and background agents with a management panel (status, cost, results).

An overnight task leaves its evidence artifact by morning.

7.24 M Reviewer agent: an independent second pass that audits the diff (bugs, security, style) before proposing it to the user.

Every diff arrives with the reviewer's report.

7.25 M A graphoos CLI for terminal and SSH reusing andromeda, and an SDK to embed the agent in other Empoorio apps.

graphoos agent "…" works on the VPS over SSH.

8.1 XL AccessKit in Floem (2 refs today): an accessibility tree for the explorer, editor, palette and settings; tested with VoiceOver, NVDA and Orca.

Walk through the palette and editor with VoiceOver announcing the content.

8.2 M Full keyboard navigation, visible focus, WCAG AA contrast in the default themes.

Audit against a WCAG 2.1 AA checklist with no critical failures.

8.3 S HiDPI scaling and fonts: measure on Windows 125/150 %, macOS Retina, fractional Linux (0.4.5/0.4.6 already fixed bugs here).

No misalignment across 6 documented combinations.

8.4 L Localization: an i18n system (8 refs to locale today), complete ES and EN, language contributions per file.

Changing the language in settings translates the whole UI without restarting.

8.6 M Onboarding: welcome screen, import VS Code settings and keymaps, choose modal or not, choose an AI provider.

A new user is productive in < 5 min without reading the docs.

9.1 M Beta program with a feedback form inside the editor and a dedicated channel.

100 active users with recorded feedback.

9.2 S Weekly issue triage (templates already exist) and public priority labels.

Time to first response < 72 h for 8 weeks.

9.4 M Opt-in adoption metrics (installs, OS, version) with no personal data.

Internal dashboard with weekly figures.

9.5 M Update policy for the forked dependencies (Floem, xi-rope, vger, winit, lsp-types): a schedule for bringing in improvements from their origin projects without reintroducing third-party names (renaming script already tested).

Decision document and first update cycle.

9.6 M Integrations with the Empoorio ecosystem only where they add value: Ennooia (notes), Ailoos (models), EmpoorioChain (plugin signatures with DID).

Each integration with a written use case before coding.