[Question] How can I safely remove the redundant/ineffective system prompts that oh-my-opencode injects into the context? (I'm using ACP.)

[BsoBird]

How can I safely remove the redundant/ineffective system prompts that oh-my-opencode injects into the context? (I'm using ACP.)

[BsoBird]

ework 接单

[ranxianglei]

重新调度

[ranxianglei]

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 Short answer: if you're on ACP ≥ 1.14.8 you don't need to do anything — ACP already ships oh-my-opencode cleanup filters that are enabled by default.

What ACP does out of the box

Since v1.14.8 (PRs #239, #242), ACP includes 5 built-in message filters targeting OMO's per-turn injections. All on by default:

Filter	Behavior
omo-system-reminder	Keeps the last 2 OMO <system-reminder> messages; for older ones, strips the <system-reminder> blocks + <!-- OMO_INTERNAL_INITIATOR --> markers but preserves your actual user content
omo-context	Keeps only the latest OMO [CONTEXT] injection; drops earlier duplicates
omo-task-directive	Keeps only the latest OMO TASK: / ## TASK directive; drops earlier ones
omo-todo-continuation	Keeps only the latest TODO CONTINUATION directive; drops earlier ones
omo-mode-injection	Strips leading mode blocks (<ultrawork-mode>, [search-mode], …) and preserves user content

Why it's safe

• Filters run before ACP assigns message refs (lib/hooks.ts:237) — filtered content is never counted toward context usage or compression triggers.
• Only user-role messages carrying OMO markers are touched; the stripping filters remove just the injected blocks, never your real message content.
• keepLast semantics keep the most recent injection(s), so the model still sees the current state instead of stale history.
• A filter that throws is caught and logged (warn once per filter per pass) — it can't break your session.
• Every filter is individually toggleable, so you can roll back exactly one.

Verify yours is actually running

1. Check your ACP version — you need ≥ 1.14.8 (current latest: 1.14.27, stable: 1.14.26). If you're older, update the plugin and restart opencode.
2. With "debug": true, filter activity shows up in the ACP daily log (per-drop debug entries + a per-pass Message filters applied info summary with drop counts).
3. Compare context usage before/after with /acp context.

Tune or disable (~/.config/opencode/acp.jsonc)

{
  "messageFilters": {
    "enabled": true,
    "filters": {
      "omo-system-reminder": { "enabled": true, "keepLast": 2 },
      "omo-context": { "enabled": true },
      "omo-task-directive": { "enabled": true },
      "omo-todo-continuation": { "enabled": true },
      "omo-mode-injection": { "enabled": true }
    }
  }
}

• "messageFilters": { "enabled": false } — turn everything off
• per-filter "enabled": false — disable just one
• "keepLast": N — for the dedup filters, keep the last N instead of 1 (e.g. keep the last 3 system-reminders)

Scope caveat

These filters target OMO injections that arrive as user-role messages (system-reminder blocks, CONTEXT/TASK directives, mode tags). If the redundant text you're seeing is in the actual system prompt (e.g. OMO's agent definitions), ACP's message filters don't touch the system prompt — that's controlled by oh-my-opencode's own config. If that's your case, paste a snippet of the offending text and where it appears and we'll take a look.

(Side note for maintainers: messageFilters isn't documented in README.md / CONFIGURATION.md — worth a docs PR, since a default-on feature is currently undiscoverable.)

[ranxianglei]

提交一个pr 配置文件写好这些例子 中英文都写

[ranxianglei]

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 已提交 PR：**https://github.com/ranxianglei/opencode-acp/pull/381**（docs: add messageFilters config reference + examples (EN/ZH)）

改动内容（纯文档，无代码变更）：

• CONFIGURATION.md / CONFIGURATION.zh-CN.md — 新增 ### messageFilters 章节：
  • messageFilters.enabled（主开关，默认 true）
  • messageFilters.filters（按过滤器的 enabled + keepLast）
  • 5 个内置 OMO 过滤器的表格（名称、版本、行为）
  • 完整配置示例
  • Common Config Recipes / 常用配置模板 里新增一条配方：调 keepLast（如保留最近 3 条 system-reminder）、单独禁用某个过滤器、整体关闭
• README.md / README.zh-CN.md — 默认配置块（Default Configuration）里补上了 messageFilters 条目（中英文注释）

验证：

• 文档里的默认值/行为全部对照源码核对过（lib/config.ts 默认值、lib/messages/filter/builtin/*.ts 过滤器名称/版本/keepLast、lib/messages/filter/apply.ts:115-116 的 keepLast 解析逻辑）
• npm run typecheck ✅、npm run build ✅、全量测试 1112/1112 通过 ✅

顺带发现一个既有文档不一致（未在本 PR 修改，超出范围）：qualityGate.algorithms.rouge-recall-v1.layer1MinRetentionPct 在 CONFIGURATION.md 的表格里写的是 5.0，但 README 默认配置块里是 1.0，建议单独修一下。

devlog 在 devlog/2026-09-09_message-filters-docs/（REQ + WORKLOG）。