Alternatives
Products that do what ClaudeFilePrep – I was tired of dragging files into Claude –> automated does
I built a Python tool that recursively collects files from nested project directories and prepares them for Claude AI analysis. It can either preserve directory structure or flatten everything with path-encoded filenames. No dependencies, just stdlib. Particularly useful if you're working with multiple files scattered across different folders and tired of constant drag-and-drop.
- 1

- 2

Store, review, and share your Claude Code sessions
Mar 2026 · bench.silverstream.ai
- 3

- 4

- 5

- 6

- 7

- 8

- 9

Let Claude make permission decisions on your behalf
Mar 2026 · claude.com
- 10CF
Claude Code deleted my research and plan markdown files and informed me: “I accidentally rm -rf'd real directories in my Obsidian vault through a symlink it didn't realize was there: I made a mistake. “ Unfortunately the backup of my documentation accidentally hadn’t run for a month. So I built claude-file-recovery, a CLI-tool and TUI that is able to extract your files from your ~/.claude session history and thankfully I was able to recover my files. It's able to extract any file that Claude Code ever read, edited or wrote. I hope you will never need it, but you can find it on my GitHub…
Feb 2026 · github.com
- 11CC
Continuous Claude is a CLI wrapper I made that runs Claude Code in an iterative loop with persistent context, automatically driving a PR-based workflow. Each iteration creates a branch, applies a focused code change, generates a commit, opens a PR via GitHub's CLI, waits for required checks and reviews, merges if green, and records state into a shared notes file. This avoids the typical stateless one-shot pattern of current coding agents and enables multi-step changes without losing intermediate reasoning, test failures, or partial progress. The tool is useful for tasks that require many…
Nov 2025 · github.com
- 12AC
Dec 2025 · github.com
- 13

Multi-agent review catching bugs early in AI-generated code
Mar 2026 · claude.com
- 14

Use Claude to build, edit & refine PowerPoint presentations.
Feb 2026 · claude.com
- 15
Claude Code auto-fix ▲370Auto-fix PRs in the cloud while you stay hands-off
Mar 2026 · code.claude.com
- 16

- 17

- 18OS
2024 · github.com
- 19CC
Hi all! I normally work on the PyTorch project but I've been on baby leave for the past month, so I've been playing around with AI as a user rather than a framework implementor. I really liked the agent experience with Claude Code, but I couldn't really justify spending so many dollars on API costs for random side projects. I already pay for a Claude Pro subscription though, and it turns out you can simulate many of Claude Code's features with an MCP. If you have a Pro subscription, check this out! I think it really captures the Claude Code experience quite well, without forcing you to pay…
2025 · github.com
- 20CR
Jan 2026 · github.com
- 21FO
2025 · github.com
- 22IB
Hi HN, I built this because I got tired of the Claude Code CLI hiding details from me. Recent updates have replaced critical output with summaries like "Read 3 files" or "Edited 2 files". To see what actually happened, I was forced to use `--verbose`, which floods the terminal with unreadable JSON and system prompts. I wanted a middle ground: *Full observability without the noise.* `claude-devtools` is a local Electron app that tails the session logs in `~/.claude/` to reconstruct the execution trace in real-time. *Unlike wrappers, it solves the visibility gap in your native…
Feb 2026 · github.com
- 23AC
We needed something like --dangerously-skip-permissions that doesn’t nuke your untracked files, exfiltrate your keys, or install malware. Claude Code's permission system is allow-or-deny per tool, but that doesn’t really scale. Deleting some files is fine sometimes. And git checkout is sometimes not fine. Even when you curate permissions, 200 IQ Opus can find a way around it. Maintaining a deny list is a fool's errand. nah is a PreToolUse hook that classifies every tool call by what it actually does, using a deterministic classifier that runs in milliseconds. It maps commands to action types…
Mar 2026 · github.com
- 24PM
I built a lightweight project management workflow to keep AI-driven development organized. The problem was that context kept disappearing between tasks. With multiple Claude agents running in parallel, I’d lose track of specs, dependencies, and history. External PM tools didn’t help because syncing them with repos always created friction. The solution was to treat GitHub Issues as the database. The "system" is ~50 bash scripts and markdown configs that: - Brainstorm with you to create a markdown PRD, spins up an epic, and decomposes it into tasks and syncs them with GitHub issues - Track…
2025 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →