docs: describe influence of take_over_control_mode on adapt_only_on_bare_turn_on#1377
docs: describe influence of take_over_control_mode on adapt_only_on_bare_turn_on#1377protyposis wants to merge 1 commit intomainfrom
take_over_control_mode on adapt_only_on_bare_turn_on#1377Conversation
|
I initially just wanted to update the docs to the current behavior, but actually it's debatable whether this behavior is desired. I'm not using |
|
Sorry it took me so long to get to this. I've been a bit overwhelmed by the number of AI-assisted PRs opened here recently, and I've also been spending nearly every spare hour on my biggest project so far, MindRoom. I'm very supportive of using AI for coding, but many of these PRs still need careful human review because even plausible-looking changes can introduce subtle breakage. That backlog made me postpone reviewing them for a while. I've now done a batch review with Codex / GPT-5.5 (xhigh). This comment is AI-assisted, but I've reviewed it before posting. The documentation improvement still seems useful, but this branch is stale/conflicting and changes generated docs/README content from an old base. Could you rebase and reapply only the current documentation wording change? For docs PRs, I want to avoid merging old generated README output over the current generated content. |
Minor docs tweak, see changed files.