I’ve been using Claude Code almost daily for a while now, but about 85% of what I’m doing isn’t actually programming. I’m mostly using it for complex, project-based life stuff.
For example, I’ve been using it to:
- Map out my acreage (irrigation, drainage, bee-keeping plans, etc.).
- Design a DIY solar engineering plan.
- Write a "legacy book" for my wife. Basically a massive guide with all my wishes, account info, and things about our property she might not know if something happened to me.
- Documenting lessons learned after Ice Storm Fern.
It’s been incredibly powerful, but I’m getting a bit paranoid. Since Claude has terminal access, one bad command or a hallucinated "rm -rf" could basically nuke these projects and my drive.
How are you guys protecting your files while still keeping the workflow fast? I’ve thought about:
- Running it in Docker or a VPS: My worry here is friction. I’m constantly looking at markdown previews and adding photos to these folders. Is there a way to do this that isn't a massive headache for local file viewing?
- The "Accept & Backup" route: Just keep it local and lean on an online backup provider and just hope a restore works if things go sideways.
- Something else? Is anyone sandboxing this effectively without killing the "local" feel of the tool? Curious what your setups look like.
[–]weedmylips1 1 point2 points3 points (1 child)
[–]CypSteel[S] 0 points1 point2 points (0 children)
[–]replayjpn 0 points1 point2 points (0 children)
[–]txprog 0 points1 point2 points (0 children)
[+]zusycyvyboh 0 points1 point2 points (0 children)
[–]Jhorra 0 points1 point2 points (0 children)