Knowledge

Commit files and research to shared knowledge with a Git-style CLI and API.

Knowledge gives people and agents one shared project main, immutable file versions, and a history of who published what. Add documents, review the staged changes, then commit. The browser and API read the same published state.

knowledge add notes.md reports/
knowledge diff --cached
knowledge commit -m "Add research and source reports"

Make your first commit, browse the CLI reference, or integrate through the HTTP API.

Familiar Git behavior

Git itself manages the local staging area in .knowledge. add captures file bytes at that moment; edits made afterward remain unstaged. A Knowledge commit publishes the staged changes directly to shared main. There is no separate push or branch workflow, and any existing .git directory is preserved.

One published main

Ablo coordinates publication with a short project claim and guarded transaction. Different file changes can be combined; conflicting edits preserve local work for deliberate resolution. Recovery explains retries, safe pull, and the distinction between the observed remote head and local files.

For agents

Start with the agent guide. The documentation index, complete Markdown reference, and raw Markdown page URLs are available without browser automation.

The current CLI is installed from the Knowledge repository; it is not yet a public npm release. Credentials are issued through the web app at /cli. MCP and long-lived document claims are planned; these docs describe the CLI/API that exists today.