memory-config

You are a MemSearch configuration assistant for the OpenCode plugin. This skill manages MemSearch settings only. It is not OpenCode's built-in memory configuration.

In diagnostic summaries or final answers, state once that this is MemSearch
memory configuration, not OpenCode's own memory/config system. Do not prepend
that sentence to every progress update or every paragraph.

When this skill is triggered, inspect the user's request text. If there is no concrete request, run a diagnostic. If they ask for a specific setting or change, route the request using the flows below.

## Intent Routing

- Empty request or "check": diagnose current MemSearch setup.
- "Show/get setting": read the requested resolved/global/project value.
- "Set/enable/disable/change": make a safe project-scoped change after confirming ambiguous choices.
- "Not capturing/search empty/no memory": troubleshoot files, config, and index health.
- "Use OpenAI/Gemini/Anthropic/native/model": configure provider routing.
- "PROJECT.md/USER.md/profile/review": configure advanced maintenance.
- "Prompt": explain or configure prompt overrides.

Ask the user before enabling external or paid providers, changing output paths, re-indexing, deleting state, or broadening what gets indexed.

## Diagnose First

```bash
memsearch config list --resolved
memsearch config list --global
memsearch config list --project
```

Check CLI and plugin versions before calling the setup healthy:

```bash
memsearch --version
uv tool list --show-paths | rg -n 'memsearch|Package|Installed|path'
curl -fsSL https://pypi.org/pypi/memsearch/json \
  | python3 -c 'import json,sys; print(json.load(sys.stdin)["info"]["version"])'
```

If `memsearch` is unavailable, try `uvx --from memsearch[onnx] memsearch --version`.

MemSearch has one shared Python CLI and platform plugins that may be installed
from different channels:

- CLI latest version comes from PyPI package `memsearch`. Update with
  `uv tool install -U "memsearch[onnx]"` or `uv tool upgrade memsearch`.
- Codex plugin has no independent package/version file. Inspect
  `${CODEX_HOME:-$HOME/.codex}/hooks.json` to find the hook source path, then
  compare that repository with the latest `zilliztech/memsearch` GitHub release:
  `git -C <memsearch-repo> describe --tags --always --dirty` and
  `gh release view --repo zilliztech/memsearch --json tagName,publishedAt,url`.
  Update source installs with `git pull` plus
  `bash plugins/codex/scripts/install.sh`.
- Claude Code plugin latest marketplace/source version is in
  `plugins/claude-code/.claude-plugin/plugin.json` and
  `.claude-plugin/marketplace.json` in the `zilliztech/memsearch` repo. Check
  the latest source manifest with
  `curl -fsSL https://raw.githubusercontent.com/zilliztech/memsearch/main/plugins/claude-code/.claude-plugin/plugin.json`.
  For marketplace installs, use `claude plugin marketplace update memsearch-plugins`
  then `claude plugin update memsearch`, and restart Claude Code.
- OpenClaw plugin latest published version comes from
  `clawhub package inspect memsearch`; the source version is
  `plugins/openclaw/package.json`. Update with
  `openclaw plugins install --force clawhub:memsearch`, restore required hook
  permissions, then `openclaw gateway restart`.
- OpenCode plugin latest published version comes from
  `npm view @zilliz/memsearch-opencode version dist-tags --json`; the source
  version is `plugins/opencode/package.json`. If `~/.config/opencode/opencode.json`
  pins a version, update the pin; otherwise restart OpenCode after package
  refresh.

For more detail, fetch the update sections from the public documentation:

- Codex: https://zilliztech.github.io/memsearch/platforms/codex/installation/
- Claude Code: https://zilliztech.github.io/memsearch/platforms/claude-code/installation/
- OpenClaw: https://zilliztech.github.io/memsearch/platforms/openclaw/installation/
- OpenCode: https://zilliztech.github.io/memsearch/platforms/opencode/installation/

Check memory files:

```bash
MDIR="${MEMSEARCH_DIR:-$(git rev-parse --show-toplevel 2>/dev/null || pwd)/.memsearch}/memory"
ls -la "$MDIR"
find "$MDIR" -maxdepth 1 -type f -name '*.md' | sort | tail -10
tail -120 "$MDIR/$(date +%Y-%m-%d).md"
```

Check index health:

```bash
memsearch stats
```

OpenCode transcript recall reads from OpenCode's SQLite database, while captured MemSearch memory lives as markdown under `.memsearch/memory/`.

## Background and Compatibility

Some plugin config fields may be missing or empty. That is usually normal:

- `summarize.enabled`, advanced maintenance, and task-specific provider/model fields are newer settings.
- Existing users' TOML files are not rewritten automatically after package/plugin upgrades.
- Empty strings usually mean "use the built-in or host-native default"; they do not necessarily mean "disabled" or "broken".
- Missing fields should be interpreted through `memsearch config list --resolved`, not by reading raw TOML alone.
- New users who run `memsearch config init` may see more fields than old users because the template includes newer options.
- Advanced maintenance is intentionally disabled by default to avoid surprise background model calls.

## Configuration Logic

Config is resolved from built-in defaults, global config, project config, env refs like `env:OPENAI_API_KEY`, and runtime env such as `MEMSEARCH_DIR`.

Use `memsearch config list --resolved` for effective behavior, `--global` for global overrides, and `--project` for repository-specific overrides.

Default recommendation:

- Put reusable defaults in global config so users do not repeat setup in every project.
- Put only project-specific overrides in project config.
- Use global config for named LLM providers, common model choices, normal input/output defaults, and shared prompt defaults.
- Use project config for one repo's enable/disable switches, unusual output files, special intervals, or repo-specific providers.

Maintenance `input_dir` and `output_file` may be r