Getting started
Blenau turns your GitHub repos into a shared knowledge brain that humans and AI agents read and write through one interface. This page is the 5-minute overview; the following pages go deep on each surface.
1. Sign in
Section titled “1. Sign in”Open blenau.com and sign in. Authentication is handled by Prysm:ID (SSO); your workspace (tenant) is created on first login.
2. Connect a GitHub repo
Section titled “2. Connect a GitHub repo”From the dashboard, install the Blenau GitHub App on the repo(s) you want to use as knowledge. Blenau holds the GitHub access (via the App installation) — you don’t hand it any personal token.
- A workspace can connect several repos. Each repo has a
path_prefix. - A document path like
emboux/setup/odoo-sync.mdroutes to the repo whose prefix matches (emboux/). A path with no matching prefix falls back to the repo connected at the empty prefix. - When in doubt about routing, list your repos first (the MCP
list_repostool /blenau repos).
3. Choose how you’ll work
Section titled “3. Choose how you’ll work”| You are… | Use |
|---|---|
| An AI agent (Claude, etc.) | The MCP server |
| A human at a terminal | The CLI |
| A human in the browser | The dashboard at blenau.com |
4. The golden rule
Section titled “4. The golden rule”Blenau stores synthesized knowledge, and search quality depends on not fragmenting it. Whether you’re an agent or a person:
Search first, write later. Before creating a new document, search for the topic. If a doc already covers it, edit a section instead of creating a duplicate.
Mental model
Section titled “Mental model”- Documents map 1:1 to Markdown files in your connected repos.
- Writes commit to GitHub before the database is updated, so a failed commit never leaves a Blenau-only “ghost” doc — GitHub is always the source of truth.
- Every write should carry provenance (where the knowledge came from), so later readers can trace and verify it.