-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Read-only chat modes documentation is ambiguous #2848
Comments
Thanks for trying aider and filing this issue. I've updated the description. |
The change is available in the main branch. You can get it by installing the latest version from github:
If you have a chance to try it, let me know if it works better for you. |
@paul-gauthier The wording change is a good start. I am still fuzzy on the distinction between the two modes. I gather from Separating code reasoning and editing | aider that |
I'm labeling this issue as stale because it has been open for 2 weeks with no activity. If there are no additional comments, I will close it in 7 days. Note: A bot script made these updates to the issue. |
I'm closing this issue because it has been stalled for 3 weeks with no activity. Feel free to add a comment here and we can re-open it. Or feel free to file a new issue at any time. Note: A bot script made these updates to the issue. |
Issue
The docs at In-chat commands | aider say the folowing:l
/architect
Enter architect mode to discuss high-level design and architecture. If no prompt provided, switches to architect mode./ask
Ask questions about the code base without editing any files. If no prompt provided, switches to ask mode.Based on these descriptions, it is difficult to tell which mode to use.
Version and model info
The text was updated successfully, but these errors were encountered: