Skip to content
Wenlan

Pages

Create and Update Wiki Pages

Turn related findings into a page you can read, follow its sources, and review changes when the underlying information changes.

Qi-Xuan LuUpdated 4 min read

At a glance

01

A page brings related sources and memories together. You can still search those records without creating a page.

02

Automatic upkeep can update AI-maintained pages. Human-edited or review-locked pages wait for review.

01

When a page is useful

A launch decision, a date, and a browser-support note are useful separately. A launch-plan page makes them easier to read together—and lets you open the sources behind each claim.

Use a page when you keep returning to the same subject. You do not need one for every imported document or saved fact.

02

Create and open a page

You can write a page in the app or ask your connected AI to organize saved material. With the Claude Code plugin, /wenlan steep processes eligible new material and updates out-of-date pages; /wenlan pages finds or opens a page.

/wenlan distill is the advanced path for organizing or rebuilding pages. Start with ordinary organization; rebuilding can affect edits you have made.

Claude Code
/wenlan steep
/wenlan pages launch

03

Check the sources before using the answer

Open a citation in the page and read the supporting record. For a launch plan, check the actual date and the reason for the release choice—not just whether a link exists.

If the record is wrong, correct that underlying information too. Editing only the page leaves the original material available to future searches.

04

What happens when a source changes?

When a tracked source or memory changes in Wenlan, the pages that depend on it are marked for refresh. A change to a file outside Wenlan must first reach the library through that source’s refresh path.

On-demand organization runs through your connected AI. Automatic background upkeep needs to be enabled with a ready model assigned to page synthesis. It processes eligible work over time; saving a change does not mean every page updates immediately.

Configure the model used for background work

05

Which changes need your approval?

Background refresh treats each page separately. One changed source can update an AI-maintained page while leaving a proposed revision for a page you edited.

  • AI-maintained page, not edited by you and not review-locked: a valid refresh can update it directly.
  • Page you created or edited: a background refresh waits as a proposed revision; the saved text stays in place.
  • Review-locked page: machine edits need approval, including edits explicitly requested through a connected AI.
  • Draft fails the citation-support check: the saved page stays unchanged.
Review changes before accepting them

06

If a page has not updated

Check these in order before asking for a rebuild.

  • Source: does the updated information appear in Wenlan itself?
  • On demand: run /wenlan steep in Claude Code or $wenlan steep in Codex, then inspect the result.
  • Automatic: check that background upkeep is enabled and the model assigned to page synthesis is ready; check Activity for progress.
  • Review: does the affected page have a pending revision? Inspect it and accept or skip the change.
  • Result: reopen the page and its citations. Confirm that the changed fact appears in both.
Optional CLI check
wenlan steep status

07

What the checks do—and do not—prove

For numbered citations, Wenlan compares cited text with the sentence or paragraph it is meant to support. A draft that fails the required support checks is not applied. Text overlap is not proof that a conclusion is true, and uncited statements still need judgment.

Wenlan also checks Mermaid diagrams for common syntax problems. These checks help catch mistakes; they do not replace reading the page and its sources.

Next

Review and Trust

Understand how Wenlan keeps uncertain memory visible: pending captures, revisions, contradictions, rejections, confirm, and forget.

Read next