/admin. To see what your own sessions cost, use Usage instead. To let one person watch a session, share it.
The dashboard refreshes every 15 seconds while it’s on screen, and the header says how fresh the figures are. It reopens on the tab you used last in this browser. Each change you make shows its result in a green banner, or the server’s reason in a red one.
Who is an admin?
An admin is an account with the admin role. Alpha shows the Admin row only to admins, and the server refuses every admin request from anyone else. Anyone else who opens/admin reads “This account doesn’t have the admin role. An admin can grant it from this page, or FORGE_ADMIN_EMAILS on the server pins it.”
On an Alpha with accounts, new accounts start without the role, so nobody is an admin until
FORGE_ADMIN_EMAILS names someone. While no admin is pinned and there is at most one admin, the Overview warns: “No admin is pinned by configuration — set FORGE_ADMIN_EMAILS so a locked-out admin can always get back in.”
If you don’t see Admin in the account menu, your account doesn’t have the admin role. In guest mode everyone sees it. Every change made from the dashboard is written to the server’s log with the name of the admin who made it. There is no separate audit table, so the server log is the record.
Read the overview
The Overview tab answers “is anything wrong, and who is working?” at a glance.
Click any session row to watch it. You open it read-only, as a viewer: you see the transcript, the files and the Preview, but you can’t send a message, and you don’t get the owner’s Publish, Shell or settings. See what viewers can do.
Approve and manage accounts
The Users tab lists every account, 50 to a page. Accounts waiting for approval come first, then the rest by spend. Search by name, email or id. Each row shows the account’s role chips, its sessions (● running, ⟳ working), its spend over 30 days and all time, how many browsers it is signed in on, and what it has connected: GitHub, integrations, secrets, and any ChatGPT or Claude sign-in. Some columns appear only in a wide window.Approve someone on the waitlist
WhenFORGE_ALLOWED_EMAILS limits who can sign in, a Google or Microsoft sign-in from an address that isn’t on it gets an account and a place on the waitlist. If FORGE_WAITLIST_SLACK_WEBHOOK is set, your team’s Slack channel hears about each new one.
1
Find the waiting account
Open the Users tab. Accounts with a waiting chip are listed first.
2
Click Approve and confirm
The dialog shows the account’s name and email and when they asked. “They can open Alpha right away: start sessions, use machines and spend on models. You can sign them out or delete the account later.” Click Approve.
3
Tell them to check again
The banner reads “Sam Rivera can use Alpha now.” They get in the next time they press Check again or refresh the waitlist screen.
FORGE_ALLOWED_EMAILS lets them in too. Emptying the list lets everyone waiting in at once.
Change roles and sign-ins
Step in on a session
The Sessions tab lists every session on your Alpha, 50 to a page, by last activity. Search by title, owner, model, agent, repository or id, and narrow the list with All, Working, Machine on or Shared. Under each title you see the owner, plus Claude Code if that’s the agent, the setup it started from, its repositories and any queued messages. The State column reads running, parked (asleep), booting, cold (no machine yet; one starts on the next message) or working, with a deploying chip while an app publishes. A spend marked ≈ is estimated, and one in amber includes turns on a model nothing prices.
For what a reset keeps on the owner’s side, see Sleep, wake and reset.
Clean up orphan machines
The Machines tab lists every machine your Alpha’s machine server reports, each matched to what claims it. Four tiles count them: Running (“VMs on a node right now”), Paused (“on their node, resumable”), Checkpointed (“sessions parked as snapshots, no VM”) and Orphans.
An orphan is a machine that nothing on your Alpha claims. Deleting it asks first: “Nothing on this Alpha claims it; whatever is inside is lost.” The Overview shows a notice whenever there is one to clean up.
See spend and published apps across Alpha
The Usage tab is your whole Alpha’s spend, “priced as the Usage page prices it”. Pick Today, 7 days, 30 days or All time; the choice is remembered in this browser. The tiles show spend and turns for the range, all-time spend, Accounts billed and Agent time. Below are Spend by day, By account, Sessions (click one to watch it) and Models. If a model has no price, its turns count as $0 and a notice names it. SetFORGE_MODEL_PRICES on the server to price it, and its past turns are priced too. Work that ran on people’s own ChatGPT or Claude plans is shown beside the totals, never in them. How prices are found is explained in Usage, costs and your own plan.
The Deploys tab lists every app published on your Alpha. Search by name, address, session, owner or status. Each row shows the service and its address, a status chip (queued, exporting, planning, building, deploying, live, failed or deleting), the session and its owner, the number of rollouts and when it last published.
From here you can Open the deployed app or Watch the session. Changes to a published app are the owner’s, from the session’s Publish tab. You watch as a viewer, so you don’t get that tab. See Manage a published app. If publishing isn’t turned on for your Alpha, a notice at the top says so and names the setting that turns it on. Apps published before it was turned off are still listed.
Choose what the integrations catalog offers
The Integrations tab decides which hosted MCP servers and apps every account sees under Integrations. Switch between MCP and Composio at the top. A third choice, ACI, is marked Coming soon and can’t be opened.
New apps are added in Composio, not here. Use Manage in Composio to open its dashboard. Until one is set up there, the tab reads “No Composio auth configs yet. Create one in Composio’s dashboard.”
Add a hosted MCP server
1
Open the form
On MCP, click Add server. The dialog is titled Add a hosted MCP server to the catalog.
2
Fill in the fields
Use the table below. The server checks every field and names the first one it can’t accept.
3
Click Add to catalog
The server appears in the catalog switched on, so every account is offered it at once. Switch it off first if you want to test it before others see it.
How people then connect to it is on MCP servers.
Share skills and check the server
Admins share skills from the ⋯ menu in one of their own skills’ dialog, not from this dashboard. Ship with Alpha puts a skill in every account’s sessions. Add to catalog lists it under From Alpha for each account to install. Unpublish gives it back to the account that added it. Only an admin can edit a shared skill. See Who can change a shared skill?. The Server tab is a read-only view of what your Alpha is running with. Nothing on it can be changed from the dashboard; whoever runs your server changes these settings there. Use it to check a setting before you report a problem.
Some values marked “(default)” on Limits, such as the turn cap and the publishing limits, appear here as your Alpha actually has them.
Next steps
Share a session
What a viewer sees, which is exactly what you see when you watch a session.
Sleep, wake and reset
What a reset keeps and loses from the owner’s side, and why machines sleep.
MCP servers
How people connect to the hosted servers you switch on here.
Limits
Every number your Alpha enforces. The Server tab shows your Alpha’s own value for several of them.