--- title: "The Frazer app: the ADE’s front door · Frazer" description: "The Frazer app is the front door to the ADE, the Agentic Development Environment: a desktop app built by Frazer, with its own agent engine and every Frazer tool inside. The Frazer extension brings the same boxes, sessions, agents, reviews and deploys to VS Code and the editors built on it." url: https://frazer.ai/app index: https://frazer.ai/llms.txt tokens: 1360 --- > For agents: every page on frazer.ai is indexed at https://frazer.ai/llms.txt. # The Frazer app: the ADE’s front door · Frazer Frazer app · The ADE’s front door macOS · Windows · Linux # An app you can work in from day one. With the whole cloud inside. The Frazer app is the front door to the ADE, the Agentic Development Environment. Built by Frazer, with its own agent engine written in Rust, it has every Frazer tool inside: devboxes, servers, agents and squads, fan-out runs, review, security, knowledge, deploys and GPUs, and it works on a devbox already set up for your company. [How the ADE works](https://frazer.ai/ade) [Start building](https://frazer.ai/start?product=app) [The VS Code extension](#extension) macOS on Apple Silicon · Windows 11 · Linux, AppImage and deb Signs in with your Frazer account; no SSH settings Download the build for your platform from the console after you sign up. Fig. 1 · Agents tool open, session on lena-api product UI, demo organization *The Frazer app with the Agents tool open: a session on the devbox lena-api upgrades pgx in inventory, the Frazer Reviewer reproduces one finding and the verifier passes the fix, and the agent offers the upgrade to 13 more repositories as a campaign with a canary and a $40 budget.* Fig. 1: the Frazer app, Agents tool open, session on lena-api. Product UI, demo organization. 01 · Every Frazer tool, one window 9 panels · MCP toolsets ## Not an editor with a chat box. Your whole platform, in reach. Each panel is a Frazer plugin over the same MCP toolset the agent uses. 1. ### Sessions Chat with the Frazer agent on your box. Resume on any device; hand off to the background. Frazer 2. ### Devboxes Pick, create, resize and share boxes. Previews, ports and the terminal in the right pane. frazer.devbox 3. ### Agents “Make this an agent”: triggers, standing agents, campaigns across many repositories. frazer.agents frazer.campaigns 4. ### Review Frazer Reviewer findings with evidence, the verifier’s verdict, one-click fixes. frazer.review 5. ### Knowledge Ask your company bases; every answer cites its sources and respects permissions. frazer.knowledge 6. ### Deploy “Kubernetes or serverless?” with a reason, then one Plan card, database included. frazer.run frazer.deploy frazer.data 7. ### Servers Your servers and pools, capacity before you ask for it, accept a new server. frazer.servers 8. ### GPUs Deploy a model, fine-tune it, open a GPU pod; share one model across boxes. frazer.ai 9. ### Security Findings that touch your work, agent activity, approvals waiting for you. frazer.security frazer.observe 02 · How it is built Fig. 2 ## The agent lives on the box. The app is a window onto it. Close the laptop and the work goes on. The app, the extension and the terminal all reach the same gateway with short-lived credentials bound to you, the box and your device. **Fig. 2** Laptop, devbox, control plane 03 · Live in VS Code? Keep it. Fig. 3 ## The Frazer extension for VS Code and editors built on it. The same boxes, sessions, agents, reviews, deploys and knowledge, in the editor you already use. - Opens any devbox with Remote-SSH through frazer devboxes proxy over Frazer Access. No keys on disk - Chat goes to the Frazer agent on your box, so work continues when the editor closes - Reviewer findings inline, Plan cards in a panel, Apply with the same approvals - In the VS Code Marketplace and on Open VSX [Start building](https://frazer.ai/start?product=app) *The Frazer extension in VS Code, connected to the devbox lena-api over Remote-SSH: a Frazer sidebar lists devboxes, sessions, agents, reviews, deploys and knowledge; a Frazer Reviewer note sits inline in repo.go; the Frazer: Plan panel shows a staging deploy plan ready to apply.* **Fig. 3** The Frazer extension in VS Code, connected to lena-api · product UI, demo organization 04 · Every way in ## One identity, one device check, one revoke. Whatever you open the box with. - ### Frazer app Recommended. Every tool, Plan cards, sessions by box. - ### VS Code + extension Remote-SSH through Frazer Access; Frazer panels. - ### Other VS Code-based editors Their own remote-SSH plus the extension. - ### Hermes Hermes Desktop or TUI on the same gateway, through Frazer’s Hermes plugin. - ### JetBrains Toolbox remote development; a Frazer plugin lists boxes. - ### Zed Headless server on the box over SSH. - ### Terminal `frazer devboxes ssh lena-api` - ### Browser Web IDE and terminal, owner and members only. 05 · Built by Frazer ## Our own engine. Open to your harness. ### Frazer’s own engine The app’s agent engine is the Frazer harness, written in Rust by Frazer, so we control every step from your prompt to the deploy. ### Plugins for your harness We publish plugins for popular harnesses such as Hermes, so the harness you already use reaches your devbox, models and Frazer’s tools. ### Your code stays yours Transcripts stay on your box. Crash reports never include content; your organization can turn usage data off. ## Open the front door. The rest of the ADE is already there. [Start building](https://frazer.ai/start?product=app)