AI tools
Markko can open every Markdown file your coding agent writes, so you read the formatted result. This is optional; the app works without it.
Claude Code: the plugin
In Claude Code (version 2.1.224 or later), run:
/plugin marketplace add https://markko.app/claude/marketplace.json
/plugin install markko@markkoThe plugin opens each Markdown file that Claude writes or edits in Markko, in the background. It adds these commands:
/markko:comments [file.md]: Claude reads your open Markko comments on the file, works on them, and answers each one in the comments file, so the answer shows in Markko./markko:offand/markko:on: stop and start opening the files./markko:status: shows if auto-open is on and if Markko is installed.
The plugin is a zip file on this website: marketplace.json. To remove it, run /plugin uninstall markko@markko.
Cursor, Windsurf and Claude Code without the plugin: the setup script
curl -fsSL https://markko.app/setup | sh
# see every change first
curl -fsSL https://markko.app/setup | sh -s -- --dry-run
# remove the hooks again
curl -fsSL https://markko.app/setup | sh -s -- --uninstallRead it first if you like: markko.app/setup is the whole script. It adds one hook per tool. After the agent writes a .md, .markdown or .mdown file, the hook runs open -g -a Markko on it.
- It changes only these files, and only for the tools you have installed:
~/.claude/settings.json(Claude Code; skipped when the Markko plugin is installed),~/.cursor/hooks.json(Cursor) and~/.codeium/windsurf/hooks.json(Windsurf, now Devin Desktop). - Before a change, it saves a copy next to the file:
<file>.markko-backup-<date>. - It never uses
sudo. When you run it again, it changes nothing. --dry-runshows the changes and makes none.--uninstallremoves the hooks again; your other settings stay.- If Markko is not installed yet, it says so. The hooks do nothing until Markko is installed.
Start a new session in each tool after the setup, so that it loads the hook.
By hand: the hooks
To do it yourself, add the hook to the tool's file. Merge it with what is already there.
Claude Code: ~/.claude/settings.json
{
"hooks": {
"PostToolUse": [
{
"matcher": "Write|Edit|MultiEdit",
"hooks": [
{
"type": "command",
"command": "f=$(plutil -extract tool_input.file_path raw -o - - 2>/dev/null) || exit 0; case \"$f\" in *.md|*.markdown|*.mdown) open -g -a Markko \"$f\" >/dev/null 2>&1 ;; esac; exit 0 # markko-setup"
}
]
}
]
}
}Cursor: ~/.cursor/hooks.json
{
"version": 1,
"hooks": {
"afterFileEdit": [
{
"command": "f=$(plutil -extract file_path raw -o - - 2>/dev/null) || exit 0; case \"$f\" in *.md|*.markdown|*.mdown) open -g -a Markko \"$f\" >/dev/null 2>&1 ;; esac; exit 0 # markko-setup"
}
]
}
}Windsurf: ~/.codeium/windsurf/hooks.json
{
"hooks": {
"post_write_code": [
{
"command": "f=$(plutil -extract tool_info.file_path raw -o - - 2>/dev/null) || exit 0; case \"$f\" in *.md|*.markdown|*.mdown) open -g -a Markko \"$f\" >/dev/null 2>&1 ;; esac; exit 0 # markko-setup"
}
]
}
}Other editors
VS Code, JetBrains IDEs and other editors have no hook that runs after their assistant writes a file. Open a file in Markko from the terminal with open -a Markko file.md, or with the URL markko://open?path=/full/path/file.md.
The comments file format for your own scripts: Comments file format.