Plan, document, design and more.
A visual reply to your verbose agent.
claude plugin marketplace add andreiverdes/bluedocclaude plugin install bluedoc@bluedoccodex plugin marketplace add andreiverdes/bluedoccodex plugin add bluedoc@bluedocpi install git:github.com/andreiverdes/bluedocomp plugin marketplace add andreiverdes/bluedocomp plugin install bluedoc@bluedoccopilot plugin install andreiverdes/bluedocgit clone https://github.com/andreiverdes/bluedoc.gitagy plugin install bluedoc/antigravitynpx skills add andreiverdes/bluedoc
bluedoc turns what your agent writes into pages: plans, docs, reviews, designs and decks. You answer on the page; it reads every answer.
Inside your agent.
Ask for a doc the way you always do. Pick a type and see the page it opens.
Installs as a plugin in Claude Code, Codex, pi, omp, Copilot CLI, Antigravity CLI.
Install once.
Then answer on a page.

Install once.
One command adds the skill to your agent. It needs Python 3.9 or later and nothing to host.

Ask in plain words.
Ask for a plan, a review, a design or a deck, as you would anyway. It opens as a page on the local server.

Answer on the page.
Pin a comment on a part, pick an answer, approve. The agent reads every answer and revises.
Plan mode too. The plan-mode hook opens the plan as a page, and the agent waits for Approve before it writes code. Settings turns it off.
One JSON file per doc. The server renders the page from it on every request, so an edit and a reload is the whole build.
A chat asks you to reply in prose.
Agents answer in walls of text and wait for a reply in prose. A bluedoc page asks you the questions and keeps your answers.
A chat reply
Prose in, prose outWhat you do In a chat Point at one part Quote it back in prose Choose between options Type “go with option 2” See what changed Reread the whole reply Sign off Say “looks good” Keep your answers Scrolled away in the transcript Pass it on Paste the reply into a message A bluedoc page
Point, pick, approveWhat you do On a bluedoc page Point at one part Pin a comment on it Choose between options Pick an answer; the recommendation is starred See what changed Compare two revisions, word by word Sign off Approve the current revision Keep your answers Kept in ~/.bluedoc/state.db Pass it on Share a view-only bluedoc.ai link
- Doc types
- 8
- Docs, plans, reviews, designs, decks, sites, store listings and more.
- Agent plugins
- 6
- Claude Code, Codex, pi, omp, Copilot CLI, Antigravity CLI. Any other through the skills CLI.
- JSON file per doc
- 1
- The server renders the page from it; no HTML to keep in sync.
- Accounts
- 0
- No bluedoc account and no hosted service: it runs on 127.0.0.1, MIT.
Counted from the lists on this site, so they stay true when a type or an agent is added. Agent plugins: Claude Code, Codex, pi, omp, Copilot CLI, Antigravity CLI; any other agent installs through the skills CLI.
Built for answering, not just reading.
Three things you do on every page, and two you never have to think about.
Comments that become conversations
Pin a comment on an element, box a region, select a passage or draw with the pen, and attach a file when words aren’t enough. Each comment is a thread the agent replies in, its replies signed with its model’s name.
One answer card per question
Each answer explains itself in a line, and More details opens the agent’s reasoning. Pick one, or several where a question allows, write your own under Other, or ask it to Tell me more. Each list’s Accept recommended takes every starred answer.
Revisions you can compare
Every build is a revision. Changes from N, on each row of the Revisions panel, marks new, changed and removed parts in place, word by word.
All about revisions
Local
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. A doc leaves only when you press Share.
- Address
- 127.0.0.1
- Your answers
- state.db
- Leaves on
- Share
Approved · rev 1
Approve, and the agent proceeds
Plans, designs and websites wait for approval on the current revision. Approve and Request changes open one send dialog: what goes, a note, then the send key.
- Waits for
- Approve
- Sends back
- Request changes
- Each build
- a revision
Questions, answered.
Yes. bluedoc is open source under the MIT licence. There is no account, no subscription and no hosted service.
Claude Code, Codex, Copilot CLI, Antigravity CLI, pi and omp install it as a plugin, with a plan-mode hook and /bluedoc-* commands. 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.
On your machine. Ticks, picks, comments and replies live in ~/.bluedoc/state.db, a SQLite file the local server owns, never in the repo; the Settings page keeps its switches in ~/.bluedoc/settings.json. Only a browser that opened a link from the server can save. A doc leaves only when you press Share.
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 Share, importing GitHub review threads, or diffing a PR whose repo isn’t checked out calls gh.
Yes. The app bar’s ⋮ → Export saves the revision you’re viewing as an HTML file that opens without the server, a PDF, or Markdown. Decks and store listings have their own Export to…: decks as PDF, store listings as a fastlane ZIP, a plain-folders ZIP, a PDF or HTML.
Yes. Share puts the doc’s current revision in a secret gist on your own GitHub account, through gh, and copies a bluedoc.ai/g/ link that opens in any browser with nothing to install. The page there is view-only: the reader reads it, downloads it, or makes a copy in their own bluedoc. Update sends a new revision to the same link; Stop sharing deletes the gist. Anyone with the link can read it, so check the doc first.
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.
Answer your agent
on a page.
Pick your agent. Each one installs the same skill from the GitHub repository.
claude plugin marketplace add andreiverdes/bluedocclaude plugin install bluedoc@bluedocInside a session the same commands are /plugin marketplace add andreiverdes/bluedoc and /plugin install bluedoc@bluedoc. Start a new session to load the skill.
codex plugin marketplace add andreiverdes/bluedoccodex plugin add bluedoc@bluedocRestart Codex. Mention the skill with $bluedoc or let Codex pick it from your request. Plan mode (/plan) opens the plan as a page; the README has the sandbox lines that skip the approval prompts.
pi install git:github.com/andreiverdes/bluedocRestart pi. /bluedoc-plan-mode turns on plan mode, and the plan opens as a page for your approval.
omp plugin marketplace add andreiverdes/bluedocomp plugin install bluedoc@bluedocRun /reload-plugins in an open session, or start a new one. omp’s plan reviews open as pages: Approve runs the plan, Request changes refines it.
copilot plugin install andreiverdes/bluedocStart a new session. When Copilot leaves plan mode, its plan opens as a page and waits for your approval.
git clone https://github.com/andreiverdes/bluedoc.gitagy plugin install bluedoc/antigravityRestart agy. In plan mode (agy --mode plan or /plan), the implementation plan opens as a page for your approval.
npx skills add andreiverdes/bluedocFor any other agent that reads skills. Or clone the repository and link skills/bluedoc into your agent’s skills folder.
- Python 3.9 or later on PATH
- git, for code reviews
- gh, only for GitHub review threads and Share















