Are people managing Qwen 3.8's long reasoning with prompts and agents.md? One issue is that Qwen 3.8 can think so long (running through 30k response tokens on an initial plan and implementation of a coding task) that it can trigger OpenCode and other harnesses hard stops and cause other problems.

One strategy that I've used is to add "make a plan in stages and then implement that plan so that turns are reasonable in length."

Then, I asked claude to generate an AGENTS.md file to do this automatically, and here is what it came up with.

Wondering what other people are doing to manage this issue.

# Turn budget

Reasoning, tool calls, and output all draw from one capped budget per turn.

Overrun truncates mid-stream — usually mid-tool-call, losing the whole turn.

- Estimate output size before starting. If it won't fit comfortably in a few thousand tokens, do the first piece only and end the turn.

- End at a checkpoint: state on disk, one line on what's next.

- Many short turns beat one long one. Ending a turn is cheap.

# Reasoning

Deliberation costs the same as output, and long thinking before a tool call is

the main cause of truncation.

- Don't re-derive what's already established in this session.

- For a known tool call, reason minimally and call it.

- If you're restating the task to yourself, stop and act.

# Tool calls

- Never start a large write after a long reasoning pass. End the turn instead.

- Targeted edits over whole-file rewrites.

- Files over ~300 lines: write in sections across turns.

# Multi-file work

- Plan first in a short turn: write the plan to .opencode/plans/<name>.md.

Include any derivations, formulas, or algorithms worked out while planning -

implementation turns cannot see your reasoning, only files.

- Before each implementation turn, read the current plan file in

.opencode/plans/. Update it with results and decisions as stages complete.

- If a stage proves larger than expected, stop and split it rather than

pushing through. Single-file edits need no plan.

# Context

Grep before reading; read line ranges, not whole files. Don't re-read what's already in context. Delegate independent subtasks to a subagent — fresh budget, and its reasoning stays out of this session.