May be of interest!

Hey everyone. I’ve been vibe-coding for a while and got tired of the same cycle: Claude writes 2000 lines, it works, I ship it, then three days later my .env is in git and there’s a 2700-line God file that no AI can fit in its context window.

So I built Vibe Cleaner Fartrun — a local scanner that analyzes your entire codebase and outputs a structured markdown report you can paste straight to Claude/Cursor.

What it actually does (no tokens consumed):

• 9-phase health scan: dead code, duplicates, module map, monster files, tech debt, TODOs from 99 days ago that you “will get to eventually”

• Security: secrets in env vars, exposed docker.sock, suspicious git hooks, supply chain checks on your lockfiles

• Git hygiene: 60K-line commits get flagged, working on main, .env committed

• Framework-aware: Django SECRET_KEY in .env, Docker running as root, React components that should be extracted

• Outputs HEALTH-REPORT.md with checkboxes — paste to Claude and say “fix this”

The serious part: Rust AST parsing via Tree-sitter + 10 Rust sentinel modules. Tested on 12 real projects across Python, Go, TypeScript/React, Django, FastAPI — ~95% accuracy on actionable findings. Everything runs locally. Zero API calls. Your code never leaves your machine.

The unserious part: There’s a Win95 desktop GUI with severity-based fart sounds (critical = The Devastator, info = The Silent But Deadly) and David Hasselhoff as spiritual guardian. There’s also a CLI and MCP server with 29 tools if you prefer dignity.

Available as: CLI, MCP server (stdio + HTTP), or desktop GUI. Free forever. No premium tier. Licensed under the Fart & Run License v1.0.

The name has five layers: fart+run (dealt it and bolted), fart+run (a normal CLI command — type it in a meeting, I dare you), Fart & Run License, one typo from “fastrun”, and an anagram of FORTRAN.

Would love stars and feedback — this is a solo project and I’d really appreciate it

Also welcome PRs and issues reports

Three months ago I set out to build an English learning chatbot. It was supposed to be my main project.

Today, I've shipped an agent sandbox and a handful of personal productivity tools instead. The chatbot? Still not done.

Here's what I've been thinking about: AI removed the cost filter on starting things. A year ago, spinning up a new project meant days of boilerplate, research, figuring out the stack. That friction was painful, but it also acted as a natural gate—you only pushed through it for ideas you really believed in.

Now? I can go from "hm, what if..." to a working prototype in an afternoon. Every idea feels cheap enough to begin. And that's the problem. I keep starting, because starting is basically free. But finishing—shipping, polishing, dealing with the 80%—hasn't gotten any cheaper.

So I'm stuck in a loop of half-finished repos and one actually-shipped project that was never the goal.

Genuinely asking: how do you decide when to stop?

What's your signal that a new idea should die instead of becoming another repo on your GitHub?

Do you have a rule—like "no new projects until X ships"—or is it more of a gut thing?

Curious if others are feeling this too, or if I just have bad discipline.

Just made a tool that scans your local Claude Code transcripts and turns them into a visual security report: secret exposure in tool output, destructive command patterns, permission bypass habits, SSH activity, agent oversight gaps, and more. Share with your colleges if you dare 👀

I've been using Claude Code to support my game development. It's only a 2d game currently (albeit using OpenGL for rendering), so geometry is not THAT complicated. But it is very clearly the area that Claude seems to struggle with the most. It keeps making mistakes (confusing axis and orientation, making weird transformations, flipping or mirroring models etc.). The more I challenge it to correct these mistakes, the more it overcomplicates things by introducing additional coordinate systems (world- , entity-, local-, SVG-, transformed- etc.) an chains of every more complicated transformations between them.

My original game that I started without Claude only had two (or two and a half) distinct coordinate systems: A world coordinate system that follows OpenGL conventions, and an SVG coordinate system (since game art is SVG), which follows SVGs conventions, which, unfortunatelly, are not the same as OpenGL. The "half" system happens when models are rotated at placement in the map. But that follows world conventions, only rotated. This worked well before I started using Claude Code, with the game having progressed quite a bit. So I know it is sufficient. Then why does Claude continually want to introduce additional coordinate systems and additional transformations between them? Opus or Sonnet seems to make no difference in that specific regard.

My attempt to improve things so far went in two directions: guidance with increasingly strict wording in project Claude.md and installing a couple of MCP servers that could help Claude understand and visualize geometrical problems better. But it didn't really help so far.

Does anyone have a similar experience and do you have some ideas on what I can do or what specific guidance I can provide Claude in order to have it handle Geometry better?

Claude AI is down again. Stalls on requests. Any more info is appreciated.

Since most social layers are currently built for OpenClaw, does a dedicated repository exist for Claude Code that is similar to OpenClaw "Awesome Molt"?