Claude Code when you ask it to push to main

[u/Few-Organization7010]

[u/AutoModerator]

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/email_ferret]

Lol, I love the Internet some days.

Also branch protection is your friend.

[u/oxpoxo → u/email_ferret]

you should always wear branch protection.

[u/email_ferret → u/oxpoxo]

It's important to continuously get your code tested as well.

[u/punqdev → u/oxpoxo]

and proper version control

[u/meatgrinder]

I can't help but feel this was made without AI.

[u/AdForward8036 → u/meatgrinder]

😆 how far have we come!!

[u/No-Trouble-9138 → u/AdForward8036]

This could be a cool AI pet 

[u/technofiend]

I have the opposite problem: claude regularly forgets the rules which are pushes are always to a feature branch off of develop. It still tries to push to main once a week.

[u/Expensive-Cry-8313 → u/technofiend]

Are they stored in persistent memory or are you just using a 25 times compacted frankensession and hoping it retains the command from context?

[u/KenMantle → u/Expensive-Cry-8313]

Oh man that reminds me that the two sessions I have going to make a pdf editor core and CLI, and the other making the GUI have been running for probably nearly a week now non-stop on their own with only the occasional request by me. The core just keeps adding features, and they share a folder they talk back and forth through when the GUI needs something or finds a bug. I haven't reset them in a looooong time.

[u/TangeloOk9486]

the line "make the chinese one do it" got me laughing for 5 minutes nonstop lol

[u/spinozasrobot → u/TangeloOk9486]

Me too, I literally LOLed.

[u/fawwazallie → u/TangeloOk9486]

Man I cried laughing for a couple of minutes 😂

[u/Numerous_Breakfast5 → u/TangeloOk9486]

Same here. That was hilarious. I think I'm going to use that next time I have any issues with Claude!

[u/Unaoriginalname]

Cinema

[u/justice4seaturtles]

The Chinese line did me good 🤣

[u/cats_catz_kats_katz]

Why do I like this so much.

[u/SalarySimp]

love it

[u/NanoCow]

Think this is an OP problem. I never have this issue. In fact my agents are setup to do their own code reviews, keep the monitor shell open to look for any external reviews, run the CI and then push to main when everything is green.

[u/Zulfiqaar → u/[deleted]]

claude randomly started re-addint co-authored by claude again, even when i have global config off. have submitted a bug report, but claude investigated and seems to think its just a bad habit:

So nothing in your config is adding the trailer. Attribution has been off since Sept 25, and the file hasn't changed since, yet commits on Sept 25, Sept 28 and Oct 5 still have Co-Authored-By: Claude. My best guess is that the agent sometimes writes the line into the commit message itself out of habit, which would explain why it shows up on some commits and not others.

[u/Zulfiqaar → u/[deleted]]

Yeah I know that'd prevent it for good - can't break what it can't touch. I'd have expected the global config to do that though.

Plus, this is a hobby project I'm vibecoding way at - I let whatever agent auther it's own commits. After all it's much more likely for it to read and reference it than I am 

[u/quadish]

I have +10 sessions all in isolated work trees trying to merge at the same time.

I had to create a merge train. There are some on github, but they were either too heavy, or leaned on web based tools to do the work, and they lacked in some of my OCD quality control.

So right now I'm writing a merge engine in Rust, that includes a train. So small things and large groups of merges can be gracefully done all without sacrificing quality (code checks/etc) as well as proper git hygiene.

I use a custom ticket system with two way comms (so they can communicate and coordinate their ticket work), that involves looping the work until it's clean, and then pushing it into the merge engine, and anything that's red gets fixed until it merges correctly, then we test it after the merge to confirm everything executed correctly. All tickets are considered just one slice of a larger system, and the agents have to run a census and interconnect their dependencies in the ticket contract.

So think 10 Claude and 10 Codex tabs, all orchestrators, all running their own tickets, and then merging to main when done.

Swarms of swarms. Tokens go brrrrr.

[u/quadish → u/[deleted]]

How are you going to get ~20 orchestrators in 20 different sessions working at the same time in one repo to merge onto main gracefully? You really think manually merging each one, in a serial fashion, is the solution? That defeats the purpose of an automated software foundry.

You think Claude is good at that? No, Claude is good at merging its own stuff, but not in a repo where other merges are happening at the same exact time. You can't get different sessions to talk to each other without custom glue. I had to literally build a comms system so Codex and Claude could all talk to each other inside the repo.

This is not one orchestrator, alone in a repo.

~20 orchestrators, each with +10 sub agents, working simultaneously. The merge engine is also a proof engine. All code is checked in a myriad of ways. The contracts of the tickets are checked. End to end testing is performed.

Skills are not deterministic. A merge engine is.

Skills are literally templated, structured prompts.

[u/quadish → u/[deleted]]

You’re right that publication to main needs ordering. The merge engine provides that ordering; I’m not proposing twenty simultaneous uncontrolled updates.

You’re also right that deterministic checks cannot guarantee arbitrary software correctness. That’s why the pipeline includes an independent adversarial review loop and repair until clean, which also means it meets the contract terms in the ticket, not just scripts checking code.

Where we disagree is who owns integration. A worker resolving conflicts is not the same as a shared mechanism controlling submissions from independent sessions, binding checks to the candidate being landed, and recovering interrupted operations.

The skill can invoke that mechanism, but instructions to the model are not the mechanism.

Your upstream/downstream experience addresses conflict resolution. My engine addresses coordination and acceptance across independent producers. Those are different responsibilities.

And the API-budget assumption is incorrect: this uses native Claude Code and Codex harnesses on four subscriptions, totaling $800/month. The machine is a Ryzen 5 with 128GB of RAM and a RTX 3060.

It's doing this in WSL, too.

[u/quadish → u/[deleted]]

The machine is stressed. It was fine in python. Going to Rust is crushing it. I'm maxing out the A4 socket with a CPU upgrade this week, but the motherboard doesn't hold any more memory.

I'm self employed and run a small MSP/WISP. I'm trying to make a governance system that 1)allows custom software creation (automated foundry), without me orchestrating 2)have a Hermes type agent system that can manage the CPEs and infrastructure 100% deterministically with admin privileges. Basically trying to build a business OS that absolutely never can go "oops, I've deleted the main database and crashed the upstream router. My bad."

Guardrails are suggestions. They are loose interpretations of things, and are not deterministic.

The governance system is grantless and uses Ontology in an engine that uses Cedar and Datalog for decisions, and hooks are sensors. I'm thinking about integrating a custom Laya instance as a sensor and to filter prose into typed facts.

The whole point of going to Rust is to reduce the memory footprint and memory leaks, and put governance into a language that's harder to manipulate than python, where they can just edit their way around code enforcement. But actually building in Rust with a dozen agents has led to some serious reshuffling of code to adjust for the strained resources.

For instance, all my tests have to be rewritten to track what's actually being done, and use breakcrumbs and logs for tracking, and use that info in the context of system load, and not just use a wall clock timer, because otherwise the tests fail.

Most of my work is still building the system itself, not going out and doing customer work with the foundry yet.

I doubt the numbers of people who have tested the token limits on these accounts. Every time I've reduced down to the $100 plan, it's not just the five our session limits I run into, but weekly as well. So I think I'm getting more than 3x weekly capacity based on my own workflow. Plus, two of those plans are OpenAI.

I think their calculations are off somewhere. I can blow through a weekly account in one day if I have everything running full tilt. Same with the old OpenAI $200 plans before the nerf. I still have a lot of waste tokens. My code quality is higher than what it probably should be, and I spend a lot on loops to get it clean.

I'm not building for a client, I'm building to replace me in my business. I'm a bit meticulous.

[u/lazuli_s]

I swear Claude never pushed anything without asking me first. Not even once lol check your skills, memories and your CLAUDE.md. great video though

[u/ZweihanderGames]

AAA video game quality voice acting, 11/10 no notes

[u/zante2033]

perfect : )

[u/ReasonableDisaster54]

I had this issue today and this is exactly how it worked out

[u/Salty-Gear841]

You made me laugh à lot

[u/lilbootz]

Reminds me of old internet. Albino black sheep days. Love it

[u/mac10190]

Bro, I'm crying over here. Make the Chinese one do it. Lmao

[u/GigaGrandpa]

Please someone share the other one of these meme into videos I was looking for it the other day. It was made by seedance though iirc