OpenWiki

Read repository memory

Do not enumerate, preload, or search wikis at task start. Use retrieval when the user asks for it, when unfamiliar architecture or dependency behavior materially affects the task, or when source inspection leaves an important uncertainty. Stop once the question is grounded.

When those conditions apply, use openwiki_search({ root, query, paths?, limit? }) to locate code, understand behavior or relationships, choose an approach, or find a testing procedure. Supply the absolute Git top-level. Optional repository-relative source paths boost related sections without filtering other matches. Empty results are valid.

Repositories connected by openwiki link form named wiki workspaces. When the current wiki belongs to no workspace, search it alone. When it belongs to one workspace, search that workspace automatically. When it belongs to multiple workspaces, use its persistent active workspace. If none is active, openwiki_search returns status: "workspace_required" with the choices: ask the user which workspace applies, then retry with its workspace ID. Remember that choice for later searches in the conversation unless the user changes it.

Use openwiki_list_workspaces({ root, wiki? }) to list the workspaces containing the current wiki, or another reachable wiki identified by wiki. Use openwiki_list_wikis({ root, workspace }) to inspect the members of one workspace. Every workspace search result includes a wiki plus compact refs such as openwiki/architecture/jobs.md#retry-control. When a result is relevant, split the ref at # and call openwiki_read({ root, wiki, page, sections }) with that result's wiki ID and the exact page and heading anchors needed. Omit wiki for an ordinary unlinked repository. Read returns each complete selected section in request order. Neither operation starts a generation run or invokes a model.