Kinic Wiki is a canister-backed wiki and memory interface for coding agents.
It stores durable wiki nodes in an Internet Computer canister and exposes them through a browser UI, kinic-vfs-cli, and agent-readable APIs.
Vector databases are useful for retrieving nearby text fragments from large corpora. Agent memory has a different shape. Agents need stable places for current decisions, source evidence, open questions, operating procedures, and relationships between notes.
Kinic Wiki uses a canister-backed file system as that memory layer. Organized knowledge lives under /Wiki/...; raw evidence lives under /Sources/raw/.... Agents can search it, follow paths and links, inspect recent changes, and update notes with etag guarded writes.
For many medium-sized agent workflows, structured file-system search is often more useful than embedding-only retrieval. A result is not just a similar chunk; it is a named, linked, updateable knowledge node.
- Browser access for public and private wiki databases
- Path-based reads, writes, search, recent nodes, and link graph inspection
etagguarded edits for safer agent and operator workflows- Skill Registry packages for discovering, evaluating, and improving agent skills
- Read-only Agent Memory API methods for direct canister clients
The public browser entry point is:
The official Kinic Wiki database is:
https://wiki.kinic.xyz/db_kva4v2twg6jv/Wiki?read=anonymous
Database ID:
db_kva4v2twg6jv
The canonical CLI guide is:
npm install -g kinic-vfs-cli
kinic-vfs-cli --helpThe npm package downloads a release binary and verifies its SHA-256 checksum. Current npm binaries support macOS arm64 and Linux x64.
Most commands need a database id. Pass it per command, link it once for a workspace, or set VFS_DATABASE_ID.
kinic-vfs-cli --database-id <database-id> status --json
kinic-vfs-cli database link <database-id>
VFS_DATABASE_ID=<database-id> kinic-vfs-cli search-remote "query text" --prefix /Wiki --jsonRead exact nodes when a path is known:
kinic-vfs-cli read-node --path /Wiki/page.md --json
kinic-vfs-cli read-node-context --path /Wiki/page.md --jsonFor writes, read first, keep the returned etag, then mutate with an expected etag:
kinic-vfs-cli edit-node --path /Wiki/page.md --old-text before --new-text after --expected-etag <etag> --jsonPublic databases can be read anonymously only when the database grants reader access to the anonymous principal. Writes, database grants, archive operations, and private Skill Registry writes require an authenticated identity.
Skill Registry commands use the same CLI:
kinic-vfs-cli skill find "contract review" --json
kinic-vfs-cli skill inspect legal-review --json
kinic-vfs-cli skill record-run legal-review --task "review contract" --outcome success --notes-file ./notes.md --jsonAgents should discover relevant skills, inspect the package, use the instructions, then record run evidence when the workflow produces useful feedback.
- Browser: browse, search, edit, and manage database access
- CLI: scripted database operations and Skill Registry workflows
- Chrome extension: ChatGPT export and active-tab URL ingest
- Agent Memory API: direct read-only canister queries such as
memory_manifest,query_context, andsource_evidence - Agent Tool Calling: embedded OpenAI-compatible and Anthropic-compatible tool schemas
The Chrome extension connects browser work to Kinic Wiki. It can save recent ChatGPT conversations as raw sources and queue active web pages for URL ingest. The browser is the capture surface, the Wiki is the structured memory, and the CLI is the operator automation layer.
Developer and operator guides:
- CLI setup and database operations: docs/CLI.md
- Skill Registry workflows: docs/SKILL_REGISTRY.md
- Canister Agent Memory API: docs/AGENT_MEMORY_API.md
- Shared Rust library tool calling: docs/AGENT_TOOL_CALLING.md
- VFS validation and benchmarks: docs/validation/VFS_VALIDATION_PLAN.md
- Public CLI guide: https://wiki.kinic.xyz/cli