01 · REQUEST
Tell us how you hope to use it
Submit the accessible access request with your name, email, platform, and intended use. A request does not guarantee approval.
Private beta · access by approval
Start with an idea.
Leave with something real.
A calm path from requesting access to starting your first local project. The private beta grows deliberately so participant feedback can be reviewed and acted on.
The user journey
One step at a time, with no magic promises.
The desktop beta is a local tool, while identity, application review, and protected downloads use this website. The exact screens and provider setup can vary by platform and connection.
02 · VERIFY
Verify your email
Use the newest short-lived link sent to your inbox. For privacy, public forms never reveal whether another application already exists.
03 · REVIEW
Wait for a decision
The independent maintainer reviews requests. Sign-in and approval are separate: a verified account still needs current approval to download.
04 · LAUNCH
Open the local app
Launch Agents Chat from your installed application. The beta runs locally; it does not create an Agents Chat cloud workspace for you.
05 · CONNECT
Choose your agents
Complete onboarding, review what the app finds, and connect only the agents or providers you want to use. Agents Chat does not bundle provider subscriptions or credentials.
06 · BEGIN
Start a first project
Give the team a small, clear outcome and point it at a project folder when the work needs files. Begin with something you can inspect easily.
07 · ORGANIZE
Choose a teamwork mode
Use the pattern that matches the work: a direct builder for a focused task, a coordinator for a larger plan, or a review-oriented mode when you want more separation.
08 · REVIEW
Use Mission Studio when useful
For work with several stages, Mission Studio can make plan, build, verify, review, and integrate visible. Steer the work, inspect the evidence, and keep your approval in the loop.
09 · FINISH
Export and share feedback
Review the messages, decisions, checks, artifacts, and costs. Keep the result or export what you need, then send feedback to the maintainer.
Choose your starting point
Same local-first idea. Different installer.
Both platform paths begin in the protected download area after verified sign-in and approval. Available packages and real metadata are shown there.
macOS beta
After approval, choose the macOS package in your protected download area. If package-signing or publisher-provided integrity instructions accompany it, follow them before installing.
View your accessWindows beta
After approval, choose the Windows package in your protected download area. If package-signing or publisher-provided integrity instructions accompany it, follow them before installing.
View your accessBefore you connect anything: provider accounts, model access, and pricing belong to the services you choose. Check those providers’ own terms and data policies.
When the work gets bigger
Make the team’s work easier to inspect.
Mission Studio is useful when a project benefits from a visible sequence: plan the outcome, bound the work, run checks, review the result, and decide what becomes final.
See Mission Studio on the homepage →A practical loop
Steer. Verify. Review. Decide.
Agents can help with the work, but they do not replace your judgment. Keep consequential choices reviewable.
- Keep host checks authoritative
- Inspect artifacts and decisions
- Stop or redirect when the result is unclear
- Approve what becomes final
Know what you are trying
Useful, local, and still a beta.
Local by design
Desktop working state stays on your computer. Access account and application records are stored by this website; connected providers may process data under their own policies.
No automatic access
Agents Chat does not include AI subscriptions, provider keys, or guaranteed access to paid services.
Results need review
Checks, limitations, and human judgment still matter. No outcome is guaranteed by this website or the beta.
Your next small project
Ready to see where it breaks?
Request private beta access, try a contained workflow if approved, and tell the solo maintainer what happened.
Request access