@minchoi What @Daniel_Farinax said cannot be overstated. I’ve been maining Grok build for better and for worse (😅) for 3 weeks now. It’s above & beyond the best bang for your buck now with Composer 2.5. To add to that, I would highly recommend https://t.co/hNsd5Faxv7 by

Grok-Wiki - Repository wikis powered by local agents

Source: https://grok-wiki.com/ Episode 01 / Desktop film

What’s Grok-Wiki?

A short product film for the desktop loop: source-grounded repository context, local CLI agents, and model access that stays with you.

Local CLI-first desktop

Grok-Wiki prepares repository context, streams source-grounded progress, and lets the selected CLI account own model access.

Desktop contractLocal-first

01

Wiki opens first

Generate from GitHub repos, URLs, or local folders; save finished artifacts to the library.

wikis

02

Model access stays with the CLI

Grok CLI, Codex CLI, Claude Code, Pi, and Antigravity authenticate through their own tools.

cli-owned

03

Telemetry has a payload boundary

Optional usage signals exclude prompts, answers, code, paths, keys, and run logs.

no payloads

WikiGenerate repository wikis

Starting

Wiki

Generate a repository wiki.

Add one or more GitHub repos, URLs, or local paths. Generated pages and source evidence appear in the library below.

GitHub URL, owner/repo, or local path

RuntimeGrok CLIMax pagesAuto <= 6FormatFirst 30 MinutesLanguagesEnglish

Ask

Ask across repositories.

Add repos, URLs, or local paths. Sources and activity appear only after a run exists.

What do you want to understand?

CE Bundled SKILL.mdRuntimeGrok CLI

IdeasRoot CausePlanMapBreakdown

Docs

Generate repository documentation.

Turn a GitHub repo, URL, or local folder into a docs-site structure with quickstarts, guides, references, examples, and source evidence.

GitHub URL, owner/repo, or local path

RuntimeGrok CLIFormatDocumentationGuides, reference, troubleshootingLanguagesEnglish

Settings

Settings mirror the desktop app.

Appearance, Language, Shortcuts, Skills, CLI, Privacy, and Skill Packs. Desktop is Local CLI-first today.

Interface language

Switch desktop UI between English, Japanese, and Mandarin. Wiki output languages stay separate.

EnglishEnglish interfaceCurrent

JapaneseJapanese interfaceAvailable

MandarinMandarin interfaceAvailable

Command Line

Install grok-wiki for terminal sessions, scripts, and orchestrated agents.

Grok-Wiki CLIDesktop-bundled runtime with local-agent auth.Install

Examplegrok-wiki ask owner/repo “What should I read first?“Copy

Privacy

Optional analytics omit prompts, answers, code, repo names, local paths, keys, and run logs.

Usage signalsApp open, selected section, generation counts, format, runtime, and success or error state.On

Session replayAutocapture and replay are off.Off

Shortcuts

Configure a global wiki shortcut, confirm or power launch mode, runtime defaults, and page/style defaults.

Launch behaviorDefault asks before generation. Power starts after GitHub repo resolution.Default

FeedbackVisual HUD and haptic feedback are optional.Opt in

Skill Packs

Compound Engineering lenses improve Ask and Wiki quality without taking over execution workflows.

Compound QualityIdeas, Root Cause, Plan, QA Review, and Page Shape.Bundled

Basic WikiUse repository code and explicitly attached wiki context only.Option

Local agent

Choose the CLI that owns model access.

The desktop runtime is Local CLI-first. Shared BYOK architecture exists, but desktop agents authenticate through their own CLIs today.

Public library

Public wikis and docs stay browsable.

The real public library supports All, Wikis, Docs, search, sort, format, page length filters, and public reader routes.

Runtime architecture

Desktop state, local CLI readiness, source grounding, and scoped rendering.

/public/wiki/:id CLI documentation

Install, authenticate, run, and publish from local agents.

/public/docs/:id Ask evidence map

Source inspector, code preview, answer citations, and process timeline.

/public/wikis

Repository memory

The context stays close to the work.

Grok-Wiki turns old runs, source trails, and generated docs into a local workspace your agents can actually read.

Source trailsLocal runsDocs archive

Workflows

Generate, ask, and index repos.

Start a wiki, ask a question, or add a GitHub repo. Grok-Wiki keeps the run, sources, and selected local CLI in view.

Wiki runselected local agent

runningAsyncFuncAI/grok-wiki

local first

01

Read repositoryResolve files and source scope

done

02

Draft outlineBuild page tree from evidence

live

03

Write pagesPatch active run monitor only

live

04

Attach sourcesLink exact files and lines

next

Generate a wiki without moving the desktop.

The run monitor advances in place while sidebar, reader, composer, and selected local agent stay stable.

Askrepo context attached

AsyncFuncAI/grok-wiki

What is the main entry point?

Working for 6s

Scanning repository structureFound desktop, public, and API entry surfaces.

Reading package scriptsMatched the local web and desktop commands.

Checking source evidencePreparing file-backed answer references.

is thinking through the repo...Active step streams without remounting the composer.

Ask the repo and keep sources visible.

Answers stream beside the evidence map, so claims stay tied to files instead of a detached chat transcript.

github.com/AsyncFuncAI/AsyncReviewindex from GitHub

Press the shortcut on a repo and start indexing.

Cmd + Shift + Space turns the active GitHub repository or local folder into source context without changing provider ownership.

Public library

Share docs, wikis, and Obsidian ZIPs.

Browse generated docs and public wikis, or download a vault-ready Markdown ZIP for Obsidian.

Docs readerGenerated pages can be browsed, shared, or exported as a Markdown vault.

/public/docs/:id### Local CLI setup

Install a local agent, authenticate through its CLI, and recheck readiness before generation.

CardsLink generated pages.

Code groupsShow cited examples.

StepsPreserve setup flow.

UpdatesTrack runbook changes.

Route mapPublished HTML, agent Markdown, and vault exports stay separate.

Public library

Public library/public/wikis

Docs gallery/public/docs

Wiki reader/public/wiki/:id

Docs reader/public/docs/:id

Obsidian ZIP/api/wiki/export.zip?id=:wiki

Agent Markdown/:surface/:id/llms.txt

Episodes/episodes

Changelog/changelog

Public wiki handoff

One click turns a public wiki into agent context.

Use Add Agent on a public Grok-Wiki page to point your selected local agent at the wiki’s source-backed context. Export the same pages as an Obsidian ZIP when you want the knowledge in your local vault.

Add AgentAgent MarkdownObsidian ZIP

Published pages stay useful for humans, local agents, and vault exports without moving model access away from the CLI accounts you own.

Customer proof

Here’s what Grok-Wiki users say.

Builders are using Grok-Wiki to understand repositories, share source-backed docs, and turn local agent runs into something others can actually read.

View on X

> “Sheing is brilliant, one to watch/follow for sure. Trying out Grok-Wiki now.” A founder signal from Kevin Rose, with Digg.com highlighted as a real-world Grok-Wiki use case.Neil Parker@nwparker_ / Orca

X

“Now we’ve got to re-write the whole thing to keep you on your toes!”

A practical builder reaction from Orca after seeing Grok-Wiki in the wild.

Gabe PerezLinkedIn

LinkedIn

“the structure mapping actually caught dependencies I forgot existed.”

Tried Grok-Wiki on a 50k LOC repo and pressed on how agents handle competing importance signals.

Matt Van Horn@mvanhorn

X

“love your work”

A concise X endorsement from a product-minded builder.

“awesome, keep shipping”

A short public signal from the Grok-Wiki launch thread.

“crazy Sheing and Grok-Wiki are on fire”

Deduped into one card with both public posts attached, including the Warp repository note.

“This might be my new favorite tool.”

Used Grok-Wiki a second time on a favorite tool that had been semi-broken and deprecated.

Agents on Grok-Wiki

FAQ

Frequently Asked Questions

Everything you need to know about working with Grok-Wiki. Still have a question?Get in touch.

Why use Grok-Wiki instead of just Codex, Claude Code, Grok, or ChatGPT?Grok-Wiki is not trying to replace your agent. It prepares repository context, runs the local CLI agent you already use, then turns the investigation into source-grounded wikis, docs, Ask sessions, and public handoff pages. The agent does the work; Grok-Wiki gives it durable structure, citations, and a workspace other agents can read later.

Where is my data stored?The desktop app runs a local loopback server and stores data under the app data directory. Your local agent credentials stay with their own CLI tools. Public wiki pages are separate read-only copies that exist only when you publish them.

How does Grok-Wiki keep the wiki grounded in the source?Each run starts from the repository itself, builds a structure from the files it reads, and keeps source trails attached to generated pages and Ask answers. The result is easier to inspect than a chat transcript because the useful claims are packaged back into navigable docs.

Can Grok-Wiki do more than generate a wiki?Yes. It can generate repository wikis and docs, answer questions against source evidence, keep run history, publish read-only pages, expose agent-readable Markdown, and export Obsidian-ready ZIPs. The point is to turn one investigation into reusable repository memory instead of another throwaway chat.

Can Grok-Wiki work with private repos, local folders, or my own cloud?The desktop and CLI flows are designed for local-first work where your authenticated tools and filesystem own access. For hosted deployments, the architecture keeps storage and provider credentials configurable so teams can run with their own auth, database, and infrastructure choices as the product expands.

What happens when I publish a wiki?Publishing creates a separate read-only page that you can share with teammates, users, or other agents. It does not turn the original workspace into a public editing surface; regeneration, Ask, and app controls stay in your local or authenticated workspace.

Can another agent use a Grok-Wiki page after it is generated?Yes. Published wikis expose agent-readable context through the public page and Markdown surfaces, so an agent can start from the generated structure instead of rereading the repository from zero.

What kinds of repositories are a good fit?Grok-Wiki is most useful when the codebase has enough surface area that a README is not enough: architecture handoffs, onboarding, legacy systems, SDKs, CLIs, internal tools, and projects where source-backed explanations matter more than a quick summary.