Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
cli agents ive used so far have kind of sucked in comparison to getting context and just asking chatgpt ui. i like chatgpt model for coding. i couldnt use it cos codex cli ui sucked dick. now it is actually very good and auth is smoother (or i have lower tolerance for annoyance). ive been using it stock for a week with brew (imperatively) and its time to give it a go but properly thus this PR. seems to me like CLI agents are at a point now where its no longer early adopter and now more like first to an objectively force multiplying thing. may be good to promote them from a shitty tool to a core part of my workflow shitty tool that i now have to unshittify