Craken / Docs

Wiki

Use the workspace wiki for durable Markdown pages, links, collaborative editing, history, backlinks, restore, and Ask Orca.

The wiki is the durable knowledge base for a workspace. Use it for decisions, procedures, research summaries, specs, plans, and any information that should remain findable after the conversation moves on.

Create And Rename Pages

Create a page from the Wiki + action, from the full wiki list, or by following an empty [[Page Title]] link and saving content.

A wiki page is identified by its title. A workspace cannot have two pages with the same title. When a page is renamed, Craken updates workspace wiki links that target that title, so you can improve page names without breaking existing links.

Edit Collaboratively

Wiki editing is collaborative. Multiple people can edit the same page, remote cursors appear in the editor, and changes autosave after idle time. Press Done when you finish editing to save remaining changes immediately and return to reading mode.

The editor supports autocomplete for pages, shared files, people, agents, and channels. Type [[, [[/, @, or # to open suggestions.

Wiki pages use Markdown with Craken workspace links:

  • Wiki pages: [[Launch Plan]] or [[Launch Plan|launch plan]].
  • Shared files: [[/briefs/q2-launch.pdf]].
  • Channels: #general.
  • Math: inline $E=mc^2$ or block $$ ... $$.
  • GFM tables, task lists, code fences, footnotes, and images.

See Syntax for details.

Meaningful saves create page versions. Open History to inspect who changed what and to read older versions. The Links area shows other pages and messages that point to the current page, which helps you see where a decision is being used.

Deleted Pages

Deleted wiki pages can be restored from Wiki More... to Deleted pages. Wiki pages do not use the same 30-day trash policy as deleted files.

Ask Orca About Selected Text

In reading mode, select text on a wiki page to open Ask Orca. Craken sends the selected passage as context in a DM with Orca, which is useful for summarizing, translating, explaining, or asking for follow-up edits.

Public Wiki Pages

Some wiki pages can be made public through the page's visibility setting. Public wiki pages are rendered as standalone public HTML or Markdown only when the current page is explicitly public. Private pages and private linked pages stay private.

To give a workspace a public wiki home page, create a page titled _Home, make it public, and share the public wiki URL. Visitors open it at /public/w/:workspace/wiki. The same page is available as Markdown at /public/w/:workspace/wiki.md, and other public pages can be read as Markdown by adding .md to their public page URL or by requesting Markdown. If a page title itself ends in .md, that exact public URL opens the page; request Markdown with the Accept: text/markdown header. Workspace members who open the normal /w/:workspace/wiki app URL still see the workspace app.

You can add public layout around public wiki HTML pages with two normal Markdown pages:

  • _Sidebar creates public navigation when the page is public. Use ## headings for sections, lists for the items in each section, and nested lists for collapsible groups.
  • _Footer adds small-text content to the page footer when the page is public. Use it for short notes, copyright text, status links, or contact links.

Public wiki HTML keeps a minimal document layout: the article stays on a readable measure, while _Sidebar navigation and generated contents use stable side columns that begin with the article body on wide screens and collapse into the reading flow on narrow screens. The side navigation and contents links share the same quiet link treatment, and the contents column marks the current section as you scroll.

These layout pages affect public HTML pages only. Markdown reads such as /public/w/:workspace/wiki.md or /public/w/:workspace/wiki/Page.md return just the requested page content.

Public wiki pages are cached for fast anonymous reading. Craken checks the current public page and layout state before reusing its server-side public copy, though a visitor's browser may briefly reuse a page it already cached locally.