Memory wiki

Memory wiki 문서는 OpenClaw 공식 문서(plugins/memory-wiki)를 한국어로 정리한 가이드입니다. memory-wiki: compiled knowledge vault with provenance, claims, dashboards, and bridge mode 명령·설정 키·코드 예시는 공식 문서를 그대로 보존하며, 해석과 절차 안내는 한국어로 제공합니다. 최종 동작은 설치된 CLI 버전과 공식 원문을 확인하세요.

핵심 요약

memory-wiki: compiled knowledge vault with provenance, claims, dashboards, and bridge mode

한국어 가이드 범위: plugins/memory-wiki 경로의 설정·명령·제약·예시를 학습용으로 재구성합니다.

문서 구성

공식 문서의 주요 섹션은 다음과 같습니다.

Vault modes
Vault layout
Open Knowledge Format imports
Structured claims and evidence
Agent-facing entity metadata
Compile pipeline
Dashboards and health reports
Search and retrieval
Agent tools
Prompt and context behavior
구성
Per-agent vaults
Example: QMD + bridge mode
CLI
Obsidian support
Recommended workflow
Related docs

상세 내용

본문

memory-wiki is a bundled plugin that compiles durable knowledge into a navigable wiki: deterministic pages, structured claims with evidence, provenance, dashboards, and machine-readable digests.

주요 항목:

memory_search for one broad recall pass across whatever corpora are configured
wiki_search / wiki_get when you want wiki-specific ranking, provenance, or page-level belief structure
memory_search corpus=all to span both layers in one call, when the active memory plugin supports corpus selection

Layer	Owns
Active memory plugin	Recall, semantic search, promotion, dreaming, memory runtime
`memory-wiki`	Compiled wiki pages, provenance-rich syntheses, dashboards, wiki search/get/apply

openclaw plugins enable memory-wiki
openclaw gateway restart

Vault modes

Vault mode and vault scope are separate choices:

주요 항목:

isolated (default): own vault, own sources, no dependency on the active memory plugin. Use this for a self-contained curated knowledge store.
bridge: reads public memory artifacts and event logs from the active memory plugin through public plugin SDK seams. Use this to compile the memory plugin's exported artifacts without reaching into private plugin internals.
unsafe-local: explicit same-machine escape hatch for local private paths. Intentionally experimental and non-portable; use only when you understand the trust boundary and specifically need local filesystem access bridge mode cannot provide.
vaultMode chooses where wiki inputs come from.
vault.scope chooses whether all agents use one vault or each agent gets a child vault.
exported memory artifacts (indexMemoryRoot)
daily notes (indexDailyNotes)
dream reports (indexDreamReports)
memory event logs (followMemoryEvents)

Vault layout

Managed content stays inside generated blocks; human note blocks are preserved across regeneration.

주요 항목:

sources/: imported raw material and bridge/unsafe-local-backed pages
entities/: durable things, people, systems, projects, objects
concepts/: ideas, abstractions, patterns, policies (also the landing spot for OKF imports)
syntheses/: compiled summaries and maintained rollups
reports/: generated dashboards

<vault>/
  AGENTS.md
  WIKI.md
  index.md
  inbox.md
  entities/
  concepts/
  syntheses/
  sources/
  reports/
  _attachments/
  _views/
  .openclaw-wiki/

Open Knowledge Format imports

Import an unpacked Open Knowledge Format bundle into wiki concept pages. Good fit when a data catalog, documentation crawler, or enrichment agent already produces OKF: keep OKF as the portable exchange artifact, let memory-wiki turn it into OpenClaw-native concept pages and compiled digests.

주요 항목:

non-reserved .md files are concept documents
each imported concept requires a non-empty type frontmatter field; missing type produces a missing-type warning and the file is skipped
unknown type values are accepted as generic concepts
index.md and log.md are reserved and never imported as concepts
broken or external markdown links are left unchanged

openclaw wiki okf import ./bundles/ga4

Structured claims and evidence

Pages carry structured claims frontmatter, not just freeform text. Each claim can include id, text, status, confidence, evidence[], and updatedAt. Each evidence entry can include kind, sourceId, path, lines, weight, confidence, privacyTier, note, and updatedAt.

Agent-facing entity metadata

Entity pages carry generic routing metadata usable for people, teams, systems, projects, or any other entity type:

주요 항목:

entityType: for example person, team, system, project
canonicalId: stable identity key across aliases and imports
aliases: names, handles, or labels that resolve to the same page
privacyTier: free-form string; public is treated as no-review, any other value (for example local-private, sensitive, confirm-before-use) is flagged in reports/privacy-review.md
bestUsedFor / notEnoughFor: compact routing hints
lastRefreshedAt: source-refresh timestamp, separate from page edit time
personCard: optional person-specific routing card (handles, socials, emails, timezone, lane, ask-for, avoid-asking-for, confidence, privacy tier)
relationships: typed edges to related pages (target, kind, weight, confidence, evidence kind, privacy tier, note)
Alex
example-handle
Example ecosystem routing
legal approval
"@example-handle"
"https://x.example/example-handle"
alex@example.com
Example rollout questions
unrelated billing decisions
targetId: entity.other-person
id: claim.example.routing
kind: maintainer-whois

pageType: entity
entityType: person
id: entity.example-person
canonicalId: maintainer.example-person
aliases:
  - Alex
  - example-handle
privacyTier: local-private
bestUsedFor:
  - Example ecosystem routing
notEnoughFor:
  - legal approval
lastRefreshedAt: "2026-04-29T00:00:00.000Z"
personCard:
  handles:
    - "@example-handle"
  socials:
    - "https://x.example/example-handle"
  emails:
    - alex@example.com
  timezone: America/Chicago
  lane: Example ecosystem
  askFor:
    - Example rollout questions
  avoidAskingFor:
    - unrelated billing decisions
  confidence: 0.8
  privacyTier: confirm-before-use
relationships:
  - targetId: entity.other-person
    targetTitle: Other Person
    kind: collaborates-with
    confidence: 0.7
    evidenceKind: discrawl-stat
claims:
  - id: claim.example.routing
    text: Alex is useful for example-ecosystem routing.
    status: supported
    confidence: 0.9
    evidence:
      - kind: maintainer-whois
        sourceId: source.maintainers
        privacyTier: local-private

Compile pipeline

Compile reads wiki pages, normalizes summaries, and persists a machine-facing snapshot in OpenClaw's shared SQLite plugin state. Runtime code uses the lifecycle-owned owner snapshot to load SQLite during async prompt preparation; synchronous prompt assembly never scrapes Markdown or reads cache files. Compiled output also powers first-pass wiki indexing for search/get, claim-id lookup back to owning pages, compact prompt supplements, and report generation.

Dashboards and health reports

When render.createDashboards is enabled, compile maintains dashboards under reports/:

Report	Tracks
`reports/open-questions.md`	pages with unresolved questions
`reports/contradictions.md`	contradiction note clusters
`reports/low-confidence.md`	low-confidence pages and claims
`reports/claim-health.md`	claims missing structured evidence
`reports/stale-pages.md`	stale or unknown freshness
`reports/person-agent-directory.md`	person/entity routing cards
`reports/relationship-graph.md`	structured relationship edges
`reports/provenance-coverage.md`	evidence class coverage
`reports/privacy-review.md`	non-public privacy tiers needing review before use

Search and retrieval

Search modes (--mode / tool mode param):

주요 항목:

shared: use the shared memory search flow when available
local: search the wiki locally
wiki_search / wiki_get use compiled digests as a first pass when possible
claim ids resolve back to the owning page
contested/stale/fresh claims influence ranking
provenance labels survive into results

Mode	Boosts
`auto`	balanced default
`find-person`	person-like entities, aliases, handles, socials, canonical IDs
`route-question`	agent cards, ask-for/best-used-for hints, relationship context
`source-evidence`	source pages and structured evidence metadata
`raw-claim`	matching structured claims; returns claim/evidence metadata

Agent tools

The plugin also registers a non-exclusive memory corpus supplement, so shared memory_search and memory_get can reach the wiki when the active memory plugin supports corpus selection.

Tool	Purpose
`wiki_status`	current vault mode and scope, resolved agent, health, Obsidian CLI availability
`wiki_search`	search wiki pages and, when configured, the shared memory corpus; accepts `mode` for person lookup, question routing, source evidence, or raw claim drilldown
`wiki_get`	read a wiki page by id/path, falling back to the shared memory corpus when shared search is enabled and the lookup misses
`wiki_apply`	narrow synthesis/metadata mutations without freeform page surgery
`wiki_lint`	structural checks, provenance gaps, contradictions, open questions

Prompt and context behavior

When context.includeCompiledDigestPrompt is enabled, memory prompt sections append a compact compiled snapshot from plugin state: top pages only, top claims only, contradiction count, question count, confidence/freshness qualifiers. This is opt-in because it changes prompt shape; it mainly matters for context engines or prompt assembly that explicitly consume memory supplements.

구성

Put config under plugins.entries.memory-wiki.config:

Key	Values / default	Notes
`vaultMode`	`isolated` (default), `bridge`, `unsafe-local`	chooses input and integration behavior
`vault.scope`	`global` (default), `agent`	one shared vault or one child vault per agent
`vault.path`	global default `~/.openclaw/wiki/main`	exact vault globally; agent-scope parent defaults to `~/.openclaw/wiki`
`vault.renderMode`	`native` (default), `obsidian`
`bridge.readMemoryArtifacts`	default `true`	import active memory plugin public artifacts
`bridge.followMemoryEvents`	default `true`	include event logs in bridge mode
`unsafeLocal.allowPrivateMemoryCoreAccess`	default `false`	required to run `unsafe-local` imports
`unsafeLocal.paths`	default `[]`	explicit local paths to import in `unsafe-local` mode
`search.backend`	`shared` (default), `local`
`search.corpus`	`wiki` (default), `memory`, `all`
`context.includeCompiledDigestPrompt`	default `false`	append the selected agent's compact digest snapshot to memory prompt sections
`render.createBacklinks`	default `true`	generate deterministic related blocks
`render.createDashboards`	default `true`	generate dashboard pages

{
  plugins: {
    entries: {
      "memory-wiki": {
        enabled: true,
        config: {
          vaultMode: "isolated",
          vault: {
            scope: "global",
            path: "~/.openclaw/wiki/main",
            renderMode: "obsidian",
          },
          obsidian: {
            enabled: true,
            useOfficialCli: true,
            vaultName: "OpenClaw Wiki",
            openAfterWrites: false,
          },
          bridge: {
            enabled: false,
            readMemoryArtifacts: true,
            indexDreamReports: true,
            indexDailyNotes: true,
            indexMemoryRoot: true,
            followMemoryEvents: true,
          },
          unsafeLocal: {
            allowPrivateMemoryCoreAccess: false,
            paths: [],
          },
          ingest: {
            autoCompile: true,
            maxConcurrentJobs: 1,
            allowUrlIngest: true,
          },
          search: {
            backend: "shared",
            corpus: "wiki",
          },
          context: {
            includeCompiledDigestPrompt: false,
          },
          render: {
            preserveHumanBlocks: true,
            createBacklinks: true,
            createDashboards: true,
          },
        },
      },
    },
  },
}

Per-agent vaults

Set vault.scope to agent to give every configured agent a separate wiki. In this scope, vault.path is a parent directory and OpenClaw appends the normalized agent id:

{
  agents: {
    list: [{ id: "support" }, { id: "marketing" }],
  },
  plugins: {
    entries: {
      "memory-wiki": {
        enabled: true,
        config: {
          vaultMode: "bridge",
          vault: {
            scope: "agent",
            path: "~/.openclaw/wiki",
          },
          bridge: {
            enabled: true,
            readMemoryArtifacts: true,
          },
        },
      },
    },
  },
}

Example: QMD + bridge mode

Use this when you want QMD for recall and memory-wiki for a maintained knowledge layer. Each layer stays focused: QMD keeps raw notes, session exports, and extra collections searchable, while memory-wiki compiles stable entities, claims, dashboards, and source pages.

{
  memory: {
    backend: "qmd",
  },
  plugins: {
    entries: {
      "memory-wiki": {
        enabled: true,
        config: {
          vaultMode: "bridge",
          bridge: {
            enabled: true,
            readMemoryArtifacts: true,
            indexDreamReports: true,
            indexDailyNotes: true,
            indexMemoryRoot: true,
            followMemoryEvents: true,
          },
          search: {
            backend: "shared",
            corpus: "all",
          },
          context: {
            includeCompiledDigestPrompt: false,
          },
        },
      },
    },
  },
}

CLI

See CLI: wiki for the full command reference, including wiki okf import, wiki apply metadata, wiki unsafe-local import, wiki chatgpt import / wiki chatgpt rollback, and the full wiki obsidian subcommand set.

openclaw wiki status
openclaw wiki doctor
openclaw wiki init
openclaw wiki ingest ./notes/alpha.md
openclaw wiki compile
openclaw wiki lint
openclaw wiki search "alpha"
openclaw wiki get entity.alpha
openclaw wiki apply synthesis "Alpha Summary" --body "..." --source-id source.alpha
openclaw wiki bridge import
openclaw wiki obsidian status

Obsidian support

When vault.renderMode is obsidian, the plugin writes Obsidian-friendly Markdown and can optionally use the official obsidian CLI for status probing, vault search, opening a page, invoking a command, and jumping to the daily note. This is optional; the wiki still works in native mode without Obsidian.

Recommended workflow

Recall, promotion, and dreaming stay owned by the configured memory backend.

주요 항목:

Memory Overview
CLI: memory
CLI: wiki
Plugin SDK overview

실습 체크리스트

공식 문서와 로컬 버전을 대조합니다: https://docs.openclaw.ai/plugins/memory-wiki
관련 CLI는 openclaw --help 및 하위 명령 --help로 옵션을 확인합니다.
설정 변경 시 openclaw config / openclaw doctor로 유효성을 검사합니다.
Gateway·채널·플러그인 변경 후에는 필요 시 Gateway를 재시작합니다.

자주 쓰는 명령·설정 예시

openclaw plugins enable memory-wiki
openclaw gateway restart

<vault>/
  AGENTS.md
  WIKI.md
  index.md
  inbox.md
  entities/
  concepts/
  syntheses/
  sources/
  reports/
  _attachments/
  _views/
  .openclaw-wiki/

openclaw wiki okf import ./bundles/ga4

pageType: entity
entityType: person
id: entity.example-person
canonicalId: maintainer.example-person
aliases:
  - Alex
  - example-handle
privacyTier: local-private
bestUsedFor:
  - Example ecosystem routing
notEnoughFor:
  - legal approval
lastRefreshedAt: "2026-04-29T00:00:00.000Z"
personCard:
  handles:
    - "@example-handle"
  socials:
    - "https://x.example/example-handle"
  emails:
    - alex@example.com
  timezone: America/Chicago
  lane: Example ecosystem
  askFor:
    - Example rollout questions
  avoidAskingFor:
    - unrelated billing decisions
  confidence: 0.8
  privacyTier: confirm-before-use
relationships:
  - targetId: entity.other-person
    targetTitle: Other Person
    kind: collaborates-with
    confidence: 0.7
    evidenceKind: discrawl-stat
claims:
  - id: claim.example.routing
    text: Alex is useful for example-ecosystem routing.
    status: supported
    confidence: 0.9
    evidence:
      - kind: maintainer-whois
        sourceId: source.maintainers
        privacyTier: local-private

{
  plugins: {
    entries: {
      "memory-wiki": {
        enabled: true,
        config: {
          vaultMode: "isolated",
          vault: {
            scope: "global",
            path: "~/.openclaw/wiki/main",
            renderMode: "obsidian",
          },
          obsidian: {
            enabled: true,
            useOfficialCli: true,
            vaultName: "OpenClaw Wiki",
            openAfterWrites: false,
          },
          bridge: {
            enabled: false,
            readMemoryArtifacts: true,
            indexDreamReports: true,
            indexDailyNotes: true,
            indexMemoryRoot: true,
            followMemoryEvents: true,
          },
          unsafeLocal: {
            allowPrivateMemoryCoreAccess: false,
            paths: [],
          },
          ingest: {
            autoCompile: true,
            maxConcurrentJobs: 1,
            allowUrlIngest: true,
          },
          search: {
            backend: "shared",
            corpus: "wiki",
          },
          context: {
            includeCompiledDigestPrompt: false,
          },
          render: {
            preserveHumanBlocks: true,
            createBacklinks: true,
            createDashboards: true,
          },
        },
      },
    },
  },
}

{
  agents: {
    list: [{ id: "support" }, { id: "marketing" }],
  },
  plugins: {
    entries: {
      "memory-wiki": {
        enabled: true,
        config: {
          vaultMode: "bridge",
          vault: {
            scope: "agent",
            path: "~/.openclaw/wiki",
          },
          bridge: {
            enabled: true,
            readMemoryArtifacts: true,
          },
        },
      },
    },
  },
}

Memory wiki

핵심 요약

memory-wiki: compiled knowledge vault with provenance, claims, dashboards, and bridge mode

한국어 가이드 범위: plugins/memory-wiki 경로의 설정·명령·제약·예시를 학습용으로 재구성합니다.

문서 구성

공식 문서의 주요 섹션은 다음과 같습니다.

Vault modes
Vault layout
Open Knowledge Format imports
Structured claims and evidence
Agent-facing entity metadata
Compile pipeline
Dashboards and health reports
Search and retrieval
Agent tools
Prompt and context behavior
구성
Per-agent vaults
Example: QMD + bridge mode
CLI
Obsidian support
Recommended workflow
Related docs

상세 내용

본문

memory-wiki is a bundled plugin that compiles durable knowledge into a navigable wiki: deterministic pages, structured claims with evidence, provenance, dashboards, and machine-readable digests.

주요 항목:

memory_search for one broad recall pass across whatever corpora are configured
wiki_search / wiki_get when you want wiki-specific ranking, provenance, or page-level belief structure
memory_search corpus=all to span both layers in one call, when the active memory plugin supports corpus selection

Layer	Owns
Active memory plugin	Recall, semantic search, promotion, dreaming, memory runtime
`memory-wiki`	Compiled wiki pages, provenance-rich syntheses, dashboards, wiki search/get/apply

openclaw plugins enable memory-wiki
openclaw gateway restart

Vault modes

Vault mode and vault scope are separate choices:

주요 항목:

isolated (default): own vault, own sources, no dependency on the active memory plugin. Use this for a self-contained curated knowledge store.
bridge: reads public memory artifacts and event logs from the active memory plugin through public plugin SDK seams. Use this to compile the memory plugin's exported artifacts without reaching into private plugin internals.
unsafe-local: explicit same-machine escape hatch for local private paths. Intentionally experimental and non-portable; use only when you understand the trust boundary and specifically need local filesystem access bridge mode cannot provide.
vaultMode chooses where wiki inputs come from.
vault.scope chooses whether all agents use one vault or each agent gets a child vault.
exported memory artifacts (indexMemoryRoot)
daily notes (indexDailyNotes)
dream reports (indexDreamReports)
memory event logs (followMemoryEvents)

Vault layout

Managed content stays inside generated blocks; human note blocks are preserved across regeneration.

주요 항목:

sources/: imported raw material and bridge/unsafe-local-backed pages
entities/: durable things, people, systems, projects, objects
concepts/: ideas, abstractions, patterns, policies (also the landing spot for OKF imports)
syntheses/: compiled summaries and maintained rollups
reports/: generated dashboards

<vault>/
  AGENTS.md
  WIKI.md
  index.md
  inbox.md
  entities/
  concepts/
  syntheses/
  sources/
  reports/
  _attachments/
  _views/
  .openclaw-wiki/

Open Knowledge Format imports

주요 항목:

non-reserved .md files are concept documents
each imported concept requires a non-empty type frontmatter field; missing type produces a missing-type warning and the file is skipped
unknown type values are accepted as generic concepts
index.md and log.md are reserved and never imported as concepts
broken or external markdown links are left unchanged

openclaw wiki okf import ./bundles/ga4

Structured claims and evidence

Agent-facing entity metadata

Entity pages carry generic routing metadata usable for people, teams, systems, projects, or any other entity type:

주요 항목:

entityType: for example person, team, system, project
canonicalId: stable identity key across aliases and imports
aliases: names, handles, or labels that resolve to the same page
privacyTier: free-form string; public is treated as no-review, any other value (for example local-private, sensitive, confirm-before-use) is flagged in reports/privacy-review.md
bestUsedFor / notEnoughFor: compact routing hints
lastRefreshedAt: source-refresh timestamp, separate from page edit time
personCard: optional person-specific routing card (handles, socials, emails, timezone, lane, ask-for, avoid-asking-for, confidence, privacy tier)
relationships: typed edges to related pages (target, kind, weight, confidence, evidence kind, privacy tier, note)
Alex
example-handle
Example ecosystem routing
legal approval
"@example-handle"
"https://x.example/example-handle"
alex@example.com
Example rollout questions
unrelated billing decisions
targetId: entity.other-person
id: claim.example.routing
kind: maintainer-whois

pageType: entity
entityType: person
id: entity.example-person
canonicalId: maintainer.example-person
aliases:
  - Alex
  - example-handle
privacyTier: local-private
bestUsedFor:
  - Example ecosystem routing
notEnoughFor:
  - legal approval
lastRefreshedAt: "2026-04-29T00:00:00.000Z"
personCard:
  handles:
    - "@example-handle"
  socials:
    - "https://x.example/example-handle"
  emails:
    - alex@example.com
  timezone: America/Chicago
  lane: Example ecosystem
  askFor:
    - Example rollout questions
  avoidAskingFor:
    - unrelated billing decisions
  confidence: 0.8
  privacyTier: confirm-before-use
relationships:
  - targetId: entity.other-person
    targetTitle: Other Person
    kind: collaborates-with
    confidence: 0.7
    evidenceKind: discrawl-stat
claims:
  - id: claim.example.routing
    text: Alex is useful for example-ecosystem routing.
    status: supported
    confidence: 0.9
    evidence:
      - kind: maintainer-whois
        sourceId: source.maintainers
        privacyTier: local-private

Compile pipeline

Dashboards and health reports

When render.createDashboards is enabled, compile maintains dashboards under reports/:

Report	Tracks
`reports/open-questions.md`	pages with unresolved questions
`reports/contradictions.md`	contradiction note clusters
`reports/low-confidence.md`	low-confidence pages and claims
`reports/claim-health.md`	claims missing structured evidence
`reports/stale-pages.md`	stale or unknown freshness
`reports/person-agent-directory.md`	person/entity routing cards
`reports/relationship-graph.md`	structured relationship edges
`reports/provenance-coverage.md`	evidence class coverage
`reports/privacy-review.md`	non-public privacy tiers needing review before use

Search and retrieval

Search modes (--mode / tool mode param):

주요 항목:

shared: use the shared memory search flow when available
local: search the wiki locally
wiki_search / wiki_get use compiled digests as a first pass when possible
claim ids resolve back to the owning page
contested/stale/fresh claims influence ranking
provenance labels survive into results

Mode	Boosts
`auto`	balanced default
`find-person`	person-like entities, aliases, handles, socials, canonical IDs
`route-question`	agent cards, ask-for/best-used-for hints, relationship context
`source-evidence`	source pages and structured evidence metadata
`raw-claim`	matching structured claims; returns claim/evidence metadata

Agent tools

The plugin also registers a non-exclusive memory corpus supplement, so shared memory_search and memory_get can reach the wiki when the active memory plugin supports corpus selection.

Tool	Purpose
`wiki_status`	current vault mode and scope, resolved agent, health, Obsidian CLI availability
`wiki_search`	search wiki pages and, when configured, the shared memory corpus; accepts `mode` for person lookup, question routing, source evidence, or raw claim drilldown
`wiki_get`	read a wiki page by id/path, falling back to the shared memory corpus when shared search is enabled and the lookup misses
`wiki_apply`	narrow synthesis/metadata mutations without freeform page surgery
`wiki_lint`	structural checks, provenance gaps, contradictions, open questions

Prompt and context behavior

구성

Put config under plugins.entries.memory-wiki.config:

Key	Values / default	Notes
`vaultMode`	`isolated` (default), `bridge`, `unsafe-local`	chooses input and integration behavior
`vault.scope`	`global` (default), `agent`	one shared vault or one child vault per agent
`vault.path`	global default `~/.openclaw/wiki/main`	exact vault globally; agent-scope parent defaults to `~/.openclaw/wiki`
`vault.renderMode`	`native` (default), `obsidian`
`bridge.readMemoryArtifacts`	default `true`	import active memory plugin public artifacts
`bridge.followMemoryEvents`	default `true`	include event logs in bridge mode
`unsafeLocal.allowPrivateMemoryCoreAccess`	default `false`	required to run `unsafe-local` imports
`unsafeLocal.paths`	default `[]`	explicit local paths to import in `unsafe-local` mode
`search.backend`	`shared` (default), `local`
`search.corpus`	`wiki` (default), `memory`, `all`
`context.includeCompiledDigestPrompt`	default `false`	append the selected agent's compact digest snapshot to memory prompt sections
`render.createBacklinks`	default `true`	generate deterministic related blocks
`render.createDashboards`	default `true`	generate dashboard pages

{
  plugins: {
    entries: {
      "memory-wiki": {
        enabled: true,
        config: {
          vaultMode: "isolated",
          vault: {
            scope: "global",
            path: "~/.openclaw/wiki/main",
            renderMode: "obsidian",
          },
          obsidian: {
            enabled: true,
            useOfficialCli: true,
            vaultName: "OpenClaw Wiki",
            openAfterWrites: false,
          },
          bridge: {
            enabled: false,
            readMemoryArtifacts: true,
            indexDreamReports: true,
            indexDailyNotes: true,
            indexMemoryRoot: true,
            followMemoryEvents: true,
          },
          unsafeLocal: {
            allowPrivateMemoryCoreAccess: false,
            paths: [],
          },
          ingest: {
            autoCompile: true,
            maxConcurrentJobs: 1,
            allowUrlIngest: true,
          },
          search: {
            backend: "shared",
            corpus: "wiki",
          },
          context: {
            includeCompiledDigestPrompt: false,
          },
          render: {
            preserveHumanBlocks: true,
            createBacklinks: true,
            createDashboards: true,
          },
        },
      },
    },
  },
}

Per-agent vaults

Set vault.scope to agent to give every configured agent a separate wiki. In this scope, vault.path is a parent directory and OpenClaw appends the normalized agent id:

{
  agents: {
    list: [{ id: "support" }, { id: "marketing" }],
  },
  plugins: {
    entries: {
      "memory-wiki": {
        enabled: true,
        config: {
          vaultMode: "bridge",
          vault: {
            scope: "agent",
            path: "~/.openclaw/wiki",
          },
          bridge: {
            enabled: true,
            readMemoryArtifacts: true,
          },
        },
      },
    },
  },
}

Example: QMD + bridge mode

{
  memory: {
    backend: "qmd",
  },
  plugins: {
    entries: {
      "memory-wiki": {
        enabled: true,
        config: {
          vaultMode: "bridge",
          bridge: {
            enabled: true,
            readMemoryArtifacts: true,
            indexDreamReports: true,
            indexDailyNotes: true,
            indexMemoryRoot: true,
            followMemoryEvents: true,
          },
          search: {
            backend: "shared",
            corpus: "all",
          },
          context: {
            includeCompiledDigestPrompt: false,
          },
        },
      },
    },
  },
}

CLI

openclaw wiki status
openclaw wiki doctor
openclaw wiki init
openclaw wiki ingest ./notes/alpha.md
openclaw wiki compile
openclaw wiki lint
openclaw wiki search "alpha"
openclaw wiki get entity.alpha
openclaw wiki apply synthesis "Alpha Summary" --body "..." --source-id source.alpha
openclaw wiki bridge import
openclaw wiki obsidian status

Obsidian support

Recommended workflow

Recall, promotion, and dreaming stay owned by the configured memory backend.

주요 항목:

Memory Overview
CLI: memory
CLI: wiki
Plugin SDK overview

실습 체크리스트

공식 문서와 로컬 버전을 대조합니다: https://docs.openclaw.ai/plugins/memory-wiki
관련 CLI는 openclaw --help 및 하위 명령 --help로 옵션을 확인합니다.
설정 변경 시 openclaw config / openclaw doctor로 유효성을 검사합니다.
Gateway·채널·플러그인 변경 후에는 필요 시 Gateway를 재시작합니다.

자주 쓰는 명령·설정 예시

openclaw plugins enable memory-wiki
openclaw gateway restart

<vault>/
  AGENTS.md
  WIKI.md
  index.md
  inbox.md
  entities/
  concepts/
  syntheses/
  sources/
  reports/
  _attachments/
  _views/
  .openclaw-wiki/

openclaw wiki okf import ./bundles/ga4

pageType: entity
entityType: person
id: entity.example-person
canonicalId: maintainer.example-person
aliases:
  - Alex
  - example-handle
privacyTier: local-private
bestUsedFor:
  - Example ecosystem routing
notEnoughFor:
  - legal approval
lastRefreshedAt: "2026-04-29T00:00:00.000Z"
personCard:
  handles:
    - "@example-handle"
  socials:
    - "https://x.example/example-handle"
  emails:
    - alex@example.com
  timezone: America/Chicago
  lane: Example ecosystem
  askFor:
    - Example rollout questions
  avoidAskingFor:
    - unrelated billing decisions
  confidence: 0.8
  privacyTier: confirm-before-use
relationships:
  - targetId: entity.other-person
    targetTitle: Other Person
    kind: collaborates-with
    confidence: 0.7
    evidenceKind: discrawl-stat
claims:
  - id: claim.example.routing
    text: Alex is useful for example-ecosystem routing.
    status: supported
    confidence: 0.9
    evidence:
      - kind: maintainer-whois
        sourceId: source.maintainers
        privacyTier: local-private

{
  plugins: {
    entries: {
      "memory-wiki": {
        enabled: true,
        config: {
          vaultMode: "isolated",
          vault: {
            scope: "global",
            path: "~/.openclaw/wiki/main",
            renderMode: "obsidian",
          },
          obsidian: {
            enabled: true,
            useOfficialCli: true,
            vaultName: "OpenClaw Wiki",
            openAfterWrites: false,
          },
          bridge: {
            enabled: false,
            readMemoryArtifacts: true,
            indexDreamReports: true,
            indexDailyNotes: true,
            indexMemoryRoot: true,
            followMemoryEvents: true,
          },
          unsafeLocal: {
            allowPrivateMemoryCoreAccess: false,
            paths: [],
          },
          ingest: {
            autoCompile: true,
            maxConcurrentJobs: 1,
            allowUrlIngest: true,
          },
          search: {
            backend: "shared",
            corpus: "wiki",
          },
          context: {
            includeCompiledDigestPrompt: false,
          },
          render: {
            preserveHumanBlocks: true,
            createBacklinks: true,
            createDashboards: true,
          },
        },
      },
    },
  },
}

{
  agents: {
    list: [{ id: "support" }, { id: "marketing" }],
  },
  plugins: {
    entries: {
      "memory-wiki": {
        enabled: true,
        config: {
          vaultMode: "bridge",
          vault: {
            scope: "agent",
            path: "~/.openclaw/wiki",
          },
          bridge: {
            enabled: true,
            readMemoryArtifacts: true,
          },
        },
      },
    },
  },
}

Memory wiki

핵심 요약

문서 구성

상세 내용

본문

Vault modes

Vault layout

Open Knowledge Format imports

Structured claims and evidence

Agent-facing entity metadata

Compile pipeline

Dashboards and health reports

Search and retrieval

Agent tools

Prompt and context behavior

구성

Per-agent vaults

Example: QMD + bridge mode

CLI

Obsidian support

Recommended workflow

Related docs

실습 체크리스트

자주 쓰는 명령·설정 예시

관련 링크

관련 가이드

Memory wiki

핵심 요약

문서 구성

상세 내용

본문

Vault modes

Vault layout

Open Knowledge Format imports

Structured claims and evidence

Agent-facing entity metadata

Compile pipeline

Dashboards and health reports

Search and retrieval

Agent tools

Prompt and context behavior

구성

Per-agent vaults

Example: QMD + bridge mode

CLI

Obsidian support

Recommended workflow

Related docs

실습 체크리스트

자주 쓰는 명령·설정 예시

관련 링크

관련 가이드