@TheAmolAvasare@patomolina The same thing happened to our 40+ team. We're a professional organization and have dedicated time to investing in Claude as our primary operations hub. We've received no support after being banned without warning.
@trq212@bcherny@claudeai@ClaudeDevs - Our organization's account was suspended without warning, disrupting our operations and product. We've submitted an appeal but this is an urgent matter. Is there anyone from the team that can help expedite review?
@anothercohen My recommendation would be The Top, then Kin for a cocktail.
Other honorable mentions:
Swamp if you want nostalgia.
Cry Baby's
Indian Street Food if you want Dosa
Dragonfly for sushi
Germain's for a chicken sandwich
@sandislonjsak If you plan your projects well, you can review much faster because you have an expected outcome. Deviations and regressions become blatantly obvious.
@nikitabier@benjitaylor The most important action you can take to improve this application is to verify each account is a real human being or business entity. End the bots. End the slop.
@JohnThilen@doodlestein It's a choice, of course. However, to avoid disruption, spinning up a worktree to debug or review a PR is an efficient way to switch contexts. It works well for our team, but at the end of the day, different strokes!
I use worktrees to build across many projects at once.
@doodlestein This is likely why you're not resonating with their recommendations. When working with a team of humans, each of which may have a team of agents, the paradigm changes. Worktrees are absolutely necessary for quick code reviews, parallel work, etc.
@PovilasKorop Spend more time planning. Then, the review is more about glaring deviations from the plan. Furthermore, with proper configuration and agentic review, those deviations happen less and less.