Anchorify + Cline

Cline (formerly Claude Dev) runs an agentic Claude loop inside VS Code. Each task produces a conversation that lives in Cline's sidebar — handy in-context, awkward to share. Anchorify gives you a stable URL for the finished transcript with no copy-paste.

Export the active task

Cline → kebab menu (⋯) on the task → Export Task. Pick markdown. You get a cline-task-<id>.md file in your downloads folder.

Publish it:

anchorify ~/Downloads/cline-task-*.md

The CLI prints a URL on stdout. Send that to whoever asked for the transcript.

Auto-publish task exports

Cline stores its history under ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/tasks/<id>/ (macOS) or the equivalent VS Code globalStorage path on your OS. The per-task folder contains a ui_messages.json and a conversation_history.json. To publish the markdown export of any task whose ID you know:

TASK=<task-id>
DIR=~/Library/Application\ Support/Code/User/globalStorage/saoudrizwan.claude-dev/tasks/$TASK
just node -e "/* … render conversation_history.json as md … */" \
  | anchorify - --slug cline-$TASK

(Replace the node -e payload with whichever JSON-to-markdown renderer you prefer — the official Export Task button does this already; this recipe is for power users wiring it into automation.)

Access

Set per-publish via --access restricted|view|comment|suggest, plus --index if you want the share listed publicly. The default is --access comment --no-index: anyone with the link can read (and signed-in users can comment), but the share is hidden from search and /discover. For team-internal transcripts, prefer --access restricted so non-members get a 404 instead of a readable URL. See Access and passwords.

Install

npm i -g anchorify-cli
anchorify login

Then create an API token at https://anchorify.io/dashboard.