Documentation
Install
Download a packaged build for macOS, Windows, or Linux — or build Frontier Proxy from source.
Download a build
Packaged builds require no toolchain. The current release is v0.6.2.
| Platform | Format | File | |
|---|---|---|---|
| macOS | Zip archive | Frontier.Proxy-0.6.2-mac.zip |
Download · 110.5 MB |
| Disk image | Frontier.Proxy-0.6.2.dmg |
Download · 110.9 MB | |
| Windows | Portable | Frontier.Proxy.0.6.2.exe |
Download · 88.5 MB |
| Installer | Frontier.Proxy.Setup.0.6.2.exe |
Download · 88.7 MB | |
| Linux | Debian / Ubuntu | frontier-proxy_0.6.2_amd64.deb |
Download · 87.1 MB |
| AppImage | Frontier.Proxy-0.6.2.AppImage |
Download · 111.7 MB |
Links point at the assets attached to v0.6.2. Every version stays available on the releases page.
You still need an agent
Frontier does not install or bundle any coding agent. At least one supported CLI must be installed and signed in on the same machine — see provider setup.
Build from source
Prerequisites: Node.js 22 or newer, pnpm, and at least one supported CLI.
git clone https://github.com/ThisaST/Frontier-Proxy.git
cd Frontier-Proxy
pnpm install
pnpm dev
Before packaging, run the checks the repository ships with:
pnpm typecheck # tsc for the node and web projects
pnpm test # vitest
pnpm package # electron-builder --dir (unpacked)
pnpm dist produces full installers for the operating system you run it on — DMG and ZIP on macOS,
NSIS and portable on Windows, AppImage and DEB on Linux. Native installers should be built on their target OS or
in a CI matrix.
Windows notes
On Windows, pnpm dist can fail through its pnpm build && … prefix when pnpm
re-runs install. Building the two steps directly works:
npm run build
./node_modules/.bin/electron-builder
If packaging fails with EPERM: … rename 'release\win-unpacked', close any running Frontier Proxy
instance, delete release/win-unpacked*, and re-run.
Development builds from CI
GitHub Actions builds Windows, macOS, and Linux installers after every push to main, when a
v* tag is pushed, and on manual dispatch. Open the repository's
Actions tab, pick a successful Build desktop apps
run, and download the artifact for your platform. Artifacts are retained for 30 days; tagged versions are published
permanently to the releases page.
Where state lives
Frontier writes a single frontier-state.json file in Electron's per-user application-data directory —
tasks, providers, settings, and usage. Removing that file resets the app. Nothing is written to your projects except
the changes an agent makes in the working directory you selected.