@rafiqui987/markode 0.3.1 → 0.4.1

package/README.md

@@ -369,6 +369,8 @@ missing description, a name that doesn't match its folder…).
 markode                     # set up the project if needed, then open the editor
 markode serve               # open the editor without the setup
 markode serve --port 5000 --no-open
+markode url [<doc.md>]      # the editor's link (or a doc's); starts it in the background if needed
+markode stop                # stop the editor started in the background
 markode init                # run the setup again: only adds modules (your defaults, if saved)
 markode init --profile full # no questions: viewer, agent or full
 markode init --yes          # no questions: your defaults, or viewer + AI agent
@@ -380,20 +382,27 @@ markode features            # which modules are on, with what each one does
 markode features live off   # turn a module on or off (same as Settings → Features)
 markode translate           # choose languages to review the docs in (also: markode --translate)
 markode link                # only CLAUDE.md or only AGENTS.md? add the other one, pointing to it
+markode update              # install the latest version now (see below)
 markode -v                  # version
 ```
 
 To keep it installed: `npm install -g @rafiqui987/markode` (or `pnpm add -g @rafiqui987/markode`).
 Installing it also makes the Claude Code hooks faster than running through `npx`.
 
+**A new version right away.** pnpm (and npm with `min-release-age`) wait a day before installing a
+version just published. `markode update` asks the npm registry for the latest version and installs it
+now, with the same package manager that installed markode (`--pnpm` or `--npm` to choose);
+`markode update --check` only says whether there is one.
+
 ## For AI agents
 
 The AI agent module installs the `markode` skill where the project's agents read skills
 (`.claude/skills/` for Claude Code, `.agents/skills/` for Codex, Copilot, Gemini and others). It tells
-the agent how to write Markdown that markode presents well, and gives it two commands:
+the agent how to write Markdown that markode presents well, and gives it three commands:
 
 | Command | What the agent does | When |
 |---|---|---|
+| `/markode` | Starts the editor in the background if it isn't running and gives you its link (`markode url`) | When you want to open markode |
 | `/markode sync` | Keeps the docs consistent: applies answered proposals, ticks phases from their tasks, checks the projects table and broken links (`markode check`) | Start and end of a session, after editing docs |
 | `/markode translate` | Translates what is behind; asks before changing any source file | Only when you ask |
 
@@ -404,6 +413,11 @@ enough. In the main doc it writes only between its markers:
 - `markode:workflow`: how the project plans its work (the markode method, OpenSpec or Spec Kit);
 - `markode:proposals`: how the agent writes proposals and answers comments.
 
+**Links to docs.** When the agent points you to a doc (a proposal it wrote, a doc it changed), it gives
+a link you can click in the terminal: `http://localhost:4319/open?path=docs/proposals/003-auth.md`. The
+markode tab you already have open shows that doc, and the tab the click opened closes itself, so you
+keep a single markode tab. With no markode tab open, the link opens the editor on that doc.
+
 When the agent writes a proposal, it runs `markode wait <proposal>` in the background: it waits
 without using tokens until you press "Done, send my answer", then hands the agent your choices, open
 questions and comments. If no session was open, the next one applies the answer first.
@@ -426,6 +440,7 @@ module, in projects that use Claude Code, markode adds three hooks to `.claude/s
 Without a global install the command is `npx -y --prefer-offline @rafiqui987/markode`.
 
 ```bash
+markode url [<doc.md>]                                # link to the editor or a doc (starts it if needed)
 markode check [--json]                                # what /markode sync fixes
 markode wait <proposal.md>                            # wait for the user's answer, then print it
 markode changes [--json]                              # the user's edits and comments since last told