The web app
Mesa's web app is where you sign in to manage your own connected accounts and browse your groups. Most of what Mesa does happens in your messaging app — you talk to a bot in Telegram or by email, and the web app is a companion to that rather than the main event.
This page says plainly which parts of the web app are finished, because several are not, and a half-built screen is easier to deal with when you were expecting it.
What each screen does today
The navigation shows seven destinations. They are not all at the same stage.
| Screen | State |
|---|---|
| Integrations | Live. Reads and writes your real data. See Tool integrations. |
| Home | Preview. The layout is real; the content is sample data, the same for everyone. |
| Groups | Preview. Same — a working browser over sample groups, not your groups. |
| Timeline | Not built yet. The page reads "Coming soon". |
| Tasks | Not built yet. The page reads "Coming soon". |
| Search | Not built yet. The page reads "Coming soon". |
| Settings | Not built yet. The page reads "Coming soon". |
What "preview" means here
Home and Groups render from a fixed sample dataset that ships with the app
(frontend/apps/web/src/lib/data/mock-provider.ts). Every account sees the same groups, the same
tasks and the same activity, and nothing you do on those screens is saved anywhere.
They are worth looking at to see where the product is going. They are not worth reading as a report on your account. If a group you recognise does not appear, that is expected — none of them are yours yet.
The switch is a single file: frontend/apps/web/src/lib/data/index.ts currently re-exports the
sample provider and nothing else. When those screens are connected to real data, that is the line
that changes.
Where the real controls live
Because the web app's Settings screen is not built, the things you might look for there are elsewhere:
| Looking for | Go to |
|---|---|
| Connecting your own accounts to tools | Integrations in the web app — this part is live |
| Your name, email, password, sign-in method | Your account menu, which is handled by the sign-in provider. See Accounts & sign-in |
| Provider API keys | The admin console. See API keys |
| Anything about a bot — model, channels, behaviour | The admin console. See Creating a bot |
| How chatty a bot is in a conversation | The /verbosity command, in the conversation itself. See Verbosity |
Two screens that are not in the navigation
Both are reached by link rather than by browsing, and both are real.
- Context traces (
/context-traces) shows how the context for a reply was assembled — which messages were pulled in and from where. It is a diagnostic view; see Context & memory. - Thread assignment (
/assign-thread/<token>) is reached from a link Mesa emails you when an email thread needs to be assigned to a group. Only the person who sent the original email can complete it. See Email.
Signing in
The web app requires an account and, for most screens, a tenant — the workspace your data belongs to. If you belong to more than one, a picker appears before the page loads. Sign-in itself is handled by Clerk; see Accounts & sign-in.