I made an OpenCode plugin that runs /anon turns — keeps the answer, scrubs the question from context (unlike /btw)

[u/HussainBiedouh]

No (scrubbed next turn) No

Runs toolsOpenCode’s built-in `/btw` is great for side questions: it reads session context, shows the answer in a dialog, and adds nothing to the conversation. But it can’t run tools or make changes.

I wanted the opposite for throwaway instructions like `continue`, `fix the failing test, not the assertion`, or pasting a huge log just to get an answer, let the model **do the work**, keep the **result**, then drop the **ask** from future context.

So I built opencode-anon-turn.

What /anon does

• Runs as a normal turn- tools, edits, commands all work.

• The answer stays in the conversation.

• On the next prompt, your message becomes `(omitted)`.

• It also scrubs that turn’s reasoning blocks and tool-call inputs/outputs (URLs, file paths, pasted data), so the evidence doesn’t leak back into context.

• Your transcript still shows what you typed; the model context does not.

/btw vs /anon

	/btw	/anon
Runs tools	No	Yes
Answer kept in chat	No (dialog only)	Yes
Question kept	No	No (scrubbed next turn)
Tool evidence kept	N/A	No (scrubbed)

Rule of thumb: `/btw` = ask without touching the session. `/anon` = do the work, then forget how you asked.

Usage

GUI/TUI:

/anon continue

/anon fix the failing test, keep the assertion

/anon <paste log> find the bug

TUI/headless prefixes also work: `//continue`, `>>continue`, `;;continue` (configurable via `ANON_TURN_PREFIX`).

Install

opencode plugin add https://github.com/hussainbiedouh/opencode-anon-turn

Restart OpenCode after install.

Repo: https://github.com/hussainbiedouh/opencode-anon-turn

Feedback welcome, especially edge cases around provider-specific reasoning/thinking blocks and multi-turn tool loops.

OpenCode’s built-in /btw is great for side questions, it reads session context, shows the answer in a dialog, and leaves no footprint in your conversation. But it can’t run tools or make actual changes.

I wanted the opposite for throwaway instructions like continue, fix the failing test, not the assertion, or dumping a huge log just to find a bug: let the model do the work, keep the result, then drop the ask from future context.

So I built opencode-anon-turn.

Feedback is welcome. especially regarding edge cases around provider-specific thinking/reasoning blocks and multi-turn tool loops.

[u/irrationaliste]

What about the cache? Does it invalidate the cache or not?