KiwiFS versions every write so you never lose knowledge. Choose the strategy that fits your use case.Documentation Index
Fetch the complete documentation index at: https://docs.kiwifs.com/llms.txt
Use this file to discover all available pages before exploring further.
Strategies
Configure via CLI flag or.kiwi/config.toml:
git (default)
Every write creates a real git commit. You get fullgit log, git blame, git diff, and git revert for free. The X-Actor header becomes the commit author.
cow (copy-on-write)
Lighter-weight versioning that stores snapshots without a real git repo. Useful when you want rollback capability but don’t need the full git workflow.none
No versioning at all. Writes overwrite files in place. Use this for ephemeral or scratch knowledge bases. Best for: development, temporary data, CI pipelines.Async batching
To reduce git overhead under high write volume, KiwiFS batches commits:Optimistic locking
The versioning system powers optimistic concurrency control via ETags. When you read a file, the response includes anETag header containing the git blob SHA.
409 Conflict response.
API endpoints
| Endpoint | Method | Description |
|---|---|---|
/api/kiwi/versions | GET | Version history for a file |
/api/kiwi/version | GET | Read a specific version |
/api/kiwi/diff | GET | Unified diff between two versions |
/api/kiwi/blame | GET | Per-line git blame |
/api/kiwi/changes | GET | List recent changes across the knowledge base |