Markdowns
7 commands · plm markdowns
Markdown files on the dashboard's Tools tab, driven like doodles: create, replace, read, live.
A Markdown file on the dashboard's Tools tab is a real artifact (the body lives in object storage, gzipped, with a metadata row) that agents and humans share: an agent writes it from the terminal, the web renders it with preview and source views, and edits stream live to whoever is watching. Markdown files carry the written thinking: specs, plans, drafts, all previewable on the Tools tab and pipeable in the terminal.
Step 1 of 3
Create it from anywhere
Inline content, a file path, or a pipe: three ways in. The file becomes active, so the verbs below can omit the id.
plm md · new$ cat draft.md | plm md new --name "pitch draft" --stdin✓ created markdown "pitch draft" · now activemd_8e02b1c4d7full form · plm md new [--name N] [--content "…" | --file <path|-> | --stdin]
Step 2 of 3
Read it back raw
The body comes back exactly as stored: pipe it to a linter, diff it against a local file, or feed it to an agent. Storage, not presentation.
plm md show$ plm md showfull form · plm md show [<md_…>]
Step 3 of 3
Replace, and the browser follows
set swaps the whole body in one write. Anyone with the file open on the Tools tab sees the preview update live, the same follow-along loop doodles have.
plm md · set$ plm md set --file draft.md✓ saved md_8e02b1c4d7md_8e02b1c4d7full form · plm md set [<md_…>] --content "…" | --file <path|-> | --stdin
Also in this chapter
Set the active file.
Your Markdown files: id and name.
Rename the file.
Delete the file. Alias: delete.
- These files are user-scoped and live on the dashboard's Tools tab; works from any directory, no linked repo.
- Active file: after new or use, omit the id; an explicit md_… first argument overrides (.plmhub/state.json).
- Add --as <label> to mutating verbs to name the agent in the live-edit bar a watcher sees.
- Alias: plm markdown.