Skip to content

Commit 96f3eeb

Browse files
committed
docs: use reasoning effort presets
1 parent 36c9a91 commit 96f3eeb

6 files changed

Lines changed: 17 additions & 41 deletions

README.md

Lines changed: 7 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -61,22 +61,18 @@
6161

6262
## 想调整模型的思考强度?(可选)
6363

64-
不设置也可以正常使用,模型会采用默认行为。只有你想手动控制思考强度时,才需要做下面的配置:
64+
不设置也可以正常使用,模型会采用默认行为。AstrBot 的模型编辑器已经提供
65+
**Reasoning Effort** 预设,不需要再手动新增 `reasoning_effort` 键。
6566

6667
1. 进入模型配置,编辑使用 `OpenAI Subscribe` 的那一个模型。
6768
2. 找到 **自定义请求体参数(`custom_extra_body`**
68-
3. 填入键名 `reasoning_effort`,值类型选 `string`,点击 **+ 添加**
69-
4. 在新出现的一行里填写具体值,最后点击右下角 **确认** 保存。
69+
3.**Reasoning Effort** 输入框中填写想要的值,然后点击右下角 **确认** 保存。
7070

71-
![添加 reasoning_effort 键](docs/images/reasoning-effort-add-key.png)
71+
![在内置的 Reasoning Effort 预设中填写 max](docs/images/reasoning-effort-preset-zh.png)
7272

73-
* 1:填好键名 `reasoning_effort`,并把值类型设为 `string` 后,点击 **+ 添加***
73+
*:AstrBot 内置的 **Reasoning Effort** 预设。填写 `max` 后点击 **确认** 即可*
7474

75-
![填写 reasoning_effort 值](docs/images/reasoning-effort-set-value.png)
76-
77-
*图 2:添加成功后填写值,例如 `max`,再点击右下角的 **确认***
78-
79-
可填写的值只有下面五个,全部用小写英文:
75+
本插件支持以下值,填写时请使用小写英文:
8076

8177
| WebUI 里常见的显示名 | 要填写的值 |
8278
| --- | --- |
@@ -86,14 +82,7 @@
8682
| Extra High | `xhigh` |
8783
| Max | `max` |
8884

89-
不要把左侧显示名直接填进去。插件会把这个设置转换成 Codex 所需的请求格式。
90-
如果你习惯直接编辑 JSON,等价写法是:
91-
92-
```json
93-
{
94-
"reasoning_effort": "max"
95-
}
96-
```
85+
请填写右侧的值,不要把左侧显示名直接填进去。插件会自动转换为 Codex 所需的请求格式。
9786

9887
### 只给当前会话调整思考强度
9988

README_en.md

Lines changed: 10 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -70,27 +70,20 @@ the sign-in in that private chat; the flow will not start in group chats.
7070
## Want to set the reasoning effort? (Optional)
7171

7272
You do not need to configure this for normal use—the model uses its default
73-
behavior. Only follow these steps if you want to choose the reasoning effort
74-
yourself:
73+
behavior. AstrBot's model editor already includes a **Reasoning Effort** preset,
74+
so you do not need to add a `reasoning_effort` key yourself.
7575

7676
1. Open model configuration and edit the model that uses `OpenAI Subscribe`.
7777
2. Find **Custom request body parameters (`custom_extra_body`)**.
78-
3. Enter `reasoning_effort` as the key, choose `string` as the value type, and
79-
click **+ Add**.
80-
4. Enter the desired value in the new row, then click **Confirm** in the lower
81-
right corner to save.
78+
3. Enter the desired value in **Reasoning Effort**, then click **Confirm** in
79+
the lower right corner to save.
8280

83-
![Adding the reasoning_effort key](docs/images/reasoning-effort-add-key.png)
81+
![Entering max in the built-in Reasoning Effort preset](docs/images/reasoning-effort-preset-en.png)
8482

85-
*Figure 1: Enter `reasoning_effort`, choose `string` as its value type, then
86-
click **+ Add**.*
83+
*Figure: AstrBot's built-in **Reasoning Effort** preset. Enter `max`, then
84+
click **Confirm**.*
8785

88-
![Entering the reasoning_effort value](docs/images/reasoning-effort-set-value.png)
89-
90-
*Figure 2: After adding the key, enter a value such as `max`, then click
91-
**Confirm** in the lower right corner.*
92-
93-
Use one of these five lowercase values:
86+
This plugin supports these lowercase values:
9487

9588
| Common WebUI label | Value to enter |
9689
| --- | --- |
@@ -100,14 +93,8 @@ Use one of these five lowercase values:
10093
| Extra High | `xhigh` |
10194
| Max | `max` |
10295

103-
Do not enter the label from the left column. The plugin converts the setting to
104-
the format Codex expects. If you prefer editing JSON directly, use:
105-
106-
```json
107-
{
108-
"reasoning_effort": "max"
109-
}
110-
```
96+
Enter the value from the right column rather than the label on the left. The
97+
plugin converts it to the format Codex expects.
11198

11299
### Set reasoning effort for only the current session
113100

-112 KB
Binary file not shown.
132 KB
Loading
134 KB
Loading
-115 KB
Binary file not shown.

0 commit comments

Comments
 (0)