@BraceSproul: https://x.com/BraceSproul/status/2075276912134631484

X AI KOLs Following Tools

Summary

OpenWiki 0.1.0 introduces OpenWiki Brains, a tool that creates and maintains a local wiki from sources like Gmail, Notion, git repos, and web search, giving AI agents proactive, durable memory without manual updates.

https://t.co/2SBVU0znJZ
Original Article
View Cached Full Text

Cached at: 07/10/26, 08:08 AM

Introducing OpenWiki Brains, general-purpose wiki memory for agents

Today we’re releasing OpenWiki Brains, a way to generate and maintain wiki memory for your agents from the sources you already use.

OpenWiki started as an OSS CLI for codebase documentation. You ran it in a repo, it generated a wiki for that codebase, and it kept the wiki updated as the code changed.

That workflow still works. But with OpenWiki 0.1.0, we’re expanding the idea beyond codebases.

OpenWiki can now create a general-purpose brain for your agents. It connects to sources like Gmail, Notion, git repos, Twitter/X, Hacker News, and web search, then turns that information into a local wiki your agents can use as memory. It can also keep that wiki updated automatically, so your agents have access to fresh context without you manually writing or maintaining it.

The goal is your agents should know the important context about your work, projects, interests, and research without forcing you to copy that context into every session.

Why agents need wiki memory

Agents work better when they have the right context.

For coding agents, that context is usually the repo. They need to know where key logic lives, how files connect, and which patterns the codebase expects. That was the original reason we built OpenWiki.

But agents increasingly work across more than code. They help with research, planning, writing, customer work, personal workflows, and internal tools. For those tasks, useful context is scattered across many places.

It might live in Gmail, Notion, bookmarked posts, Hacker News threads, git repos, or repeated web searches.

You can ask an agent to search those sources each time, but that is slow and inconsistent. You can write the context down yourself, but then you have to keep it updated.

OpenWiki Brains gives agents a durable place to look. It turns your connected sources into a structured wiki that can be refreshed over time.

How this is different from built-in memory

Many agents already have memory. Claude, ChatGPT, and other assistants can remember facts you tell them and use those facts in future conversations.

That memory is useful. OpenWiki Brain is not trying to replace it.

The limitation is that built-in memory is mostly reactive. It remembers information you explicitly give the agent, or information the agent can infer from your conversations with it.

That works for preferences and facts you’ve already shared. It works less well for context that changes across your tools every day.

If an important project update happens in Slack, your agent should be able to know about it. If relevant meeting notes land in Notion, it should be able to incorporate them. If a useful thread shows up in email, or you bookmark something on Twitter/X, that context may matter later even if you never paste it into a chat.

OpenWiki Brain is proactive memory. It connects to your sources, looks for information that matches what you asked it to care about, and writes that information into a wiki your agents can use later.

Built-in memory helps agents remember what you told them. OpenWiki Brain helps agents learn from the places where your work already happens.

Personal Brain

Personal Brain is the main new mode in OpenWiki 0.1.0.

It creates a local wiki based on the sources you connect. The wiki can include context about active projects, topics you are researching, people or companies you are working with, saved links, relevant emails, notes, and other information your agents may need later.

During setup, OpenWiki asks what the brain should focus on. We provide a default prompt for a general personal assistant, but you can customize it.

For example, you could tell OpenWiki to focus on active projects, AI research topics, customer context, saved links, or recent notes from a Notion workspace.

That prompt helps OpenWiki decide what to preserve when it ingests new information.

Connectors

Personal Brain works through connectors. Connectors let OpenWiki pull context from the places where your information already lives.

The first set of connectors includes:

  • Gmail

  • Notion

  • Git repositories

  • Twitter/X

  • Hacker News

  • Web search

Slack support is coming soon.

Some connectors are deterministic. Gmail can fetch recent emails. Twitter/X can fetch recent timeline data or bookmarks. Hacker News can fetch recent posts. Git repos can inspect recent commits.

Other connectors need a more agentic approach. Notion and web search are good examples. There is no simple feed of “everything relevant.” For those sources, OpenWiki gives the agent tools at ingestion time. You describe what you want it to look for, and the agent searches with that goal in mind.

Keeping the brain up to date

A brain is only useful if it stays current.

Personal Brain runs locally, so OpenWiki can set up a scheduled job on your Mac that updates the wiki automatically. It can also wake your computer shortly before the job starts, so the brain can update overnight.

When the scheduled run starts, OpenWiki goes through your configured connectors and updates the wiki with new information.

The intended workflow is that you configure your sources once, then let OpenWiki maintain the brain in the background.

Code Brain still exists

OpenWiki still supports the original codebase workflow, now called Code Brain.

Code Brain runs inside a git repo, generates documentation, writes it into an openwiki directory, and updates agent instruction files with a reference to the wiki.

Code Brain and Personal Brain are separate because they solve different problems. Code Brain cares about repo structure, git history, file relationships, and coding conventions. Personal Brain cares about broader work context across your connected sources.

The prompts are different. The connectors are different. The update workflows are different.

The underlying idea is the same. OpenWiki gives agents generated, maintained context they can use when they need it.

Markdown first

OpenWiki Brains currently use plain Markdown files.

Markdown is easy to read, easy to inspect, and easy for agents to navigate. It also keeps the brain visible on the filesystem instead of hiding it behind an interface.

We expect the format to evolve. Inter-page linking, richer knowledge formats, and formats like Google’s Open Knowledge Format are all interesting directions. For now, Markdown gives us a simple starting point that works with existing agent workflows.

What comes next

There are a few areas we want to improve.

First, more connectors. Slack is coming soon, and we expect to add more sources over time like LangSmith traces, Claude/Codex local sessions, and more.

Second, better retrieval. Right now, the brain is a wiki on the filesystem. We are exploring full-text search, MCP, semantic search, and agentic search over the brain.

Third, better formats. Markdown works well as a starting point, but we want to keep exploring better ways to represent agent memory and link related context.

We’d love feedback from the community on all of this.

Try it

OpenWiki is open source and available now.

You can use Code Brain to generate and maintain documentation for a repo. You can use Personal Brain to generate a general-purpose wiki from your connected sources and keep it updated automatically.

Check out the repo here: https://github.com/langchain-ai/openwiki

And try it via NPM: https://www.npmjs.com/package/openwiki

npm install -g [email protected]

openwiki personal –init

Similar Articles

@hwchase17: https://x.com/hwchase17/status/2071963622298050997

X AI KOLs Timeline

The article discusses the emerging pattern of 'wiki memory' for AI agents, where raw source data is intelligently compressed into a persistent, structured knowledge layer that agents can use efficiently. It compares this to basic RAG and gives examples like DeepWiki and LLM Wiki.

@ziwenxu_: https://x.com/ziwenxu_/status/2053241837453029439

X AI KOLs Timeline

The article details a workflow for creating an automated 'Codex Knowledge Vault' using Obsidian, where AI agents automatically ingest and organize daily bookmarks into a structured knowledge base to reduce context debt.