Skip to main content
Private access is opening up — request an invite
askFinz
Desktop · 2026

ASK
FINZ
/ DESKTOP

For Windows · macOS · Linux

Browser · askFinz Drive · then the coder

Its own browser. Its own drive.

The first release is two things. A real web browser the agents drive — it navigates, signs in where you already have access, and reads the pages a crawler is refused. And askFinz Drive, which keeps a folder on your disk and your workspace as one file store, so what you edit is what an agent reads. The coder — editor, debugger, terminals — follows on the same subscription.

Desktop · offline

Running on your machine, with or without a connection.

Offline · using local model
Local model · downloaded · 4.7GB
Verified · sha256
Summarise this contract folder in three bullets.
Local · fast
Three contracts, two NDAs and one MSA. All three expire on or before Aug 2026. The MSA has an unusual unilateral termination clause at §9 — worth flagging before renewal.
Ask the local model anything · runs on this machine
In order

The first release, then the coder.

The browser and the drive come first, because they are what the desktop is for: a machine of your own that an agent can actually work on, and a folder it can actually read. The development environment — editor, debugger, source control and terminals — is built and follows them, on the same subscription. Each card below says which half it is in.

First release

Its own web browser.

Not a window onto the web app: a real browser the agents drive. It navigates, signs in where you already have access, works through a task across sites, and reads pages a crawler is refused — the same route the extension takes, on your own machine.

First release

askFinz Drive.

Cloud storage of the familiar kind, built for work a machine also does. A folder on your disk stays in step with your workspace, so the file you edit and the file an agent reads are one file — written twice, in two countries.

First release

Works offline when you do.

Pin a set of local AI minds and the desktop client will use them when the network drops. Useful on a flight, on a sensitive client site, or when you simply prefer the work stays on your machine.

First release

Reads big folders fast.

Point it at a corpus on disk — a paper archive, a code repository, a folder of contracts — and it works through them at native speed. The output feeds Search and Research.

Follows

A full editor.

A Monaco-based editor with multi-file editing, a language-server (LSP) backbone for completions and diagnostics, and AI inline autocomplete served by a local model. The editing surface is the same engine that powers professional code tools.

Follows

Step through your code.

A server-side debugger (DAP) with live, verified breakpoints across Python, JavaScript / TypeScript and Go. Built and tested; it arrives with the coder rather than with the browser and the drive.

Follows

Git, where you work.

Source control inline — diffs, blame, branch switching and staging — so you can review and commit without leaving the editor.

Follows

A multi-terminal.

Run as many shells as the job needs, side by side, in the same window as the editor and the debugger. Builds, tests and scripts stay next to the code they touch.

Debugger

Breakpoints that actually stop.

The desktop debugger runs server-side over the Debug Adapter Protocol, with breakpoints we've verified hit live. Set them, step through frames, inspect variables — across more languages than the web IDE. It arrives with the coder, after the browser and the drive.

Python
Built · verified breakpoints
JavaScript / TypeScript
Built · verified breakpoints
Go
Built · verified breakpoints
Rust
Later

Cross-language debugging is built and verified for Python, JavaScript / TypeScript and Go, and ships with the coder release. Rust is on the roadmap after it.

Honest scope

What it isn't.

The first release is the browser and the drive, with local models and the folder reader. The development environment is built and follows them — we would rather say that than let a download page imply you get all of it on day one. It is not a screen-sharing host, a remote-desktop server, or a video-conferencing tool. We hear those requests and we've catalogued them — but they don't ship and we won't pretend they do.

If you need to give an askFinz agent control of your screen, that's the job of the Navigator agent inside the web product — read how Navigator pauses, on purpose.

Desktop vs. cloud

Two front doors. Different jobs.

Desktop is the surface that runs on hardware you own: a browser an agent can drive without asking anyone's permission, your files on your own disk, and local models for offline, low-latency work. The cloud version on *.askfinz.ai has the full agent fleet, larger context windows and the most capable frontier models, and it is where the twenty-nine workspaces live today. Reach for Desktop when the work should stay on your machine; reach for Cloud when you want the frontier models and the whole fleet.

Platforms

private access
OSDistributableNote
WindowsaskFinz-Setup-x64.exeWindows 10 / 11 (x64). Code-signing pending; private-access installer is unsigned during this window.
macOSaskFinz.dmgmacOS 12 Monterey or newer (Apple Silicon and Intel). Notarisation pending; private-access build is unsigned.
LinuxaskFinz.AppImageMost x64 distros. Run `chmod +x` after download. No package-manager listing yet.

Code-signing is being finalised. Until then, private-access installers may trigger the operating system's “unverified developer” warning the first time they open. We email a checksum with every drop so you can verify what we sent.

How to get it

Email hello@askfinz.com with your platform; we send a signed checksum and a download link valid for 72 hours.

Join the waitlist