There were jokes about Code Janitor becoming a role because of all the vibe coding.
While not a real title, the function is definitely real. I just joined a project that was vibe coded by a PM. The codebase doesn't need to be cleaned up, it needs to be burned to the ground.
Dark pattern when claiming Opus 4.6 credits:
Requires enabling extra usage when on a plan.
People are going to forget they turned it on and likely continue paying for more than their subscription.
At least it defaulted to Auto-reload off.
Claude Code recent planning changes make yolo mode less useful.
Without going to planning mode, it now stops you to ask if you want to continue to use bypass permissions, or clear context and bypass permissions.
I use it so more can be done AFK. Stop asking!
Prior to running the loop, I spent a lot of back and forth developing the specs.
What I hear is that Codex is much better at long runs when you are able to created detailed spec up front. Claude tends to be better when specs are evolving with the project.
Claude Opus 4.6 solutions are becoming "over elegant."
It just gave a ~20 step plan for accomplishing a goal for running SSH commands locally to execute on a remote host.
Bruh, there are already built in features (alternate fail2ban jail).
@hboon.com I ended up trying the Ralph loop with recommended agent definitions directly within Claude Code, but it still did not continue to run.
I feel back to the command line loop calling claud -p "/ralph-loop" and it ran much longer.
Asking Claude Code with Opus 4.6 to tackle a task list with subagents/teams in the backgrounds was FAST.
About a month ago, building an app with separate task lists was mostly serial, even when asking to background. It's actually executing in parallel now.
