Workspace Overview

The Overview is the landing page after login (route /dashboard, under the DATA section of the sidebar). It shows what your memory is doing right now: what it cost, how well it answers, and what ran most recently. A user who has never completed onboarding is sent to the onboarding flow first — it is shown once per user and never re-forced, whatever the workspace activity. While the workspace provisions, a skeleton is shown, and a Your workspace is ready notice appears once it is ready. At the top you see a time-based greeting (Good morning, Good afternoon, or Good evening) with your name, and — when an agent is selected — a lavender chip naming its type.

​

Get started

Get started is a collapsed strip under the greeting — below the credit banner when one is showing — carrying the subtitle Connect your AI agents to give them persistent memory and a count of the agents that have ever connected — 3 connectors, or 1 connector in the singular. It counts lifetime registrations, not agents currently running. Use Expand ▾ / Collapse ▴ to open it. Expanded, it presents the connection cards: Clicking an agent card opens a Connect modal with the steps for that tool, and a Mac / Windows toggle that rewrites them — see Mac / Windows. The Claude Code and Codex flows write your credentials to ~/.cognee/.env; the Openclaw and API / MCP flows print environment-variable commands to run in the terminal you will start the agent from — export … on Mac, $env:… = … in PowerShell on Windows — and tell you to add them to your shell profile to keep them across terminals. The Company Dataset card opens the file picker instead, and uploads straight into a dataset without leaving the page. Once files are processed, a Knowledge graph built modal offers next steps: Search your data, Inspect the knowledge graph (the dataset in Datasets), and Explore the knowledge graph (the Mindmap). Which dataset the files land in depends only on how many you have: with more than one, an Upload to which dataset? picker always appears first; with exactly one, they go straight into it; with none, a dataset named default_dataset is created for them. Accepted file types are .pdf, .csv, .txt, .md, .json, and .docx.

​

Overview panels

Below the strip, an Overview heading (Balance, spend, and usage across your workspace) introduces four panels: the memory flow diagram, Cost Savings, Memory Coverage, and Activity.

​

Memory flow

A framed diagram shows how memory moves through your workspace: Data sources on the left, the COGNEE MEMORY core in the middle, and Agents on the right, wired together with spokes. A live badge on the core’s stroke reflects workspace health. Each element navigates: A Teams row with team cards and a + Create a new team button is built but not yet shown: the whole row is hidden until real team data is wired in, rather than showing an empty grid.

​

Cost Savings

The Cost Savings panel leads with the tokens your memory saved: a large figure and the label tokens saved, with a sub-line reading $X less than the same work at Opus 5 list prices · estimated. The estimate assumes the same work would consume a multiple of the tokens without Cognee’s recall, priced at the comparison model’s list rate, against what Cognee actually cost at the gateway rate. Tokens are the honest unit here — on usage-based billing they convert to cash, on a subscription they are limit headroom left unspent. The panel header carries your Balance in USD and a range toggle (24h, 7d, 30d) that scopes only this panel. The chart plots one series, keyed what cognee cost. View breakdown → opens Analytics carrying the same range. Three honesty details worth knowing:

• The headline reads —, not 0, until the activity feed has measured tokens for the range. A genuine zero renders as 0.
• When neither billing nor the feed has priced the range at all, the sub-line reads No spend priced for this range yet instead of a dollar figure.
• When the feed is capped at one page, an amber at least flag appears beside the headline: the token figure counts the newest slice only, while the dollar line comes from billing and is not capped the same way.

​

Memory Coverage

The Memory Coverage panel is a glance view of Memory Coverage, which replays the questions your workspace was really asked and scores how well memory answered them. The panel shows Real recall as a percentage over a full-width meter, then Coverage by dataset as one lavender hairline per dataset with its score. Each percentage is a dataset’s coverage score out of 5 expressed as a percentage, and Real recall is the mean of those across datasets that actually have a score — a dataset nobody has scored is left out rather than counted as zero. These roll-ups exclude the Other topic, so a dataset’s figure here can differ from the score on the Memory Coverage page itself; The score explains why. Its header meta line reads LLM-as-judge, or LLM-as-judge · loading, · couldn’t load, or · not scored yet. At most four datasets are listed; with more, a line reads Showing 4 of 11 datasets. Real recall averages every dataset that has a score. — so the headline covers more datasets than the rows do. Click a dataset row to open Memory Coverage scoped to it, or use the footer’s View analysis → for the full page and Upload data for the same file picker as the Company Dataset card. The panel says which of three situations you are in: with no datasets at all, Add data to see coverage by dataset; with datasets but no scores, Not scored yet. Run an analysis to see coverage per dataset.; and on a failed fetch, Couldn’t load coverage. with a retry in place rather than sending you to the other page to find out.

​

Activity

The Activity panel is a glance over the same rows as the full Activity log, newest first, with six columns: Timestamp, Action, Status, Duration, User, and Cost (est.). Its header summarizes the feed in at most three facts — operation count, failures, runs in flight, and total estimated cost, for example 1,284 operations · 3 failed · $0.4210. The glance lists the newest eight top-level operations, and clicking a row opens that run’s session in Sessions. Under the table, View full log → opens the Activity page, and a quiet line on the right says what the glance is not showing — how many more rows exist, how many nested steps are folded in, and how many rows the default filters dropped. When every loaded row measured zero tokens or is still queued, the panel says so outright rather than looking idle. While the feed loads the panel header reads loading…; if it fails the header reads couldn’t load in red and the table is replaced by an explanation rather than an empty state. With no activity at all it reads No activity recorded yet. — Rows appear here as soon as an agent reads from or writes to your memory — with a Connect an agent action.

​

Credit banners

A single red banner appears between the greeting and the Get started strip when your workspace credit balance falls below $5**: **Your workspace credit balance is$0.42. Agent requests may fail. At a balance of zero or less the wording hardens to Agent requests will fail. Workspace owners get a Top up credits → link to Billing; everyone else sees Ask the workspace owner to top up. The banner can be dismissed with the ✕. A run that actually fails for want of credits is reported separately from this banner — see When credits run out.

​

While the workspace is unavailable

The Overview stands in for the workspace itself when the workspace is not ready:

• Waking — a workspace that scaled to zero shows a Waking screen instead of the panels. See Workspace sleep and wake.
• Unreachable — when the pod cannot be reached, an amber card reads We’re having trouble reaching your workspace (or didn’t wake up after a wake attempt), with a retry and the suggestion to sign out and back in.
• Partial telemetry — if workspace activity fails to load, a red line under the panels reads Couldn’t load workspace activity, so the panels above may be incomplete or empty. We’ll keep trying in the background. If only sessions fail, an amber line says that activity from before your workspace started recording operations is missing from these panels. After repeated failed polls a notification also appears once per episode — Workspace is having trouble responding — and a faint refreshing telemetry… line shows while a refetch is in flight. The panels keep their last-known figures rather than blanking.

​

Sidebar

The sidebar is shared by every page in the app and can be collapsed to an icon-only rail on desktop. Hover over the sidebar and click the chevron handle on its right edge (Collapse sidebar / Expand sidebar) to toggle it. The sidebar’s three sections are DATA, EXPLORE, and CONNECT, in that order. Collapsed, the nav labels become icons with hover tooltips, each section heading becomes a thin divider rule, and the Billing / Pricing button becomes a card icon. The choice is stored in a cookie for a year and read on the server, so a collapsed sidebar renders collapsed on the first paint after a reload instead of animating shut. Collapsing applies to desktop only — on mobile the sidebar remains a full-width drawer with labels, opened from the hamburger button.

​

Help menu

A ? button in the top bar, on every page, opens a help menu:

​

Give feedback

The sidebar footer holds three controls on every page, in order: Give feedback, Book a call (opens a Calendly booking page in a new tab), and Billing / Pricing. The whole footer is cloud-only — it is not part of the local, open-source UI. Clicking Give feedback opens a short form; submitting sends your message straight to the Cognee team, tagged with your current workspace and the page you were on for context. You must be signed in to send feedback.

​

Pulse survey

Cognee also asks for feedback on its own once, through a small Quick question card in the bottom-right corner of the app. It is not a modal — the rest of the page stays usable — and you can close it with the ✕ button or the Esc key (Escape is ignored while you are typing an answer). The card is offered at most once per user, and only once your account has some tenure behind it: it is at least 15 days old, or it predates onboarding entirely. Creating a dataset is only an occasion to run that check sooner — it is never a way around it, so a brand-new signup is not asked on day one. The card appears on whichever page you happen to be on. Like the credit banners above, the pulse survey appears only in Cognee Cloud — it is not part of the local, open-source UI.