Alternatives
Products that do what Lens does
See and manage your entire Claude Code config in one place
- 1CM
I use Claude Code across multiple projects with different conventions and some shared repos just as it so happens to be the real world. Managing the config files (.claude/rules/, mcps.json, settings.json) by hand got tedious, so I built a local web UI for it. This one started out as claude-config but migrated to coder-config as I'm adding others (Gemini, AG, Codex, etc). Main features: - Visual editor for rules, permissions, and MCP servers - Project registry to switch between codebases - "Workstreams" to group related repos (frontend + API + shared libs) with shared context -…
Jan 2026 · github.com
- 2
- 3
- 4PM
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
- 5
- 6OS
2024 · github.com
- 7
Let Claude make permission decisions on your behalf
Mar 2026 · claude.com
- 8
- 9
Store, review, and share your Claude Code sessions
Mar 2026 · bench.silverstream.ai
- 10
- 11
- 12CC
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
- 13CC
I built this for myself but I figured why not share. The aim of CCM is to be able to fully manage all Claude Code configuration files, both globally and those in your project. Some neat features: - Manages your CLAUDE.md, rules, hooks, agents, memories and so on. - Elevate memories to rules - Copy/Move any asset from one scope to another, or elevate it to global scope - Install marketplaces and plugins The full app is embedded right on the site as a demo so you can try it out. I'm happy to receive feedback, I know it's not perfect. Thanks for taking a look.
Apr 2026 · claude.ldlework.com
- 14
- 15
- 161O
Hi, we're Sergey and Serafim. We've been building dev tools at 21st.dev and recently open-sourced 1Code (https://1code.dev), a local UI for Claude Code. Here's a video of the product: https://www.youtube.com/watch?v=Sgk9Z-nAjC0 Claude Code has been our go-to for 4 months. When Opus 4.5 dropped, parallel agents stopped needing so much babysitting. We started trusting it with more: building features end to end, adding tests, refactors. Stuff you'd normally hand off to a developer. We started running 3-4 at once. Then the CLI became annoying: too many terminals, hard to…
Jan 2026 · github.com
- 17CR
Jan 2026 · github.com
- 18
- 19
- 20
- 21AC
Dec 2025 · github.com
- 22
- 23CM
Every MCP tool call dumps raw data into Claude Code's 200K context window. A Playwright snapshot costs 56 KB, 20 GitHub issues cost 59 KB. After 30 minutes, 40% of your context is gone. I built an MCP server that sits between Claude Code and these outputs. It processes them in sandboxes and only returns summaries. 315 KB becomes 5.4 KB. It supports 10 language runtimes, SQLite FTS5 with BM25 ranking for search, and batch execution. Session time before slowdown goes from ~30 min to ~3 hours. MIT licensed, single command install: /plugin marketplace add mksglu/claude-context-mode…
Feb 2026 · github.com
- 24RT
This project (Agents Observe) started as an exploration into building automation harnesses around claude code. I needed a way to see exactly what teams of agents were doing in realtime and to filter and search their output. A few interesting learnings from building and using this: - Claude code hooks are blocking - performance degrades rapidly if you have a lot of plugins that use hooks - Hooks provide a lot more useful info than OTEL data - Claude's jsonl files provide the full picture - Lifecycle management of MCP processes started by plugins is a bit kludgy at best The biggest takeaway is…
Apr 2026 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →