Local-first documents for people and agents.

A workspace for the plans, research and decisions behind your software. You write in a browser; your coding agent reads and edits the same documents over MCP. Everything is stored on your computer, and a hub syncs it to the people you share with.

Why Uberblick Install in four commands

127.0.0.1:7777 · Uberblick product

Delivery report

Edited 2 hours agorev 1f3a

Seven issues merged this week without a person stepping in. Two needed a second review round; both were retry-limit questions the preparer could have settled from the decision record.

Line chart · deliveries6 records

The docs folder is where context goes to die.

Every team keeps the reasoning behind its code somewhere: a Markdown folder in the repo, a Notion space, a few notebooks. The folder goes stale because nobody reads it. The wiki is far from the code and farther from the agents. The notebook is one person's.

Now most teams also have agents working in the same codebase, and they need the same context: what was decided, why, and what the numbers say. They don't need it in a chat window. They need it in a place they can search, read and edit, next to the people who wrote it.

Uberblick is that place. One workspace of documents, on your computer, built MCP first: agents write most of it, and you review and adjust in the browser. Comments sit beside the text they are about. Decisions are records, not paragraphs. Numbers live in the document that explains them.

A document can hold more than prose.

The Markdown you already write, plus the blocks that never survive in a README. Data tables and line charts read records stored inside the document, so when an agent updates the records, the chart updates with them.

Code

$ ub openEditor at 127.0.0.1$

Terminal demo

Charts

Data table

Decision

Embeds

Wireframes

Why not use Notion, Obsidian or Jupyter?

Use them for what they are best at: Notion for company-wide and non-engineering content, Obsidian for a personal knowledge base, Jupyter for reproducible analysis. Uberblick takes one idea from each and aims them at a small team of people and agents working on one codebase. Which tool fits your team? has the full comparison.

What teams use it for.

These are the jobs we built it around, and the ones we use it for ourselves. Each has its own page.

Product intent that agents read before they buildPin the documents that say what the product should do. An agent loop reads them before it prepares, implements or reviews an issue. This is how Uberblick itself is built. Decisions that stay decidedRecord the answer once, with the reason and the issues it affects. The next person, or the next agent, finds it before reopening the question. Reports with the numbers insideA daily delivery report writes its records into a document. The chart on the page is the data, not a screenshot of it. Research that doesn't get lost in chatAn agent's findings land as a document in the workspace, linked from the plan, with your comments beside the parts you disagree with.

A decision looks like this.

From our own product workspace. The answer is the first thing on the page; the reason and the links follow. When the question comes up again, a new record supersedes this one on the same topic.

Decision · decided 10 October 2026Uberblick product workspace

Where does the web UI use monospace?

Only for text a person would paste somewhere: code, terminal output and ids in Settings. Everything else is set in the UI face.

Mono reads as machine output. Used for labels and timestamps it made the chrome look like a debug overlay and competed with real code blocks.

Linksuberblick-2#1551Web UI: typography

Install in four commands.

Homebrew on Apple Silicon macOS or Linux x86_64. No account, no server. The fourth command registers the MCP server with Claude Code; use codex for Codex.

Terminal

$ brew install uberblick-ai/tap/uberblick
$ mkdir uberblick-notes && cd uberblick-notes
$ ub workspace create "My Workspace"
$ ub open
Editor at http://127.0.0.1:… Keep this terminal open.

# Second terminal, same directory
$ ub mcp install claude

To share a workspace, run a hub on a computer the team can reach. It is one Docker release; Run a hub walks through it.

Docs

Install and updateHomebrew, ub update, where your files live. WorkspacesCreate, select and switch; what .uberblick.json decides. The editorBlocks, comments, the sidebar, document data. Agents over MCPInstall for Claude Code or Codex; the 25 tools and what each is for. DecisionsRecords, topics, superseding, linking issues. Run a hubThe Docker release, localhost, Tailscale (recommended) or a public host name; membership and ub auth login. CLI referenceEvery ub command, with examples.