Solari Reflex

It is a speed layer for computer use on Solari, for browsers and Linux desktops. Give it a goal and a Solari machine, and each step is one structured observation, one decision from Jev, and one verified action, with no screenshots in the loop.

JevClient makes the decision for each step; the README's log shows lines like jev 0.78 TYPE e2 and jev 0.98 CLICK e3 with the resulting state change. The Policy wrapper denies named actions, for example deny: ["Delete", "Pay now"], before they run.

Run npm install --allow-git=all github:hitakshiA/solari-reflex. npm 12 fetches git dependencies only when allowed, while older npm, pnpm and bun do not need the flag, and the package builds itself from source when fetched. It was tested on npm 12.0.2, where npm may warn that a prepare script was blocked.

Against Codex CLI (GPT-6 Astra) driving the same Solari machines through Solari's MCP server: Stripe Checkout 60.2 s and $0.011 versus 194.9 s and 34 tool calls; six checkouts 66 s and $0.064 versus 460 s and 86 tool calls; 30 LibreOffice Calc expenses 24.2 s and $0.0008 versus 98.4 s and 77 tool calls.

Yes. DesktopSurface implements the same Surface as BrowserPage, so runTask drives desktop apps unchanged, and you can call observe and act yourself. attach installs reflexd, a Python daemon that reads the active window's Linux AT-SPI accessibility tree and acts through it.

The examples use a Solari API key (SOLARI_API_KEY) to create browsers or desktops, and an OpenRouter key for the writer, advisor and planner models, such as inception/mercury-2.5 and google/gemini-3.5-flash with minimal reasoning.

The comparison comes from the author's own runs against Codex CLI driving the same Solari machines through Solari's MCP server, with each run checked by the app it worked in, and details live in a separate solari-fast-showcase repository. The README in the digest cuts off mid-sentence in the desktop section.