General
The workspace itself: the frame every module renders inside, the search that spans it, and the companion that runs on your own machine.
Some of Dots belongs to no single module: the frame every module renders inside, the search that spans everything you can read, the inbox that tells you what changed, and the process on your own machine that keeps local work flowing in.
None of it is browser-only. The rows a search returns, and the access rules that
decide which rows those are, are the same ones answering the dots command line
and any agent connected over MCP. The browser is one of three front ends over one
data layer.
Key Features
- Five-Region Frame — an authenticated page is assembled from a top bar, a module rail, a module sidebar, the page area, and a right drawer, and only the page area belongs to the module you are looking at.
- Entitled Module Rail — the rail is the application switcher, and it carries only the modules the active workspace holds, so an unentitled module is absent rather than shown disabled.
- One Palette, Three Modes — Mod+K opens universal search, a leading
>turns it into an action list, and Mod+/ opens it as a module launcher. - -Filtered Search — universal search runs over the set of Dotabases you are allowed to read, fusing keyword and vector scoring into one ranked list.
- Stacked Drawer — opening a row pushes a layer onto the drawer and closing it pops back, so you read something without losing the place you read it from.
- Settings As An Overlay — Settings opens over whatever you were doing, and the tab you are on rides in the URL, so a settings screen is a link you can hand to someone else.
- Live Notifications — the bell carries an unread count and opens the inbox as a drawer layer; one event stream drives the count and the toasts alike.
- Desktop Companion — a supervised local process watches your bound folders and tails your consented coding-agent conversations, pushing both to your deployed API.
Get Started
- App Shell — the five regions, the Settings tabs, and the notification inbox in detail.
- Search Your Workspace — the palette's scope and filter bands, jumping straight to a row by its id, and the flags that mirror each band on the terminal.
- Run The Companion — start, inspect, and stop the companion, and decide whether it starts when you sign in to this machine.
Resources
- Quickstart — bring up on the posture you pick and get through first run.
- CLI Overview — the
dotscommand surface, and how a single invocation resolves its instance, its identity, and its company. - Connect An Agent Via MCP — register the MCP server with Claude Code, Claude Desktop, or Cursor, and pick the credential it runs under.
Get Started
- App ShellThe frame every module renders inside: the five regions of an authenticated page, how workspace scoping reaches the routes, the command palette's three modes, the Settings overlay, and notifications.
- Search Your WorkspaceFind anything you can read across every Dotabase: open the command palette, narrow with scope and lens, jump straight to a row by its id, and run the same search from the terminal.
- Run The CompanionStart, inspect, stop, and supervise the Dots companion, including its durable sign-in startup registration.
- Conversation Insights DashboardThe Conversations Dotabase now seeds a thirteen-widget Conversation Insights dashboard covering conversation volume, token spend, cache efficiency, and activity over time.
- Cursor Conversation ImportCursor joins Claude Code and Codex as an importable coding agent, with per-folder consent that fails closed and metadata-only detection before you approve.
- First-run Setup AssistantA first-run Setup Assistant now walks a fresh install through nine fixed steps — license, workspace provisioning, agent detection, a guided plugin install, the concierge run, and three reveals.