<think> tags shown in agent output instead of being filtered

[joelceo]

Problem

When using MiniMax-M2.7 through agent integrations (Zed, Claude Code, etc.), the thinking tags are being displayed as visible text in the chat instead of being processed internally and filtered out.

Also affects AI commit messages

This issue also occurs when MiniMax-M2.7 is used to generate commits via AI. The thinking tags appear in the commit message output, showing the model internal reasoning process as visible text.

Expected behavior

The thinking tags should be processed internally by the agent framework and not shown to the end user. Only the actual response content should be visible.

Impact

1. Poor user experience - users see internal reasoning mixed with responses
2. Context bloat - thinking tokens accumulate in conversation history
3. Makes the model appear broken or misconfigured
4. Commit messages contain unwanted thinking content

Root cause

The thinking tags are part of the model output format but agent integrations are treating the thinking content as regular text output rather than internal processing that should be stripped.

Suggested solutions

1. API parameter to control whether thinking tags are included in output
2. Default behavior change to NOT include thinking content in API output streams
3. Better documentation on how agents should properly parse and filter thinking content

References

• Issue MiniMax-M2.7 is highly verbose and slow #12 also reports verbose thinking causing context issues with Claude Code

[joelceo]

This is a duplicate of issue #12 which was reported earlier. See that issue for more context and a workaround using a CLAUDE.md with system prompt constraints.