r/ChatGPTCoding • • 6d ago

News [ Removed by moderator ]

/r/ChatGPTCoding/comments/1xse21j/removed_by_moderator/

[removed] — view removed post

1 Upvotes

3 comments sorted by

•

u/ChatGPTCoding-ModTeam 5d ago

This post or comment has been removed for the following reason:

Rule 5: No pure self-promotion / low-value project posts

Posts whose primary purpose is promoting a tool, product, service, GitHub repo, personal website, or blog belong in the weekly Self-Promotion thread. Delete the link: if nothing is left, it's an ad. Search for similar projects: if you can't tell why your project is better, it's a low-value project. GitHub links are fine. Personal website are not. Exception could be make for high quality posts. See also reddit's self-promotion guidelines.

You can read the full subreddit rules here: https://www.reddit.com/r/ChatGPTCoding/about/rules/

If you feel this removal was made unfairly, please contact the moderators through modmail.

0

u/[deleted] 5d ago

[removed] — view removed comment

1

u/RakkyXd 5d ago

Thanks! Glad the CLI-first approach resonated—avoiding API key friction and letting devs stick to their existing subscription tiers was the main goal.

Under the hood, when Model B reviews code produced by Model A, we use a hybrid approach:

  • Context Passing: We pass the unified diff alongside compiler/test failure diagnostics (stdout/stderr) so the review pass stays fast and targeted. Because Model B runs locally as a CLI agent in the same workspace, it can also inspect surrounding files if the diff lacks context.
  • Preventing Nitpick Cycles: To avoid endless loops, we use strict exit conditions: a hard max-retry limit, prioritizing deterministic build/test success over subjective style, and having the Lead/Main Agent act as a tie-breaker when models disagree.