01 — Introducing the llm-wiki-vision agent
I am the L L M wiki vision agent, working for Professor Chris Sweet at the Center for Research Computing at the University of Notre Dame.

02 — Persistent project memory with llm-wiki
L L M wiki provides persistent project-level memory across sessions, users, and harnesses. In this tutorial, we will install the plug-in in Codex, connect a GitHub wiki, ingest a document, and then demonstrate retrieval of the saved project decisions. Before we begin, L L M wiki depends on Git, a distributed version control system designed to track changes in files over time. A separate tutorial covers installing Git. Here, Git and GitHub access are already configured. Our example uses a private repository, with a plan that supports private wikis.

03 — 1. Add the marketplace
Begin on the Plugins screen in Codex.

04 — Choose Add a marketplace
Select Add, then choose Add a marketplace from the dropdown menu.

05 — Enter the marketplace source
Paste the L L M wiki Colab repository address into the Source field, then select Add marketplace. The address is shown on screen.

06 — Find llm-wiki under Personal
After adding the marketplace, select Personal on the Plugins screen. Find L L M wiki under the L L M wiki Colab heading, and open it.

07 — 2. Install llm-wiki
On the L L M wiki page, choose Install plug-in.

08 — Installation complete
The enabled skills cover wiki initialization, document ingestion, and maintenance.

09 — Check the plug-in hooks
Before creating a project, check the plug-in’s hooks. Scroll down to Hooks and select the settings icon.

10 — Confirm both hooks are enabled
Check that both Post Tool Use and Session Start are enabled. Both switches should be on as shown here. Next, we will create a project.

11 — 3. Create a project
Return to Codex and open the sidebar. Hover over Projects to reveal the plus icon, then click it to open the Create project dialog.

12 — Add a source folder
Under Source folders, select Add to choose a folder on your computer.

13 — Choose or create the project folder
Create a new folder for the demonstration. This keeps the example project together in one place.

14 — Add the project to Codex
With the source folder added, give the project a name. Here the project is called Install Demo. Then choose Create project.

15 — Initialize local Git
In the new project, ask Codex to initialize the folder as a Git repository. A short, natural-language request is enough.

16 — 4. Connect the GitHub repository
Next, ask Codex to create a private GitHub repository for this folder, connect it as the remote, and provide the first wiki page link. Codex reports the repository is connected as origin.

17 — Create the first wiki page
Open the wiki link and select Create the first page.

18 — Save the prefilled page
The editor already contains welcome text. Simply click Save page to create the first wiki page.

19 — The GitHub wiki is created
GitHub confirms that the wiki was created. With the Home page saved, return to Codex to initialize the wiki memory.

20 — 5. Run wiki-init
Back in Codex, type dollar wiki init and select the Wiki Init skill. Use the project’s GitHub wiki when asked which kind of wiki to initialize.

21 — Wiki memory is ready
Wiki init creates a new wiki with the basic files that define its schema, along with operational files such as an index and a log. Here, it sets up that structure in the GitHub wiki we just created.

22 — 6. Start with a source document
Our input is a short brief for a fictional neighborhood garden planner. It records a local C S V storage decision, the reason for that choice, an offline requirement, and features deferred from the first version.

23 — Ingest the brief
Ask Codex to ingest project brief dot text. This brings the source’s useful information into the project wiki.

24 — Ingestion complete
Confirm the proposed framing when asked. Codex creates a Project Brief source page and a Neighborhood Garden Planner project page. It updates Home, the index, and the log, and commits the changes locally. They have not been pushed to GitHub yet.

25 — Inspect the saved requirements
Open the source summary and inspect its requirements table. The C S V choice, volunteer editing rationale, and offline requirement are preserved. This knowledge now lives in the wiki’s files.

26 — 7. Query project memory
Ask which storage format was chosen, why, and what features were deferred. Request a citation to the wiki page. This capture uses the existing chat. To test persistence, repeat the question in a new chat in the same project.

27 — The answer cites the project wiki
The answer recovers the local C S V decision and explains that volunteers can edit the schedule without a database service. It identifies weather integration and user accounts as deferred, and cites the Neighborhood Garden Planner wiki page.

28 — The index grows with the project
The index now includes the Project Brief under source summaries. That entry gives later chats a route to the saved requirements and rationale.

29 — 8. Publish the wiki updates
Finally, explicitly ask Codex to push the wiki updates to GitHub. This publishes the saved wiki changes so they can be shared with other users and sessions.

30 — Push complete
Codex reports that the existing wiki commits were pushed successfully and the wiki is synchronized with its remote.

31 — Ready for the next conversation
We have added the marketplace, installed the plug-in, connected a GitHub wiki, ingested a source, and retrieved its decisions. The saved project memory is ready for the next conversation.