Desktop AI command deck

Acrylic

The desktop AI IDE built to outgrow Cursor and Windsurf.

Real terminal, visible review, visual editing, and BYOK that stays on your machine.

$ curl acrylic.build/install | sh
Local-firstReal PTYDiff reviewBuilder
// High fidelity proof

The command deck interface

acrylic-core / src / engine.rs
1use acrylic_types::Context;
2
3pub fn process_delta(ctx: &Context) {
4 // Initialize local-first PTY stream
5+ let stream = PTYStream::new(ctx.id);
6+ stream.listen(|event| {
7 // Process events locally
8 });
9}
Real PTY - zsh
80x24
-> ~/projects/acrylic git:(main) cargo build
Compiling acrylic_core v0.9.4...
Finished dev [unoptimized + debuginfo] target(s) in 0.42s
Acrylic node initialized successfully.
$ listening for IPC signals...

Built for engineering sovereignty

Tools that respect your context and your data.

01 / Architecture

Local-first

Your repository and keys stay on your machine. Acrylic treats cloud identity as access control, not as the place where active work has to live.

02 / Interface

Real PTY

Native terminal integration. Your aliases, shell config, long-running jobs, and handoffs behave like a real workstation instead of a toy console.

03 / Workflow

Diff-first review

Every AI change becomes visible before it lands. Suggestions show up in a dedicated lane so you keep accountability.

04 / Economy

BYOK

Bring your own key. Connect your provider directly and avoid paying an extra inference tax just to use the editor.

05 / Visual

The Builder

Structural editing for UI work. Touch layout and components visually without throwing away code integrity.

06 / Roadmap

Fleet Sync

Shared local context and collaborative runtime surfaces are on the roadmap once the desktop core is hardened.

Cursor is fast.
Acrylic is grounded.

"Windsurf feels smooth. Acrylic feels owned."

Cloud-first IDEs are racing to upload your development environment for convenience. We care more about preserving ownership, visible state, and local execution when the work gets serious.

Manifesto 01

Acrylic is not an AI extension stapled onto an existing editor. It is a desktop control room designed for the high-context era of software development.

We believe in radical reviewability, local execution, and the right to own every byte of your development environment.

Desktop-nativeOwned runtimeVisible diffs

Data boundary protocol

Total transparency on data flow.

Local hardware bound

  • Project source codeNever uploaded
  • API credentials (BYOK)Local only
  • Semantic vector mapLocal index
  • PTY shell sessionDesktop runtime

Cloud synchronized

  • Account identityAuth
  • Theme and profile stateSyncable
  • Subscription statusBilling-ready
  • Beta entitlementsCloud state

Frequently asked questions

Straight answers about how Acrylic works, what stays local, and why the desktop model matters.

You provide your own API keys for providers like Anthropic or OpenAI. Acrylic uses them from your machine instead of proxying active work through our servers.

It is a native pseudo-terminal session, not a fake web console. Shell config, long-running commands, and handoff stay grounded in the same runtime.

Identity, download access, recovery, and future billing readiness. Your local repo, files, and provider secrets do not need to leave your machine.

They proved the market. Acrylic goes after the next layer: more ownership, more visible state, and a stronger desktop-native system when the work stops being a demo.

Acrylic final protocol

Secure your access

Don't just use an AI IDE. Own your development environment.