Last Updated: 9/2/2026
The Web Dashboard
Overview
My Dashboard is a group of pages in the sidebar when you open Jolli in your browser. They report what your organization’s machines have synced: the memories and decisions your repositories pushed, and the sessions your AI tools ran. Everything is filtered by a date range and a set of repositories you choose.
There are two groups, My Dashboard and Team Dashboard, holding the same five pages each. The group says whose work you are reading: your own, or everyone’s.
This is not the same thing as jolli dashboard, which runs on your own machine and reads it directly. That one is The Local Dashboard. Both call their personal view My Dashboard, so if you need to be sure which you are looking at, the line under the heading says: individual · synced here, individual · local there.
Prerequisites
- Nothing, for the My Dashboard group. Everyone can open it.
- View Team Memory Activity permission, for the Team Dashboard group. Owners and administrators have it; members do not. If you need it and you are a member, your administrator can move you to a custom role that includes it. See Settings.
- For the session half of these pages to have anything in it, session statistics must be syncing from at least one machine. That needs the CLI at 0.99.14 or later and someone signed in on it. See Where the numbers come from below.
The two groups
| Group | Address | Who can open it |
|---|---|---|
| My Dashboard | /dashboard | anyone |
| Team Dashboard | /dashboard/team | needs View Team Memory Activity |
My Dashboard reports your own work. Team Dashboard reports everyone in the organization: their commits, branches, sessions and spend. The Team Dashboard group is simply absent from the sidebar if you do not have the permission, and the address refuses too, so a shared link cannot get around it.
If you had the old Analytics page bookmarked, that address now lands here.
The five pages
Each group holds the same five pages. Every one takes the same date range and repository picker, and reads whichever scope its group names.
| Page | Address | What it answers |
|---|---|---|
| Dashboard | /dashboard | The overview: all the cards described below, on one page. |
| Standup | /dashboard/standup | A week of committed work laid out as day columns, for “what did I do since yesterday”. A weekly pager moves back and forward. Only work that reached a commit and synced appears, so uncommitted work and local changes are not shown. |
| Coaching | /dashboard/coaching | Your journeys read against your own earlier line: how many in the window, plan-first share, cost and recall, with individual journeys openable as a trace. Marked Beta. |
| Skills | /dashboard/skills | Every skill day by day, with runs and tokens, and per-skill detail. More grain than the Skills card. |
| MCPs | /dashboard/mcp | Every MCP server day by day, with calls and tools, and per-server detail. More grain than the MCPs card. |
Under Team Dashboard the same five sit at /dashboard/team, /dashboard/team/standup, and so on. The team Coaching page reads against the team’s earlier line rather than your own, and reports across members.
Choosing what you are looking at
A date range. 7d, 30d and 90d are one click each. Custom opens a calendar with quick ranges beside it: Last 14 days, This month, Last month, and Year to date. The longest range you can ask for is 366 days.
A set of repositories. The picker defaults to All repositories. Clearing it entirely is possible in one click, so if you get Select at least one repository, that is what happened.
What each card reports
These are the cards on the Dashboard page itself. Skills and MCPs appear here as cards and again as their own pages, where the same data is broken out per skill or per server.
| Card | What it counts |
|---|---|
| Memory Activity | Memories captured over the range, split however you choose: by type, model, repo, branch or time. |
| Decisions | Decisions your sessions recorded, accumulating across the range, each with the commit behind it. |
| Skills | Skill invocations, read from the tool calls in synced sessions. A skill invoked inside a subagent counts once, against the session that spawned it. |
| MCPs | MCP tool calls: which tool, and how often. Never the arguments or the results. Only servers that actually made a call in the range appear. |
| Tokens | Daily token use, stacked as Input, Output and Cache. |
| Spend | Daily estimated cost. |
| What my agents did | The session feed itself. On the Team view it reads What the team’s agents did. |
Two things about the numbers are worth knowing before you rely on them:
- Spend is an estimate, never an invoice. It is calculated from the usage in synced sessions and the price table in effect for each model.
- Cache reads bill at a fraction of input, so a rising cached share lowers cost while token counts climb. That is why Tokens and Spend can move in opposite directions, and why they are two cards rather than one.
Each card carries a short note on its own title explaining what it counts. Ranked lists load a page at a time: Show more brings one more page, not the whole list.
Where the numbers come from
The page has two halves, and they arrive by different routes. This is why it can look half-empty.
- Memories and decisions arrive when your repositories push memories, which is the same path as Share in Jolli. If you are pushing memories, this half has data.
- Sessions, skills, MCP calls, tokens and spend arrive over the session-statistics channel, which uploads from a signed-in machine running CLI 0.99.14 or later. It is on by default once you are signed in, and it covers every repository Jolli is enabled in on that machine.
So if the memory cards have data and the session cards do not, nobody’s machine is uploading session statistics yet. The empty state says so in as many words: memories appear after your next commit, and session statistics additionally need the session sync.
Every surface can now feed these pages. The JetBrains plugin bundles its own copy of the CLI and is at 0.99.17, and the Claude Code, Cursor and Codex plugins bundle theirs at 0.99.16, so a signed-in machine reports from any of them like any other.
The plugins run one release behind the CLI between their own updates, because a new plugin build is what carries a new engine. If your session cards are empty on a machine that only has a plugin, check you have taken the plugin update.
The setting that controls the session half is syncSessions, on by default once you are signed in. If the session cards stay empty on a machine you expect to be reporting, push whatever is waiting rather than waiting for the next upload, which is throttled:
jolli doctor --sync-sessionsThat reports what it sent, or why it sent nothing.
For exactly what the session channel sends, and how to switch it off, see Troubleshooting and FAQ.
What is not here
The knowledge Wiki and the Graph have no equivalent here. They exist only in the local dashboard, on your own machine. Coaching and the Standup used to be local-only as well and are now on both. See The Local Dashboard.
Related
- The Local Dashboard - the dashboard that runs on your own machine, and what only it can show.
- Troubleshooting and FAQ - what session statistics carry, and how to turn them off.
- Settings - roles, the permission matrix, and API keys.
- Supported AI Agents and Capture - how each session gets attributed to an agent, which is what the per-agent breakdowns here are built on.