Last Updated: 8/20/2026

The Local Dashboard

Overview

jolli dashboard opens a dashboard for your memories in your browser. It runs entirely on your own machine: a small web server started by the command, reading the memories Jolli has already captured. Nothing is uploaded, and no Jolli account is needed to use it.

jolli dashboard

Run it from inside a repository and it registers that repository, opens the page, and keeps serving until you stop it. Memory does not have to be enabled there yet: the pages all render, and before you have enabled anything they tell you what to do rather than sitting empty.

Prerequisites

• The jolli CLI installed, and Node 22.13 or later - the same floor as the CLI itself, because the dashboard’s database uses Node’s built-in SQLite. On an older runtime the command reports the version it needs instead of starting.
• Nothing else. No Jolli account, and no repository enabled yet.

Where you can open it

The dashboard is local, and it is the CLI’s. Every surface that offers it is running the same jolli dashboard underneath:

There is no dashboard on the web. Jolli in your browser shows the memories you have pushed to a Space as read-only pages. The stats, standup, knowledge, and graph views exist only here, on your own machine.

What you see

Five pages sit in the sidebar: My Dashboard and Daily Standup together under Dashboard, then Memories, Knowledge, and Graph. Settings is pinned to the bottom of the sidebar and opens over whichever page you are on rather than replacing it.

Every page is reachable as soon as the dashboard starts. Before you have enabled anything, My Dashboard tells you what to do rather than sitting empty: it shows No repositories yet and asks you to run jolli enable inside the repository you want to start with.

Knowledge and Graph read your Memory Bank folder rather than the dashboard’s own registry, so the repositories they cover can differ from the ones listed elsewhere. Each has its own empty state when there is nothing to show yet.

Starting and stopping it

The dashboard runs in your terminal. jolli dashboard serves it until you press Ctrl+C, and the command does not return before then.

jolli dashboard --no-open       # serve it and print the URL instead of opening a browser
jolli dashboard --port 3000     # serve on a specific port
jolli dashboard --cwd <dir>     # register a different repository than the current directory

Without --port it uses 1818, and falls back to 18118 if that one is taken.

Running jolli dashboard again replaces the one already running, so you always get a fresh dashboard at the address you expect. If an older version left a server running in the background, the new run takes it over. Anything else using port 1818 is left alone.

Earlier versions kept the server running in the background and stopped it with jolli dashboard --stop. That flag no longer exists, because there is no longer a background server to stop.

What happens on the first launch

The dashboard reads from its own local database rather than re-reading git on every page load, so the first launch has to fill that database from the memories you already have. That import runs in the background while the page is open: the page renders whatever is stored so far and fills in as the sweep lands, rather than making you wait.

It also looks through your agents’ own session history from the last seven days, not only what Jolli had already recorded, and prints one line saying what it picked up.

This import is not the same thing as jolli backfill. It only reads summaries that already exist, so it makes no AI calls and costs nothing. Creating memories for commits made before you enabled Jolli is still an explicit jolli backfill, run from the CLI.

More than one repository

The dashboard is not scoped to the repository you launched it from. It keeps a registry of repositories, and each jolli dashboard run adds the one you ran it from, so over time it becomes a view across everything you work on. Per-repository totals on My Dashboard reflect that registry.

The repository picker in the top bar chooses which of them you are looking at. It filters the view and nothing more: it does not enable, pause, or resume anything. Turning Memory on or off for a repository is jolli enable and jolli disable, run inside that repository. Disabling removes that repository’s hooks, so no new memories are captured there until you enable it again. Existing memories are never touched, and the repository keeps its row, so enabling it again needs no second import.

It is local, and it stays local

Three things are true about access, and they are worth knowing if you are wondering whether an open port is a problem:

• The server listens on loopback only and serves only localhost and 127.0.0.1 addresses. It is not reachable from another machine on your network.
• It sends no cross-origin headers, and rejects any request that arrives from a web page, so a site you have open in another tab cannot read what it serves.
• Actions that change something, such as enabling a repository or applying a setting, are additionally protected by a token that exists only in the running server’s memory and is never put in a URL.

Reading pages needs no credential, which is why http://localhost:1818/dashboard simply works if you would rather type it than have a browser opened for you.

Related

• Reference - the full flag list for jolli dashboard and every other command.
• Memory Bank and Sync - where memories are stored on disk, and the one-way move to local database storage.
• Getting Started with Jolli Memory - install, sign in, and your first Memory.