-
Notifications
You must be signed in to change notification settings - Fork 0
workflows
Patterns we've seen agents fall into naturally when given mind-map.
Before creating a page, search for the topic. If something exists, update it; if not, create. Avoids duplicate notes and orphan pages.
graph TD
A[Agent has new info] --> S[search_pages]
S --> H{Hit?}
H -->|yes| GP[get_page]
GP --> U[update_page with merged content]
H -->|no| CP[create_page]
When update_page-ing prose that references another concept, agents tend to drop in [[wikilinks]] to other pages they remember. Over time the wiki becomes a tight graph — exactly what design/wikilinks-as-graph is meant to expose.
Agents working on a project keep a single page with concepts/frontmatter:
---
type: project
status: active
last_touched: 2026-05-17
---Plus a "Decisions" subsection where each entry links to a dedicated page under decisions/. The concepts/backlinks panel then reveals "which projects this decision affects."
When a project is renamed or a topic gets split:
list_pages prefix=old/- For each page, agents/mcp-tools from
old/footonew/foo - The link table is updated atomically; no manual link-rewriting.
See guides/refactoring-a-wiki.
A fresh agent session usually starts with get_wiki_context to learn the top-level structure, then list_pages prefix=recent/ or search_pages to find what the human was last working on.