The liveknowledge command reads and writes a Knowledgebase from a terminal, a script or a coding agent. Its commands mirror the MCP tools, and it can keep a Knowledgebase as a folder of Markdown beside a repository.
Install and Sign In
The CLI is the npm package @liveknowledge/cli and needs Node 22 or later. Run it without installing:
npx @liveknowledge/cli@latest --help
or install it, which gives you the liveknowledge command:
npm install -g @liveknowledge/cli
liveknowledge auth login
auth login signs you in in your browser, once. A script can send an API token instead.
The Commands
Every command takes the Knowledgebase first: its name, the start of its id, or its address. A page is named by its id, or by its title where one page alone has it.
| Command | What it does |
|---|---|
context <kb> | The Always in Context pages as Markdown, your role and scopes, the Review Period. Run it first |
pages <kb> [--under <page>] | The page tree, each page with its id and trust |
search <kb> <words…> [--limit <n>] | Passages that match, with their page, headings and trust (20 at most) |
read <kb> <page> [--heading <h>] | A page as Markdown, then its trust, backlinks and subpages |
new <kb> <title> [<file>] [--parent <page>] | A new page from a Markdown file, or - for what is piped in |
suggest <kb> <page> --reason <r> [--old <text>] --new <text> | A suggested edit for a person to accept. Leave out --old to append. --new-file reads the Markdown from a file |
write <kb> <page> <file> [--append] | Replaces a page's writing, or adds after it. Needs the write scope |
move <kb> <page> [--parent <page> | --top] [--before <page>] | Moves a page and its subpages. Needs the write scope |
gap <kb> <question…> | Records a question the Knowledgebase could not answer |
import <path> [--name <n> | --to <kb> [--into <page>]] [--source markdown|notion] [--dry-run] | A Markdown folder, a .zip or a Notion export into a new or existing Knowledgebase |
export <kb> <dir> | The Knowledgebase as a folder of Markdown |
Add --json to any command for its answer as JSON, or -q for the bare result (ids, or the Markdown alone).
Examples
# What every agent should know first
liveknowledge context Handbook
# Find a passage, then read its page
liveknowledge search Handbook when do we deploy
liveknowledge read Handbook Deploying --heading "When we deploy" -q > section.md
# Suggest a fix for a person to accept
liveknowledge suggest Handbook Deploying --reason "Moved in March" --old "on Tuesdays" --new "on Mondays"
# Add a page under another, from a file
liveknowledge new Handbook Hotfixes hotfixes.md --parent Deploying
# Keep the Knowledgebase beside a repository
liveknowledge export Handbook docs/handbook
liveknowledge import ./docs --name Handbook --dry-run
Import and Export
export <kb> <dir>writes one.mdfile a page, a page's subpages in a folder of its name, links between pages as relative links and pictures underpictures/.export --all --to <dir>backs up every Knowledgebase you can read instead.importreads a Markdown folder or.zip(the default) and a Notion export (--source notion).--dry-runprints the plan and writes nothing. A picture comes across as its caption: import in the app to bring pictures in. A Confluence export is refused: import it in the app. See Import From a Markdown Folder.
Good to Know
writeandmoveneed the write scope, which an Editor allows in AI Knowledge. Without it the command is refused and says to usesuggest.writeis refused on a Verified or Review Due page whatever the scopes. See An Agent Cannot Write.- The CLI's reads are counted under "CLI" in Connected Agents.
liveknowledge --helplists every command, andliveknowledge <command> --helpits flags.
Was this article helpful?
Still need help?
Try Troubleshooting, or tell us what you were trying to do.