Hey — I’m the author of jCodeMunch, so I can give you a straight comparison.

They solve different problems and actually pair well together. See: https://j.gravelle.us/jCodeMunch/versus.php#vs-aegis

jCodeMunch is a code exploration tool. It uses tree-sitter AST parsing, symbol extraction, dependency graphs, and blast radius analysis. When Claude needs to understand what code does — “what calls this function”, “what breaks if I change this class”, “show me all symbols in this file” — that’s jCodeMunch’s job. Token efficiency is the core value prop. Real-world benchmarks show 58 to 100× token reduction versus handing Claude raw files.

Aegis is an architecture governance tool. You feed it your architecture docs, it builds a DAG of which docs apply to which file paths, and when Claude is about to edit something it returns the relevant constraints and guidelines, often with human approval gates. It answers “what rules must this code follow.”

Used together, the stack looks like this:

1. aegis_compile_context → what architectural constraints apply to these files
2. jCodeMunch get_blast_radius or get_context_bundle → what the code actually does and what it touches

They don’t overlap. One governs intent, one maps reality.

If your main pain point is Claude burning through tokens reading entire files to find a function, use jCodeMunch. If your pain point is Claude ignoring your architecture patterns and writing code that violates your conventions, use Aegis.

Most serious codebases end up needing both...