Context Topics

Project continuity for one OpenClaw agent.

Context Topics lets one agent move between different bodies of work without mixing them together. Put on a product-launch hat, and the agent remembers the launch plan, source-of-truth files, decisions already made, and what should not be re-litigated. Switch to a client engagement, research thread, open-source project, or half-started idea, and that work gets its own room too.

It is meant to feel like project memory, not a prompt trick. You can start a topic intentionally, capture a conversation after you realize it matters, close the topic with durable notes, and come back later with the context still waiting.

Context Topics stores everything as plain files under ~/openclaw-soul/topics/ and uses OpenClaw's public plugin hooks. No gateway fork. No Control UI patch. No drifting away from upstream updates.

Why This Exists

One good agent can help with many things, but conversations blur together. Project A has different rules than Project B. Decisions made last week get forgotten. A useful chat becomes hard to resume because it was never promoted into a durable workspace.

Context Topics gives each project a small, file-backed memory room:

• a working pin for what the agent should know immediately
• topic-local memory
• decisions
• artifact index
• notes
• validation through /topic doctor

The goal is simple: one agent, many hats, each with its own continuity.

Quick Start

Install from ClawHub:

openclaw plugins install clawhub:openclaw-context-topics
openclaw gateway restart

Then open a chat and type:

/topic

Create a new topic:

/topic new product-launch

Load it later:

/topic product-launch

Close it when the work is done:

/topic close

The One-Minute Demo

You are chatting normally and realize the conversation should become a project:

/topic capture whatsapp-research

Context Topics creates:

~/openclaw-soul/topics/whatsapp-research/
  topic.md
  memory.md
  decisions.md
  artifacts/
    README.md
    index.md
  notes/

On the next agent turn, the agent is asked to fill the starter pin, memory, decisions, and artifact index from the current conversation.

Later:

/topic whatsapp-research

The agent gets the topic room back as working context.

Commands

Topic Room Shape

New topics use this folder shape:

topics/<name>/
  topic.md
  memory.md
  decisions.md
  artifacts/
    README.md
    index.md
  notes/

topic.md contains YAML code blocks for the always-loaded pin, file references, recent-memory rules, live probes, and metadata.

Topic-local files are intentionally plain Markdown so they can be read, edited, backed up, diffed, and committed like any other project artifact.

Optional Memory Wiki Bridge

If OpenClaw's bundled Memory Wiki is enabled, Context Topics can publish a compact wiki page for each topic. The topic room is still the source of truth; the wiki page is an index card for native OpenClaw recall, search, and Memory Palace-style views.

By default, the bridge runs in auto mode:

• if Memory Wiki is enabled, /topic close, /topic capture, and /topic refresh export/update wiki/syntheses/<name>.md after the agent cleanup turn succeeds
• if Memory Wiki is not enabled, Context Topics keeps working normally
• /topic wiki <name> can export a topic manually
• /topic wiki status shows whether the bridge can see a wiki vault
• /topic doctor <name> includes bridge status

The exported page contains the topic title, summary, pin lists, source file pointers, and lightweight file stats. It does not copy complete memory, decisions, artifacts, source files, or secrets into the wiki.

Optional config:

{
  "plugins": {
    "entries": {
      "context-topics": {
        "enabled": true,
        "config": {
          "wikiBridge": {
            "enabled": "auto",
            "pageDir": "syntheses",
            "privacyTier": "local-private",
            "exportOnClose": true,
            "exportOnCapture": true,
            "exportOnRefresh": true
          }
        }
      }
    }
  }
}

Set wikiBridge.enabled to false or "off" to disable the bridge. Set wikiBridge.vaultPath only if you want to export to a different vault than the one configured by OpenClaw Memory Wiki.

Example Pin

pin:
  title: "Product Launch"
  summary: "Launch planning for the next release."
  current_state:
    - "Launch date is not final."
    - "Pricing copy is still under review."
  operating_rules:
    - "Keep recommendations practical and release-oriented."
    - "Do not reopen settled positioning unless new evidence appears."
  settled_decisions:
    - "Use the existing landing page instead of creating a new microsite."
  open_work:
    - "Draft launch checklist."
    - "Confirm owner for customer announcement."
  avoid:
    - "Do not suggest paid ads until budget is approved."

Privacy And Safety

Context Topics is local-first.

• Topic rooms live under ~/openclaw-soul/topics/.
• Plugin session state lives under ~/openclaw-soul/state/.
• The plugin does not execute shell commands.
• Live probes are listed for the agent to run manually when needed.
• Sensitive-looking files are not inlined.
• Sensitive-looking absolute paths are redacted from prompt bundles.
• Session identifiers are hashed before persistence or logging.

You still control what goes into each topic. Do not put secrets, tokens, private keys, or credential material in topic memory.

Upstream Safety

This plugin uses OpenClaw's public plugin SDK:

• registerCommand for /topic
• before_prompt_build for per-turn context injection
• registerSessionExtension as an optional session metadata probe
• agent_end to export optional wiki index pages after cleanup turns

It does not patch the gateway or Control UI bundle.

Feedback Wanted

This plugin is young. The most useful feedback is specific:

• Did /topic capture feel natural?
• Did /topic close write the right amount of memory?
• Did the topic pin help on the next session?
• Did anything feel too heavy, too magical, or too manual?
• What would make this safer for a team or shared machine?

Please open an issue with the command you ran, what you expected, what happened, and whether the topic files ended up useful.

Roadmap

Ideas being considered:

• richer file tiers and source-of-truth references
• better artifact indexing
• deeper optional Memory Wiki/Memory Palace integration once the upstream UI exposes stable plugin-owned page affordances
• optional team/shared-topic conventions
• import/export of topic rooms
• stronger schema validation for topic manifests
• more polished chat-stream topic status

Links

• ClawHub: https://clawhub.ai/plugins/context-topics

License

MIT-0. Free to use, modify, and redistribute.