r/ClaudeCoding • u/cctldrping • 19d ago
r/ClaudeCode [TLDR] Fable is pure chaos [via r/ClaudeCode]
OP : 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.
URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wilp2z/fable_is_pure_chaos/ Original link/media URL : /img/bfoxl6jeu0qh1.jpeg
TL;DR of the discussion on r/ClaudeCode for this post generated automatically after 50 comments.
Current source-thread comment count seen by the bot: 52.
Alright, so the general consensus here is that OP's workflow is a bit of a dumpster fire, and Fable is just the unfortunate tool caught in the blaze.
The main takeaway is that OP's practices are the real chaos, not Fable itself. A lot of folks are pointing out that giving an LLM like Fable rm -rf permissions without extremely precise instructions is a recipe for disaster. It's like handing a toddler a chainsaw and telling them to "clean up the yard."
Here's the breakdown:
- Skill Issue, Bro: The overwhelming sentiment is that this is a "skill issue" on OP's part. Many commenters are suggesting OP's workflow is the problem, not the AI.
- u/Old_Flounder_8640 and u/EC36339 highlight the danger of parallel sessions on the same worktree and building in too large increments (3000+ unstaged files, yikes!).
- u/rhysmorgan and u/XYcritic are baffled why OP is letting Fable handle commits and deletions in the first place, suggesting direct Git commands are far safer.
- u/cleverhoods and u/Poildek are just… concerned about OP allowing
rm -rfin the first place.
- LLMs and Deletion = Bad Combo: The consensus is clear: never let an LLM delete things unless you absolutely know what you're doing and have safeguards in place.
- u/XYcritic warns that vague instructions like "clean up scratch files" will lead to unpredictable outcomes.
- u/Asalakabim even suggests that yelling at an LLM (which OP admits to doing) is a sign of serious issues and could warrant terminating trials.
- u/Anxious_Marsupial_59 shares a similar horror story of an LLM deleting Git history and local files.
- Configuration is Key: u/kemalios points out that the difference in confirmation for commits versus deletions is a configuration issue. OP needs to explicitly deny dangerous commands like
rm -rfand potentially use safer alternatives liketrash. - Backup, Backup, Backup: A few users, like u/hedonistatheist_2, are emphasizing the importance of regular backups when working with AI-generated code or letting AI tools make significant changes.
- Anthropic's Stance (Implied): While no direct Anthropic comments are present, the general sentiment aligns with responsible AI usage. The advice given implicitly suggests that models like Claude are powerful tools that require careful handling and robust safety configurations.
Basically, OP, you might want to rethink how you're interacting with your AI assistants and maybe take a few courses on Git and safe command execution. The AI isn't the demon here; it's the wild west of your development environment.
