Knowledge

The hanzo knowledge commands.

Also for this capability: API · CLI · MCP · SDKs

Your team's wiki and your agents' memory, searchable by meaning.

API reference →

hanzo knowledge connectors list

Every command takes --json for the raw response and --help for its own flags. Sign in once with hanzo auth login; the commands below use that session, and the org they act in is the one it carries.

CommandWhat it does
hanzo knowledge graphReturns the caller org's knowledge as a node/edge graph shaped for a force-directed renderer: pages, memories and synced sources as nodes; the page parent tree, the wikilinks between pages, and each source's connector provenance as edges.
hanzo knowledge importImport an Obsidian, Notion, Roam or Evernote export into the org's knowledge base
hanzo knowledge reindexRebuilds the caller org's retrieval from its documents: every passage is removed, and every page, memory and source is cut into passages and embedded again with the configured model; the lexical index is reconciled to the same documents.
hanzo knowledge searchRuns a hybrid search over the caller org's own knowledge — its wiki pages, its agent memories and everything its connectors have synced.

Connectors

CommandWhat it does
hanzo knowledge connectors callback <provider>Finishes an OAuth connection: it exchanges the provider's code for a token, seals that token in KMS, and records the connection.
hanzo knowledge connectors catalogReturns the ONE catalog of everything a caller can connect: every first-party connector and every long-tail one, in a single list sorted by provider.
hanzo knowledge connectors connect <provider>Returns the provider authorize URL the console opens to connect this org's account.
hanzo knowledge connectors listReturns every supported knowledge connector with THIS org's connection state and the REAL number of documents each has ingested into the org's store.
hanzo knowledge connectors rm <provider>Revokes a connection: it tombstones the stored credential so a later sync cannot reuse it, removes this provider's passages from the org's store, and marks the connector disconnected.
hanzo knowledge connectors sync <provider>Pulls the provider's documents for the caller's org and files them as knowledge sources, which the store's own hook then indexes — so a synced document is retrievable exactly like a hand-written page.
Was this page useful?