Native desktop app (Tauri wrapper)

[Dhwanil25]

Overview

Package Agentis as a native desktop application using Tauri — giving users a proper app experience with system tray, file system access, and no browser CORS restrictions.

Benefits over browser

Feature	Browser	Desktop (Tauri)
File system access	❌ (needs engine proxy)	✅ Native
System tray	❌	✅
CORS restrictions	Needs Vite proxy	✅ None
Offline use	Partial	✅ Full
Auto-updates	Manual	✅ Built-in
OS notifications	Limited	✅ Native

Implementation notes

• Tauri wraps the existing Vite/React frontend with zero code changes to the UI
• Vite proxy routes can be replaced with Tauri's http plugin (direct fetch, no CORS)
• The Agentis engine (vite-plugin-agentis.ts) becomes a Tauri sidecar binary
• Build targets: macOS (arm64 + x64), Windows (x64), Linux (x64)

Discussion

Is there enough demand for a desktop app? Would you use it? Comment below — if there's interest we'll prioritise it.

Related

• Mentioned in README roadmap

[CodeByStella]

Hello @Dhwanil25,
I wanna get assigned this roadmap.

[Dhwanil25]

@CodeByStella Hello, I have assigned you here. If you have any questions, you can ask me

[Dhwanil25]

@CodeByStella, these are a few things to consider. It will be useful for you.

1. Dual entry points — Tauri should target app.html, not index.html

The repo has two separate HTML entries:

• index.html → the landing page (pure HTML, no React)
• app.html → the actual React app (src/main.tsx)

The Tauri tauri.conf.json frontendDist + devUrl should point to app.html;

2. The Vite proxy routes are the main work — 15+ of them

vite.config.ts has proxy routes for Anthropic, OpenAI, Google, Groq, Mistral, DeepSeek, OpenRouter, Cohere, xAI, Together, Tavily, GitHub, and skills.sh. In Tauri, we replace these with Tauri's @tauri-apps/plugin-http so the WebView makes direct HTTPS calls (no proxy needed). The proxy paths like /anthropic, /openai-proxy, etc., are used throughout src/lib/multiAgentEngine.ts — we'll either need to keep them (by running Vite's dev server as the frontend) or update the fetch URLs when building for production.

3. The Agentis engine (openfang binary) becomes a Tauri sidecar

vite-plugin-agentis.ts currently spawns the bin/openfang binary as a child process inside the Vite dev server. In Tauri, this moves to a https://tauri.app/develop/sidecar/. The middleware endpoints it registers (/agentis/status, /agentis/configure, /agentis/logs, /agentis/migrate) currently run on the Vite dev server — in Tauri, these need to move to Tauri commands or a lightweight local HTTP server the sidecar provides.

4. Storage is IndexedDB (Dexie) + localStorage — both work fine in Tauri's WebView

No changes needed for data persistence. API keys in localStorage, analytics/memory in IndexedDB via Dexie.

5. The /agentis-proxy route proxies to localhost:4200 (the engine)

This is separate from the LLM proxies above. In Tauri, since there's no Vite middleware, we'll need the engine sidecar to either expose its API directly (already does on port 4200) and have the frontend call http://localhost:4200 directly, or use Tauri commands as a bridge.