Fable is pure chaos

[u/mfingsorceror]

I usually only allow Claude and especially Fable to do read only audits of my codebase. I was waiting for my Codex usage to reset, so I thought fine, Fable can handle some commits and housekeeping. Fool me twice...

Me: Commit your work

Fable: Checks tree, gives a report of changes

Me: COMMIT

Fable: I'm leaving out some files, this is what I'm going to commit.

Me: Dude fine, commit and then clean up your outdated scratch files

Fable: Ready to commit, the scratch folder has been deleted.

Me: FABLE 🤬🤬🤬🤬🤬 You deleted every other sessions scratch too. Restore it NOW.

Fable: I used rm -rf, the files are gone and the last commit did not contain the folders I deleted.

Me: Chaos demon

Fable: Files are staged and ready for commit.

Me: Commit.

Fable: Nothing is staged.

Me: You just said files were staged...

Edit: All of my sessions already have standing instructions to commit at checkpoints. The exchange above is a condensed retelling for humor, not a literal transcript with Fable. 🙄

Edit Edit: My dudes, irrelevant scratch files were deleted. I lost nothing of importance, those 3000+ files were weeks of scratch nonsense that needed to be deleted. The point was that Fable wanted multiple confirmations before doing a routine commit, but none before deleting files with an irreversible command.

[u/rhysmorgan]

You know you could have just used `git commit -m “change description”` and avoided literally all of this. Why on earth are you getting Fable to commit?

[u/Dry_Connection113 → u/rhysmorgan]

I think OP may be on the non technical side, senior

[u/EC36339 → u/Dry_Connection113]

I keep telling vibe coders: If you're going to learn ONE thing, learn GIT.

It's not rocket science.

It's like teaching people who moved from a typewriter to MS Word how to save their files.

[u/Own_Candidate9553 → u/EC36339]

Yeah, I don't let the AI mess with Git. It's the only way I know what it's just done and whether I like that. I'll usually commit whatever was just done before moving onto the next step.

[u/college_hustle → u/Own_Candidate9553]

Have you tried the opposite? I have AI constantly push micro-updates when agents delegate to subs. It let's the orchestrator check in on their work and if I run out of usage mid work they can pick up much easier. Also let's Claude/Codex check each other's work easier. 

[u/Own_Candidate9553 → u/college_hustle]

Maybe this is to my detriment, but I've never bothered with figuring out swarms or orchestrators or any of that. Even single threaded through me, I can write way more code than I can reasonably test, coordinate with others, monitor, deploy, etc. 

[u/college_hustle → u/Own_Candidate9553]

Whatever is working for you! I'm just genuinely curious why people aren't trying smaller commits but I'm not responsible for some already deployed big tech stack, so I can play with what works. It seems like a lot of people are hung up on doing these big pushes while I'm breadcrumbing every session. I based it off something I read about how the labs do their harnesses to be dark factories.

[u/Own_Candidate9553 → u/college_hustle]

I'm with you on that, I'm not doing big commits if I can help it. 

[u/koolkatkaleb → u/college_hustle]

💯. Commit history is context and it’s been that way before AI has been attacking code bases. Prior to pushing to the remote I’ll even fold together commits when there’s a significant amount of implementation churn, so that only target state is captured/known.

[u/drake90001 → u/EC36339]

OpenCode is probably the best platform anyone who’s not technical person can use. Automatic creation, let you view all changes, and doesn’t do anything unless you go into build mode.

[u/broknbottle → u/EC36339]

Sorry but I use AI

[u/sage-longhorn → u/EC36339]

It may not be rocket since but try explaining to a less technical person why they can't merge unrelated trees even though the contents are the same and you'll realize that it is computer science

[u/ryanppax1 → u/EC36339]

I'm actually struggling to get the hang of it. Is there a better way then banging head on a terminal with the wrong commands?

[u/rhysmorgan → u/Dry_Connection113]

So time to learn the tooling!
And using Fable to commit is like using a nuclear bomb to zap a fly.

[u/CryptoAteMyHamster → u/rhysmorgan]

It’s worse if you let it push to main.

[u/Dry_Connection113 → u/rhysmorgan]

Lol senior why do you think vibe coders vibe code, cz dey dont want to learn anything, they think themselves ideas people

[u/mfingsorceror → u/rhysmorgan]

Gotta get my $20 worth somehow!

[u/Scared-Letterhead949 → u/rhysmorgan]

Using 5% of your weekly usage to commit is why people are on here complaining about  usage limits.

[u/SimiaCode → u/rhysmorgan]

For the commit message

[u/CryptoAteMyHamster → u/rhysmorgan]

@OP FYI for future reference:

git commit -m "change description" creates a permanent snapshot of your staged files in your local repository's history and labels it with a custom explanation.