Alternatives
Products that do what AwsomeContext does
122+ engineering rules for Claude Code, retrieved in <5ms
- 1
- 2
- 3CM
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
- 4
- 5
Put Claude Code tasks on autopilot with smart routines
Apr 2026 · anthropic.com
- 6
Store, review, and share your Claude Code sessions
Mar 2026 · bench.silverstream.ai
- 7
Let Claude make permission decisions on your behalf
Mar 2026 · claude.com
- 8
- 9
- 10SC
I got tired of Claude Code forgetting all my context every time I open a new session: set-up decisions, how I like my margins, decision history. etc. We built a shared memory layer you can drop in as a Claude Code Skill. It’s basically a tiny memory DB with recall that remembers your sessions. Not magic. Not AGI. Just state. Install in Claude Code: /plugin marketplace add https://github.com/mutable-state-inc/ensue-skill /plugin install ensue-memory # restart Claude Code What it does: (1) persists context between sessions (2) semantic & temportal search (not just…
Dec 2025 · github.com
- 11
Push events and chat with Claude Code via Telegram & Discord
Mar 2026 · code.claude.com
- 12AC
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
- 13CC
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
- 14RG
Hey HN! I'm José, and I built Recall to solve a problem that was driving me crazy. The Problem: I use Claude for coding daily, but every conversation starts from scratch. I'd explain my architecture, coding standards, past decisions... then hit the context limit and lose everything. Next session? Start over. The Solution: Recall is an MCP (Model Context Protocol) server that gives Claude persistent memory using Redis + semantic search. Think of it as long-term memory that survives context limits and session restarts. How it works: - Claude stores important context as "memories" during…
Oct 2025 · npmjs.com
- 15FO
2025 · github.com
- 16OS
2024 · github.com
- 17
- 18CM
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
- 19
- 20CM
We built CodeYam Memory because Claude Code kept making the same mistakes on our codebase. Our claude.md files quickly got stale and maintaining by hand or with Claude wasn’t sufficient. While digging into this we found that Claude has a native rules system that allowed us to target specific parts of our repo with path matching. This was ideal for our use case but trying to manage these rules by hand was already not working and would be even harder with more granular, targeted rules. CodeYam Memory uses a background agent to review your coding session transcripts, identifies confusion…
Mar 2026
- 21CC
2025 · cloudcoding.ai
- 22
- 23GU
Gigacode is an experimental, just-for-fun project that makes OpenCode's TUI + web + SDK work with Claude Code, Codex, and Amp. It's not a fork of OpenCode. Instead, it implements the OpenCode protocol and just runs `opencode attach` to the server that converts API calls to the underlying agents. We build this to scratch our itch of being able to rapidly switch between coding agents based on the task at hand. For example, we find that: - Claude Code is the best executor & fast iterator - Codex (high) is the best for complex or long-running tasks - OpenCode for fine-tuned, do-exactly-as-I-say…
Feb 2026 · github.com
- 24HC
Hey all! Few weeks ago we realized AI models are now so good you don't need to babysit them anymore. You can kick off a coding task at lunch and Claude Code just... works. But then you're stuck at your desk steering it. We were joking around - wouldn't it be cool to grab coffee and keep chatting with Claude from your phone? Next thing you know, 4 of us are hacking on weekends to make it happen. Dead simple to try: "npm install -g happy-coder" then run "happy" instead of "claude". That's it. We had three goals: * Don't break anyone's flow - Use Claude Code normally at your desk, pick up your…
2025 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →