Skip to content
Pixel art of a bay at night: a ringed planet over the water, ships with engine trails, and a city whose rooftop billboard reads “bluedoc”.Pixel art of the same bay by day: a ringed planet in a blue sky, ships, clouds and the city’s “bluedoc” billboard.

Beta · Agent skill · Local · MIT

Point, pick, approve. Your agent does the rest.

bluedoc turns plans, code reviews, architecture docs, UI designs and slide decks into interactive pages. Comment on any element, pick an option, approve. Your agent reads the answers and gets on with it.

InstallView on GitHub
claude plugin marketplace add andreiverdes/bluedoc
claude plugin install bluedoc@bluedoc

One home for every doc

Every doc your agent writes, in one place.

The local server lists each doc with its type, status and revision. Filter by type or status, browse projects in the sidebar, and open a doc to read, comment and decide.

The bluedoc home page in dark mode: the pixel-art banner behind the title and search field, filter chips by type and status, the sidebar of projects and the doc cards.

How it works

One loop, from draft to approved.

The agent writes, you answer on the page, the agent revises. Each round is a revision you can compare with the last.

  1. Agent writes

    One JSON file. The local server renders it as a page; no HTML to keep in sync.

  2. You mark up

    Pin a comment on any element, a selected passage or a box you draw.

  3. You decide

    Pick an option per question. The agent’s recommendation is starred.

  4. Agent revises

    It edits one part at a time and marks the comments it resolved.

  5. You approve

    Approve the current revision; the agent waits for it before it writes code.

Doc types

Seven kinds of page, one way to answer them.

Each type has its own layout and its own decisions. Comments, revisions and approval work the same on all of them.

  • The Acme orders doc: the order path canvas zoomed into the orders-api system, playing step 3 of a flow.

    Docs

    docs

    Architecture pages, walkthroughs, runbooks, setup guides and change proposals.

    • A zoomable blueprint canvas, nested up to 3 levels
    • Animated flows: a request, an event, a data path
    • Checklists whose ticks the local server keeps
  • The Acme saved carts plan: three open questions with the recommended options starred, and Approve plan in the bottom tray.

    Plans

    plan

    A plan you approve or send back before the agent writes code.

    • Steps, files, risks and checks on one page
    • Open questions with the recommendation starred
    • The agent waits for Approve plan
  • The Acme review findings: a finding card under the lines of createOrder.ts it is about, with Fix in PR picked.

    Reviews

    review

    Review findings pinned to their lines from git, one decision per finding.

    • Diffs expanded from git on each render
    • Fix in PR, Ticket or Decline, with a reason
    • GitHub review threads imported as findings
  • The Acme Fit design board: the Today phone screen selected, with its links drawn as right-angle connectors to other screens.

    Designs

    design

    UI screens on a pan-and-zoom board, and app icons.

    • Watch, phone, tablet, desktop and browser frames
    • Screens link to each other; Present follows the taps
    • App icon sheets with PNG export
  • The Acme Fit Q3 launch review deck: five slides stacked in one column, with the Present key in the toolbar.

    Presentations

    presentation

    Slide decks with speaker notes, played in Present.

    • 16:9 HTML slides in deck order
    • ← → to step, N for notes, Esc to leave
  • The Acme Fit site board: the Home mockup at 1440 px with its hero’s A, B and C versions, and the Blog live from the dev server at 390 px with a pin on a post title.

    Websites

    website

    A site’s pages on a board, live from its dev server.

    • Live pages from localhost, hot reload included
    • Comments that name the source file to edit
    • Versions of a section, picked in place
  • The Acme weekly status page for week 41: the TL;DR and the week-over-week numbers table.

    Other

    other

    Status pages, incident reports, inventories, meeting notes and comparisons.

    • A TL;DR, then one section per question
    • A hero stat that sums the page up

Features

Built for answering, not just reading.

A wall of text in a chat asks you to reply in prose. A bluedoc page asks you the questions and keeps your answers.

  • Comments on any element

    Point at an element, select a passage or draw a box. Notes collect as Pending, Open and Resolved.

  • Decision pills, recommendation starred

    Pick one option per question, or press Accept recommended to take every starred option at once.

  • Revisions you can compare

    Every build is a revision. Compare any two: new, changed and removed parts are marked in place, word by word.

  • Approve, and the agent proceeds

    Plans, designs and decks wait for approval on the current revision. Request changes sends them back.

  • Your input stays on your machine

    Ticks, picks and comments live in a local SQLite file the server owns, never in the repo. Screens run sandboxed, with no network.

  • Works with your agent

    Claude Code, Codex, pi and omp install it as a plugin. Any other agent gets it through the skills CLI.

See every feature

JSON in, page out

The agent writes JSON. You get a page.

Agents never write page HTML. The server renders each doc from its JSON on every request, so an edit and a reload is the whole build.

saved-carts.bluedoc.json
{  "title": "Acme Shop: saved carts",  "meta": { "type": "plan", "rev": "1" },  "sections": [{    "title": "Open questions",    "blocks": [{      "type": "checklist",      "id": "decisions",      "items": [{        "id": "retention",        "text": "How long does a saved cart stay?",        "recommend": "d180",        "choices": [          { "id": "d90", "label": "90 days" },          { "id": "d180", "label": "180 days" },          { "id": "forever", "label": "Until deleted" }        ]      }]    }]  }]}
Rendered by the local server
The rendered Acme saved carts plan: the retention question with 90 days, 180 days (starred) and Until deleted as pills.

Install

Pick your agent.

Each one installs the same skill from the GitHub repository.

claude plugin marketplace add andreiverdes/bluedoc
claude plugin install bluedoc@bluedoc

Inside a session the same commands are /plugin marketplace add andreiverdes/bluedoc and /plugin install bluedoc@bluedoc. Start a new session to load the skill.

Needs: Python 3.9 or later on PATH · git, for code reviews · gh, only to import GitHub review threads.

FAQ

Questions, answered.

Is it free?

Yes. bluedoc is open source under the MIT licence. There is no account, no subscription and no hosted service.

Which agents does it work with?

Claude Code, Codex, pi and omp install it as a plugin. Any other agent that reads skills can get it with the skills CLI (npx skills add andreiverdes/bluedoc) or a copy of the skill folder.

Where does my data live?

On your machine. Ticks, picks, comments and replies live in ~/.bluedoc/state.db, a SQLite file the local server owns, never in the repo. Only a browser that opened a link from the server can save.

Does it need an internet connection?

No. The server runs on 127.0.0.1 and serves its fonts, styles and UI kits itself. Design screens run sandboxed with no network. Only importing GitHub review threads, or diffing a PR whose repo isn’t checked out, calls gh.

Can I export a doc as HTML?

Yes. Add -o name.html to the build command and bluedoc writes a standalone HTML file you can send to someone.

What licence is it under?

bluedoc’s own code is MIT. The vendored HorizonUI build is Apache-2.0, and the fonts it ships are SIL OFL 1.1. The repository’s README lists every third-party licence.

Approved · rev 1

Answer your agent on a page.

Install the skill, ask your agent for a plan, and answer it on a page.

Star on GitHubInstall