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.
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 inPasskey or SSO; this laptop connects to Frazer Access
- B
- Where the agent worksYour box, a team box, a shared box or no machine
- C
- Default routeModels through the organization’s gateway, with a daily budget
- D
- Bring your HermesSkills, MCP servers, memory and sessions, each opt-in
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 youPlans, batched questions, approvals, outbound mail
- B
- Running nowA fan-out, sessions, a squad, a personal agent
- C
- Quick actionsNew session, fan-out, deploy, open box, new agent
- D
- BoxesYours, asleep until woken, or shared with you
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 workOpens to one-line steps
- B
- The diff, then ReviewHunk by hunk before a pull request
- C
- A Plan cardChanges, checks and cost; apply with one key
- D
- PickersRoute, agent and box for the next prompt
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 hunkAccept Y, reject X, comment C
- B
- Reviewer pre-checkA finding lands on the hunk it concerns
- C
- Checks on GitHub runnersTests, integration, replay, review
- D
- Draft PR, as GitAccepted hunks only, co-authored
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 templateVariables bound to each item
- B
- Items1,000 modules from one catalog query
- C
- How it runsHarness, image, route, concurrency, budget, lane
- D
- Dry run and checksQuota, budget, lane and grants before you start
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
- BucketsDone, review, waiting, running, queued, failed, skipped
- B
- ClustersGrouped by the shape of the change
- C
- Waiting on youOne question for 174 sessions
- D
- LimitsConcurrency, the run key, the Agent PR lane
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
- Cluster196 items, the same change
- B
- RepresentativeThe median diff, with tests and verdicts
- C
- Spot checkThree members, drawn fresh each time
- D
- Pull requests58 drafts on the Agent PR lane
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 typeApprovals, asks, reviews, security, budget, reports
- B
- A batched askOne answer goes to 174 sessions
- C
- Standing answerCovers sessions that have not asked yet
- D
- EverywhereJ K to move, A approve, R deny; also Slack and email
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
- ObjectiveKey results and a guardrail, measured by Frazer
- B
- MembersAgents and people, with roles
- C
- A hireInside the hiring policy, reversible
- D
- BoardReady, in progress, review, needs a person, done
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 attachedOn the session, or locked to the box
- B
- An answer, evaluatedCost, time and faithfulness shown
- C
- Sources, checked for youEach one with who may see it
- D
- Left outNo access: ask its owner
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
- TargetFive kinds of deploy, one sheet
- B
- The reasonWhy this target, from what the code needs
- C
- BindingsDatabase, cache, model route, secrets, checks
- D
- PlanChanges, checks, cost, and who it applies as
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, projectScoped to what you own
- B
- HealthRequests, errors, p95, uptime
- C
- DeploysEvery revision; roll back as a plan
- D
- CIMain, people’s and agents’ lanes
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 · LinuxVS Code and editors built on it
The Frazer extension: Remote-SSH through Frazer Access; sessions, boxes and approvals in panels.
Marketplace · Open VSXJetBrains
Toolbox remote development; a Frazer plugin lists your boxes.
ToolboxConsole
The whole platform in the browser: approvals, access, billing, fleet and policies.
console.frazer.aiSlack and Teams
Talk to agents and get digests. Approvals open in Frazer, never in the chat.
business channelsCLI and API
The frazer CLI and the API: the same plans, the same approvals.
frazer devboxes ssh lena-apiMCP
Any MCP client through Frazer’s MCP server, with grants that start read-only.
mcp.frazer.aiBrowser
A web IDE and terminal on your box, for its owner and members.
no install
Keep going.
How it works
One piece of work, from a prompt to production, in eight steps on the real screens.
A thousand sessions
Fan-out, waves and budgets, where sessions run, and how results come back.
Stay in charge
Approvals, budgets, guardrails, grants and Secrets, audit and the kill switch.