You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Session title generation bypasses plugin hooks #46115
Session title generation bypasses plugin hooks entirely. The title agent's LLM call sends the raw first user message straight to the model — it never goes through plugin.trigger("experimental.chat.messages.transform", ...), unlike the main chat completion.
This means any plugin that redacts/anonymizes outgoing content (secrets, PII, etc.) has no way to intercept the title-generation request. The main chat message gets scrubbed correctly; the title request for the exact same message does not.
Suggested fix:
route title()'s outgoing messages through plugin.trigger("experimental.chat.messages.transform", ...) before the llm.stream() call, or add a dedicated hook for it.
Workaround in the meantime:
{"agent": {"title": {"disable": true}}} stops the call entirely (loses auto-generated titles).
Plugins
@rehydra/opencode v0.13.0 (used to surface the gap — content-transform plugins in general are affected, not specific to this one)
OpenCode version
1.18.20
Steps to reproduce
Install a plugin that redacts outgoing message content via experimental.chat.messages.transform
Start a new session, send a first message containing a secret
Inspect actual outbound HTTP requests (MITM proxy or request tracer)
See two LLM calls from the same input: main chat completion is scrubbed correctly; the title-generation call (agent=title, small=true) contains the raw, unscrubbed secret
Thanks for the report! OpenCode 2.0 is now out and development is focused on V2, so we're closing issues filed against OpenCode 1. Please upgrade (opencode upgrade --major, details: https://anoma.ly/notes/opencode-2-0), and if this is still relevant on 2.0, reopen this issue or open a new one with your 2.0 version.
Activity
thdxr commentedon Oct 11, 2026
Thanks for the report! OpenCode 2.0 is now out and development is focused on V2, so we're closing issues filed against OpenCode 1. Please upgrade (
opencode upgrade --major, details: https://anoma.ly/notes/opencode-2-0), and if this is still relevant on 2.0, reopen this issue or open a new one with your 2.0 version.— from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊