Pre-launch. Planned as real-time chat with Cruxy Code in your browser: every conversation saved, no CLI required.
Interface preview. Cruxy Bench is pre-launch: features shown are planned, not yet available.
What Bench is planned to do
Planned: search every conversation you've had
Interface preview. Cruxy Bench is pre-launch: features shown are planned, not yet available.
Planned: multi-step plans with approval at every step
Interface preview. Cruxy Bench is pre-launch: features shown are planned, not yet available.
By design, your API key never leaves the server
Browser
session token only
Bench Server
API key lives here
Cruxy Code
model inference
API keys live on the server. The browser only carries a session token. Even with DevTools open, your credentials aren't there.
Interface preview. Cruxy Bench is pre-launch: features shown are planned, not yet available.
Features
Direct chat with Cruxy Code
Planned to share the Cruxy Code engine, browser-native, with no install and no plugin.
Accept/Decline every action
Designed so you see plans before files are touched, and every change is reversible.
Every conversation saved
Planned: searchable history across sessions, so you can resume any thread.
No API key in the browser
Designed around a server-to-server connection that keeps credentials off the client.
Planned for any device
Designed to need no install, no binary and no IDE plugin.
Reads your repo
Planned integrations: GitHub and GitLab, so one link gives Bench full context on every request.
Who it's for
Mobile-first developers
Planned: make code changes from your phone, with full proposal review and approval designed for a 5-inch screen.
Pair programming with non-technical teammates
Planned: share a Bench thread so your PM can watch what changes and learn the codebase without checking out the repo.
Quick edits on someone else's machine
Customer-facing emergency? Bench is planned to let you open a browser, make the fix with full review, and ship. No laptop needed.
FAQ
Cruxy Code is a CLI for your local machine, in early access. Bench is pre-launch: it is planned to share the same engine in a browser, with chat history and a team-friendly review UI.
As designed, Bench will read your repo from GitHub or GitLab (planned integrations) on demand. Nothing will be stored permanently except your conversation history; code context will be fetched per request.
Bench is designed to redact known secret patterns (API keys, tokens, .env values) before sending context to the model, with configurable paths to skip entirely.
By design, every action will land as a regular Git commit on a feature branch, so reverting is git revert. Bench will never force-push.
That is the plan. Bench is designed mobile-first, with proposal cards, diffs, and approval designed for phone screens.
Bench is rolling out on every plan, Free included, as shown in the pricing table. Join the waitlist for early access.
Planned: a GitHub link, real-time chat, and approval on every change.