Desktop App

Forgexa Desktop is a native desktop workbench built with Tauri 2 and React. It gives you an IDE-style environment to review and drive Forgexa's workflow/gate/QA-governed AI agents directly against your own local working directory — no browser required.

The app is fully self-contained: it bundles the runtime daemon and manages it automatically, so no separate CLI installation is needed.

Download & Install

Log in to the Forgexa web app and open the Download page in the sidebar. It detects your platform and serves the latest build from the Forgexa Desktop release channel.

Platform	Format	Notes
macOS	.dmg	Universal binary (Intel + Apple Silicon)
Linux (Debian/Ubuntu)	.deb	Ubuntu 22.04+, Deepin 25
Linux (other)	.AppImage	x86_64
Windows	.exe (NSIS), .msi (WiX)	Windows 10+

macOS

1. Open the downloaded .dmg file.
2. Drag Forgexa.app to the Applications folder.
3. If macOS blocks the unsigned app, remove the quarantine attribute:

sudo xattr -cr /Applications/Forgexa.app

Linux

# .deb (Debian / Ubuntu / Deepin)
sudo dpkg -i ~/Downloads/forgexa_*.deb

# .AppImage
chmod +x ~/Downloads/forgexa_*.AppImage
./forgexa_*.AppImage

Windows

1. Double-click the .exe (or .msi) installer.
2. If Windows SmartScreen shows a warning, click More info → Run anyway.
3. Follow the installation wizard.

Sign In

On first launch the app asks for your Forgexa account. Release builds connect to the production API by default; to point the app at a different server (e.g. a local backend), either:

• Set server_url in the shared ~/.forgexa/config file (the same file the CLI's forgexa login uses), or
• Launch the raw binary with the environment variable set, e.g. FORGEXA_SERVER_URL=http://localhost:8000 "./Forgexa.app/Contents/MacOS/forgexa-desktop".

Interface Overview

The workbench follows a VS Code-style layout:

• Activity Bar — switch between Explorer, Search, Source Control, Requirements, and Agent views; account and settings live at the bottom.
• Sidebar — file tree for the bound local folder, search across files, or the requirements/agent panels depending on the active view.
• Editor Area — tabbed code editor with syntax highlighting, diff view, and Markdown preview; Settings opens here as a tab.
• Bottom Panel — integrated terminal, workflow node output stream, and Problems (from the built-in TypeScript/JavaScript language server).
• Status Bar — bound workspace, linked project, daemon connectivity, and running agent state.
• Quick Open — jump to any file by name from the keyboard.

The app runs in two modes, switched from the Activity Bar:

• Requirements mode — pick a requirement from the list and work through its AI-driven workflow.
• Agent mode — free-form agent chat and code editing against the bound folder.

Workspaces

Forgexa Desktop works against a local folder on your machine:

1. Click Open Folder (status bar or Explorer) to bind a local directory as the workspace.
2. Optionally Link to Project from the status bar to associate the folder with a Forgexa platform project — this connects requirements, executions, and gates to your local files.
3. Recent workspaces are remembered; use Switch Workspace in the status bar to move between them.

Agent Chat

The Agent view provides a chat composer that drives AI agents inside your workspace:

• Send instructions in natural language; the agent reads and edits files in the bound folder.
• Tool calls (file edits, commands) appear inline in the transcript, with a consent prompt before sensitive actions.
• A running agent is indicated in the status bar; click it to jump back to the conversation.

DeepSeek Harness appears in the existing agent picker when its exact 0.2.0-rc.2 build/Node/platform acceptance passes. Its committed JSONL text is not live token streaming; the final is emitted once, and cancellation is supervised by AgentHost. Native resume is bound to the same workspace/build/runtime composition. Images, native fork, read-only review and parallel capabilities are not advertised. Authentication is a read-only external reference and runtime state lives in a managed home; native Windows is not enabled. See Harness setup.

Requirements & Workflow

The Requirements view mirrors the platform's requirement workflow locally:

• Browse requirements of the linked project and open one to see its detail, description, and change files.
• Step through the AI-driven phases with the phase wizard; watch each workflow node's live output in the bottom panel.
• Review gates when they pend, inspect gate scores, and follow the delivery steps through verification.
• The requirement's Files panel shows just that requirement's changes, while the Explorer always shows the whole project.

Editor, Terminal & Git

• Editor — open files from the Explorer; changes are saved to disk directly. External modifications (e.g. by an agent) are detected and you choose to reload or overwrite. Markdown files offer a rendered preview.
• Terminal — a real shell rooted at the workspace folder, in the bottom panel.
• Source Control — review working-tree changes with colored diffs and commit from the Git panel.
• Problems — diagnostics from the built-in language server for open TypeScript/JavaScript files.

Settings & Updates

Open Settings from the Activity Bar (or the native app menu). Available options include:

• Theme (light / dark / system) and interface language
• Server URL resolution and daemon status / auto-start
• Local output log inspection and cleanup
• Update check — the app checks the /releases/desktop/latest channel automatically and can re-check on demand

Building from Source

The app is built from the desktop/ directory at the repository root. See desktop/README.md for the full build guide. In short:

cd desktop
npm install
npm run tauri dev      # development (Vite dev server + Tauri window)

# Production builds
./desktop/scripts/build-macos.sh    # macOS .dmg
./desktop/scripts/build-linux.sh    # Linux .deb + .AppImage
.\desktop\scripts\build-windows.ps1 # Windows .exe + .msi