Skip to main content
A wiki is a repository-backed knowledge base in your workspace. Use it for product documentation, team handbooks, research collections, and other knowledge that grows across linked documents. Every wiki owns a dedicated repository. Its content is stored as Markdown, with Git history and branches. Fractal turns that content into a reader with navigation, search, backlinks, and a graph of connections.

​
Create a wiki

  1. Open Add resource in your workspace.
  2. Select Wiki, then Continue.
  3. Enter a name and, optionally, a description.
  4. Choose the audience and select Create wiki.
Fractal prepares the repository and initial index. The wiki may show preparation status before it is ready.

​
Build it with an agent

An empty wiki offers Build with an agent.
  1. Select that action and choose a configured cloud agent.
  2. Fractal opens the agent with the wiki attached to your draft.
  3. Describe what you want the wiki to contain, then send your message.
For example:
Build a product handbook in this wiki. Start with an overview, the main concepts, and a glossary. Link related documents and identify questions that need my input.
Selecting the agent prepares the draft; sending it starts the request. External agents do not have the same in-app composer. For later changes, give an agent access to the wiki and specify what should change. Ask it to verify the resulting content as part of the task.

​
Read and explore

Use the wiki navigation to browse documents and folders. Search finds content across the built wiki, including documents you have not opened. Backlinks show which documents refer to the current page. The graph helps you explore relationships within the current section or the whole wiki. A wiki can contain Markdown tables, supported charts, and diagrams. It does not run the interactive HTML applications supported by pages.

​
Revisions and builds

The reader displays a prepared revision of the repository. A build turns a committed revision into readable pages, navigation, and search results. When a newer revision is being prepared, an already open revision remains readable. View latest opens the new ready build. The wiki menu’s Builds view shows progress and diagnostics. A ready build means the content is available to read. It does not mean every link or authored document has passed validation.

​
Work with the repository

Use Repo in the wiki menu to inspect its repository, or Copy Git URL to work with Git. An agent can edit Markdown on a branch, push its changes, run wiki maintenance and validation, and integrate the result. Changes need to reach the revision you are reading before they appear there. The repository belongs to the wiki and follows its audience. It cannot be renamed or deleted independently. Deleting the wiki also removes access to its repository.

​
Choose a wiki or a page

Use a wiki for connected documentation maintained over time. Use a page for a focused deliverable or interactive tool. For example, a research page can compare three approaches. After your team chooses one, a wiki entry can record the decision and become the reference for future work. For name and description changes, access, public links, and deletion, see Wiki settings.

​
Recover an expired build

A prepared build can expire while its build details and events remain available. This does not mean the source revision was deleted. Choose Rebuild this revision to prepare the same committed content again. Choose View latest when you intentionally want a newer ready revision. In Wiki options → Builds, select a build to inspect its attempts, errors, and events. Read this build opens an available ready version.

​
Search the revision you are reading

Wiki search uses the build currently open. Content on another branch or in a newer build will not appear until you open that version. Search results are incomplete means the results are partial, not that there are no other matches. Use the retry control if search fails. For reviewing source changes before integration, see Repositories and merge requests.