--- title: "The Frazer app, screen by screen · Frazer" description: "A tour of the Frazer app, the front door to the ADE: twelve screens from one working day at a demo organization, from the first run to a fan-out over 1,000 items, triage, the Inbox and deploys, and every way into the same boxes, sessions and approvals." url: https://frazer.ai/ade/tour index: https://frazer.ai/llms.txt tokens: 4078 --- > For agents: every page on frazer.ai is indexed at https://frazer.ai/llms.txt. # The Frazer app, screen by screen · Frazer **ADE** Tour # The Frazer app, screen by screen. The front door to the ADE. Twelve screens from one working day at Acme, a demo organization: what each one shows, what it does, and where it sits in the ADE. All of it is the real app, built by Frazer. [Download the Frazer app](https://frazer.ai/app#download) [See how the ADE works](https://frazer.ai/ade/how-it-works) The tour 12 screens · and every way in 1. [01 First run](#first-run) 2. [02 Home](#home) 3. [03 Session](#session) 4. [04 Review before the PR](#review) 5. [05 New fan-out](#fan-out) 6. [06 Fan-out run](#run) 7. [07 Triage](#triage) 8. [08 Inbox](#inbox) 9. [09 Squads](#squads) 10. [10 Knowledge](#knowledge) 11. [11 Deploy sheet](#deploy) 12. [12 Cloud](#cloud) 01 / 12 · First run Fig. 1 · product UI, demo organization *The Frazer app’s first run: lena signs in with a passkey and Acme’s single sign-on, picks her box lena-api for the agent to work on, keeps the balanced model route through Acme’s LLM gateway with a $10 daily budget, and chooses which skills and MCP servers to bring from her Hermes setup.* Fig. 1: First run. Product UI, demo organization. ## Sign in, then choose where the agent works. A passkey or your company’s single sign-on, then a box, or No machine for chat, research and knowledge. The model route comes from your organization’s LLM gateway, with its budget. A **Sign in** Passkey or SSO; this laptop connects to Frazer Access B **Where the agent works** Your box, a team box, a shared box or no machine C **Default route** Models through the organization’s gateway, with a daily budget D **Bring your Hermes** Skills, MCP servers, memory and sessions, each opt-in 02 / 12 · Home Fig. 2 · product UI, demo organization *Home in the Frazer app, demo organization Acme: “What should we build, lena?”, the composer with its pickers and five quick actions. Needs you: a staging deploy plan to apply, one question asked by 174 sessions of the pgx run, noah’s production deploy waiting for a second person, and lena’s assistant asking to email a supplier. Running now: the fan-out pgx-v57 at 412 of 1,000, a session, the squad platform-ops and a personal agent. Then recent sessions and lena’s boxes: lena-api running, lena-gpu asleep, and noah-api shared with her.* Fig. 2: Home. Product UI, demo organization. ## Everything that needs you, and everything running. One list of what needs a person, what runs without you, your recent sessions and your boxes. Five quick actions start anything, each with its key. A **Needs you** Plans, batched questions, approvals, outbound mail B **Running now** A fan-out, sessions, a squad, a personal agent C **Quick actions** New session, fan-out, deploy, open box, new agent D **Boxes** Yours, asleep until woken, or shared with you 03 / 12 · Session Fig. 3 · product UI, demo organization *A session in the Frazer app on the devbox lena-api, demo organization Acme. lena asked for a “waiting on customer” label that nudges the customer after three quiet days, tested on last week’s tickets, then a staging deploy. The agent’s run of work (a test run, an edit, a replay of 200 tickets and a browser step that created the label) is one row; the change to app/triage/rules.ts sits in a fence with Review; the staging deploy waits as a Plan card to apply. The side pane shows the preview, the files and artifacts, and the dev server’s terminal.* Fig. 3: Session. Product UI, demo organization. ## A session on your box. Chat with the agent on lena-api: one row per run of work, the diff in a fence, a Plan card to apply, and the preview, files and terminal on the right. Slash commands reach every tool. A **One row per run of work** Opens to one-line steps B **The diff, then Review** Hunk by hunk before a pull request C **A Plan card** Changes, checks and cost; apply with one key D **Pickers** Route, agent and box for the next prompt 04 / 12 · Review before the PR Fig. 4 · product UI, demo organization *Review before the pull request: three changed files hunk by hunk, one hunk accepted and one waiting, the Frazer Reviewer’s finding on the hunk it concerns, the checks the pull request will show on GitHub runners, and a draft pull request that takes accepted hunks only.* Fig. 4: Review before the PR. Product UI, demo organization. ## Accept hunks, then open the pull request. Accept or reject each hunk, see the checks the pull request will show, read the Reviewer’s pre-check on the hunk it concerns, and open a draft that takes accepted hunks only. A **Hunk by hunk** Accept Y, reject X, comment C B **Reviewer pre-check** A finding lands on the hunk it concerns C **Checks on GitHub runners** Tests, integration, replay, review D **Draft PR, as Git** Accepted hunks only, co-authored 05 / 12 · New fan-out Fig. 5 · product UI, demo organization *A new fan-out in the Frazer app, demo organization Acme, set up from the session “Upgrade pgx to v5.7”. A: a prompt template with six variables (module, test command, path, branch, repository, owner), five resolved on every item and the owner missing on two. B: 1,000 items from a catalog query, Go modules in 214 repositories that use pgx below v5.7, each checked as ready, a major-version jump or without an owner. C: how it runs: the Frazer agent, one headless session per item, on the Standard image; the balanced route with its own run key at batch priority; 100 sessions at a time; $1.50 per item and $400 for the run; draft pull requests on the Agent PR lane at 40 an hour; waves of a dry run on 3, then 10 %, then the rest. D: the three dry-run items, the smallest, the largest and a random one, and the checks before anything starts: quota, the gateway budget, the Agent PR lane’s runner-minutes, grants and the armed kill switch.* Fig. 5: New fan-out. Product UI, demo organization. ## One prompt over many items. A template with variables checked on every item; items from a catalog query, repositories, tickets, a dataset or a list; how it runs; and a dry run on three items picked for spread. A **Prompt template** Variables bound to each item B **Items** 1,000 modules from one catalog query C **How it runs** Harness, image, route, concurrency, budget, lane D **Dry run and checks** Quota, budget, lane and grants before you start 06 / 12 · Fan-out run Fig. 6 · product UI, demo organization *A fan-out run in the Frazer app, demo organization Acme: pgx v5.7 across 1,000 modules, running, wave 3 of 3; 412 of 1,000 finished, an ETA of about 2 hours 10 minutes, $163.20 of a $400 budget, 31 of 214 draft pull requests open. A: seven buckets: 64 done, 318 need review in 5 clusters, 212 wait on lena in 3 batched asks, 96 running of 100 slots, 280 queued, 19 failed, 11 skipped. B: results grouped by outcome, with the verifier’s passes and the Reviewer’s findings per cluster. C: waiting on you: 174 sessions ask the same question about the pgxpool tracer, answered once for all of them. D: limits: concurrency 96 of 100, the gateway run key at $163 of $400, the Agent PR lane with 1,140 runner-minutes left; the waves, the item rate and the armed kill switch.* Fig. 6: Fan-out run. Product UI, demo organization. ## Seven buckets and a few clusters. A run of 1,000 items at a glance: progress, cost against the cap and an ETA, results grouped by outcome, questions asked once, the waves and the limits. A **Buckets** Done, review, waiting, running, queued, failed, skipped B **Clusters** Grouped by the shape of the change C **Waiting on you** One question for 174 sessions D **Limits** Concurrency, the run key, the Agent PR lane 07 / 12 · Triage Fig. 7 · product UI, demo organization *Triage of the fan-out run pgx-v57 in the Frazer app, demo organization Acme. On the left, 318 results that need review in five outcome clusters, then what is decided: 64 accepted and 19 failed. A: the open cluster, “Import bump only, tests pass”, 196 items in 58 repositories: each changed only go.mod and go.sum, its tests passed, the verifier from another model family passed all 196 and the Frazer Reviewer found nothing. B: the representative, the median diff, bumping pgx from v5.5.0 to v5.7.4. C: a spot check of three random members, all the same change. D: accept the cluster, and open 58 draft pull requests in batches on the Agent PR lane at 40 an hour; three escalations wait for a person.* Fig. 7: Triage. Product UI, demo organization. ## Review by cluster, from the keyboard. A cluster’s representative and three random spot checks, then accept or reject all of it, or edit the prompt and retry as a new wave. Pull requests open in batches. A **Cluster** 196 items, the same change B **Representative** The median diff, with tests and verdicts C **Spot check** Three members, drawn fresh each time D **Pull requests** 58 drafts on the Agent PR lane 08 / 12 · Inbox Fig. 8 · product UI, demo organization *The Inbox in the Frazer app, demo organization Acme: 9 open, 5 need lena. Needs you now: 174 sessions of the pgx run ask one question, answered once for all; a staging deploy plan to apply; lena’s assistant asking to email an outside sender; noah’s production deploy waiting for a second person; the Frazer Reviewer’s findings on a pull request. Earlier today: the run’s digest, a high security finding on a deployed image and the LLM budget at 80 %.* Fig. 8: Inbox. Product UI, demo organization. ## Every decision in one list. Approvals, asks, reviews, security, budget and reports, with a key for each action. The same items reach the console, Slack and email. A **By type** Approvals, asks, reviews, security, budget, reports B **A batched ask** One answer goes to 174 sessions C **Standing answer** Covers sessions that have not asked yet D **Everywhere** J K to move, A approve, R deny; also Slack and email 09 / 12 · Squads Fig. 9 · product UI, demo organization *The squad platform-ops on the objective Calm on-call by December: key results read from PagerDuty and the runbooks, a guardrail, agents and people with their roles, a hire made inside the hiring policy, the board from ready to done, and the morning standup.* Fig. 9: Squads. Product UI, demo organization. ## A squad on an objective. A manager and workers on “Calm on-call by December”: key results read from real sources, members and a reversible hire, the board, and the morning standup. A **Objective** Key results and a guardrail, measured by Frazer B **Members** Agents and people, with roles C **A hire** Inside the hiring policy, reversible D **Board** Ready, in progress, review, needs a person, done 10 / 12 · Knowledge Fig. 10 · product UI, demo organization *Knowledge in the Frazer app: a question about how long support transcripts are kept, answered from the bases attached to the session with a citation on every sentence, the cost, time and faithfulness of the answer, the sources with who may see them, and one match left out because Lena cannot open it.* Fig. 10: Knowledge. Product UI, demo organization. ## Answers with citations, as you. Ask the company’s bases from a session or a box. Every sentence cites its source, and a match you cannot open is left out, with the owner to ask. A **Bases attached** On the session, or locked to the box B **An answer, evaluated** Cost, time and faithfulness shown C **Sources, checked for you** Each one with who may see it D **Left out** No access: ask its owner 11 / 12 · Deploy sheet Fig. 11 · product UI, demo organization *The deploy sheet in the Frazer app for inventory, demo organization Acme, from the session “Upgrade pgx to v5.7”. Kubernetes is recommended because inventory already deploys from envs/staging in acme/platform-envs with Frazer GitOps; serverless, a model endpoint, a GPU pod and an agent are the other choices. The service runs on the cluster acme-staging on Acme’s pool, rolls out as a canary from 10 to 100 percent and stays internal; it keeps its Postgres database, memory store, secrets by reference, uptime check and dashboards. The plan is a Git pull request with five changes; all five checks pass, from CI on GitHub runners to the Reviewer’s pre-check; it adds $0.00 a month on Acme’s servers and applies as lena, on behalf of the Frazer agent.* Fig. 11: Deploy sheet. Product UI, demo organization. ## Five targets, one plan. Serverless, Kubernetes, a model endpoint, a GPU pod or an agent. The sheet detects what the app needs, recommends a target with a reason, binds the data and secrets, and shows the plan with its cost. A **Target** Five kinds of deploy, one sheet B **The reason** Why this target, from what the code needs C **Bindings** Database, cache, model route, secrets, checks D **Plan** Changes, checks, cost, and who it applies as 12 / 12 · Cloud Fig. 12 · product UI, demo organization *Cloud in the Frazer app, team view, demo organization Acme: everything lena’s team runs in acme-staging, with state, last change, monthly cost and security findings; inventory is healthy after rolling out pgx v5.7 nine minutes ago. Alerts and events list a latency alert on pricing-api and the inventory rollout. The side pane shows inventory: 380 requests a minute, 0.1 % errors, p95 96 ms, uptime checks; its deploys, with the Frazer Reviewer watching the rollout for 21 more minutes and finding no regression, and a rollback one plan away; CI on GitHub runners, the signed image with no critical findings, and its secret references.* Fig. 12: Cloud. Product UI, demo organization. ## What you run, watched. Everything you deploy, from a session, the deploy sheet, the CLI or the console, with health, deploys, CI, the image, secret references and findings on one page. A **Mine, team, project** Scoped to what you own B **Health** Requests, errors, p95, uptime C **Deploys** Every revision; roll back as a plan D **CI** Main, people’s and agents’ lanes 13 · Every way in Fig. 13 ## Every way in. One identity behind all of them. Open the same boxes, sessions and approvals from the Frazer app, your editor, the console, a chat or your own code. One sign-in, one device check and one revoke, whatever you open the box with. - ### Frazer app Recommended. Every tool, Plan cards, sessions by box. macOS · Windows · Linux - ### VS Code and editors built on it The Frazer extension: Remote-SSH through Frazer Access; sessions, boxes and approvals in panels. Marketplace · Open VSX - ### JetBrains Toolbox remote development; a Frazer plugin lists your boxes. Toolbox - ### Console The whole platform in the browser: approvals, access, billing, fleet and policies. console.frazer.ai - ### Slack and Teams Talk to agents and get digests. Approvals open in Frazer, never in the chat. business channels - ### CLI and API The frazer CLI and the API: the same plans, the same approvals. frazer devboxes ssh lena-api - ### MCP Any MCP client through Frazer’s MCP server, with grants that start read-only. mcp.frazer.ai - ### Browser A web IDE and terminal on your box, for its owner and members. no install *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. 13** The Frazer extension in VS Code, connected to lena-api product UI, demo organization The ADE ## Keep going. - ### [How it works](https://frazer.ai/ade/how-it-works) One piece of work, from a prompt to production, in eight steps on the real screens. - ### [A thousand sessions](https://frazer.ai/ade/sessions) Fan-out, waves and budgets, where sessions run, and how results come back. - ### [Stay in charge](https://frazer.ai/ade/control) Approvals, budgets, guardrails, grants and Secrets, audit and the kill switch. ## Open the front door. The rest of the ADE is behind it. [Download the Frazer app](https://frazer.ai/app#download) [Start building](https://frazer.ai/start?product=app)