文件最后提交记录最后更新时间
3 个月前
13 天前
12 天前
7 天前
21 天前
2 天前
README

config/ — oGMemory Configuration Directory

This directory holds all configuration files, templates, and environment variables for oGMemory.

Runtime Files (gitignored)

File Purpose
ogmem.yaml Runtime config (generated by ogmem onboard or ogmem config init)
.env Runtime environment variables (API keys, etc.)

Templates

File Purpose
ogmem.reference.yaml Master config template for all modes (local/docker/plugin)
env.example Environment variable template
deploy.env.reference Docker deployment environment variables template
agfs/config.reference.yaml AGFS server configuration reference
openclaw/ogmem.template.json OpenClaw Gateway template (placeholder-based)

The OpenClaw template, plugin schema, and server configuration default semanticTurnMode to user_message, matching the verified OpenClaw 2026.6.10 lifecycle. This is currently the only supported semantic Turn mode; the option is retained as an explicit extension point for future host lifecycles.

Large tool-result externalization is opt-in. When enabled, first_view_enabled defaults to true, allowing a trusted post-tool/pre-model middleware to replace an individual result at or above single_result_chars with a multiresolution Artifact stub before its first model request.

Usage

ogmem onboard   # Interactive wizard generates ogmem.yaml and .env for you

Local development (manual)

cp config/ogmem.reference.yaml config/ogmem.yaml
cp config/env.example config/.env
# Edit config/ogmem.yaml and config/.env with your settings

Docker deployment

cp config/deploy.env.reference deploy/deploy.env
# Edit deploy/deploy.env, then run bash deploy/deploy.sh

Config search order

  1. OGMEM_CONFIG environment variable
  2. config/ogmem.yaml (this directory)
  3. /etc/ogmem/config.yaml (Docker/production)

Priority per field: YAML value > environment variable > code default

Mode annotations in ogmem.reference.yaml

  • [all] — applies to all deployment modes
  • [local] — local development only
  • [docker] — Docker deployment (uses ${ENV_VAR} from deploy.env)