chore: remove deprecated empty_message_recovery experimental option

The empty message recovery is now enabled by default (no longer experimental).
Removes the config option from schema and all README files.

🤖 Generated with assistance of [OhMyOpenCode](https://github.com/code-yeongyu/oh-my-opencode)
This commit is contained in:
YeonGyu-Kim
2025-12-20 15:53:04 +09:00
parent a29e50c9f9
commit f27f5c42cc
5 changed files with 0 additions and 9 deletions

View File

@@ -897,7 +897,6 @@ Opt-in experimental features that may change or be removed in future versions. U
{
"experimental": {
"aggressive_truncation": true,
"empty_message_recovery": true,
"auto_resume": true
}
}
@@ -906,7 +905,6 @@ Opt-in experimental features that may change or be removed in future versions. U
| Option | Default | Description |
| ------------------------ | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `aggressive_truncation` | `false` | When token limit is exceeded, aggressively truncates tool outputs to fit within limits. More aggressive than the default truncation behavior. Falls back to summarize/revert if insufficient. |
| `empty_message_recovery` | `false` | Automatically recovers from "non-empty content" API errors by fixing empty messages in the session. Up to 3 recovery attempts before giving up. |
| `auto_resume` | `false` | Automatically resumes session after successful recovery from thinking block errors or thinking disabled violations. Extracts the last user message and continues. |
**Warning**: These features are experimental and may cause unexpected behavior. Enable only if you understand the implications.