feat(agent-core): suggest update-config command in max-steps error - #1099
Conversation
|
commit: |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f6ba085305
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
…oonshotAI#1099) (cherry picked from commit f059649)
Related Issue
N/A — small follow-up to #1097.
Problem
The per-turn step limit error added in #1097 only points users to edit
loop_control.max_steps_per_turninconfig.tomlby hand. Users who prefer the interactive config command get no hint that they can run/update-configand then/reloadinstead.What changed
Extend the
loop.max_steps_exceedederror message to also suggest running/update-configfollowed by/reload, next to the existingconfig.tomlinstruction.Checklist
gen-changesetsskill, or this PR needs no changeset.gen-docsskill, or this PR needs no doc update.