Choose the scope
Discover the repository and its supported targets. Decide which source snapshot answers your question.
Code understanding for you and your agent
Find the code.
Follow the thread.
Untangle an unfamiliar codebase. Find relevant code, explain how it fits together, and follow each answer back to its source.
Kotlin · Java · Rust · Python All language support →
macOS · Linux · WSL2v0.11.1 · Public pilot
curl -fsSL https://codeclew.github.io/codeclew/install.sh | shThen run clew skill install to connect your agent.
Requirements & updates
Git and Python 3.11+. Source documentation for Python, Java and Kotlin requires no application build. Optional Kotlin compiler analysis requires JDK 21; other compiler profiles use their project toolchains. Prebuilt for macOS arm64/x64 and Linux x64 (glibc 2.35+). On Windows, use WSL2 and keep projects in its Linux filesystem.
Update with clew upgrade. Installation and update instructions ↗
Pick a loose end
A clearer path through your code.
01 / Find
Get to the relevant code
Start with a question. Inspect a focused set of declarations and the source behind them.
Follow the walkthrough → 02 / ExplainKeep service knowledge useful
Read internal flows and linked decision tables alongside service explanations. Keep the supporting source and review limits visible.
Explore service documentation → 03 / ReviewMake sense of saved edits
Compare saved Kotlin or Rust changes with HEAD. Inspect changed code and supported direct connections.
Open an example report →Source you can openInspect the code behind a finding.
Focused contextRetrieve relevant pieces in bounded steps.
Visible limitsSee what is known and what still needs checking.
Local analysisCodeclew makes no automatic code upload.
Start with one useful question
Small question.
Followable answer.
Install Codeclew and its skill, then ask your agent: “Find where this behavior starts and explain it with source references.”
Find the code
Retrieve declarations, source and the relationships supported by that language.
Follow the evidence
Open the exact source. Keep observed facts, interpretations and unanswered questions visible.
Use what you learned
Review a change, explain a behavior or maintain service documentation your team can inspect.
Language support · v0.11.1
Different languages.
Honest levels of detail.
All of these profiles can help you inspect code. Compiler analysis resolves supported identities and relations; syntax analysis records what is written in the selected source.
| Language | What you can inspect | Managed changes |
|---|---|---|
| KotlinJVM 1.9–2.4 · Gradle / Maven | Compiler-backed declarations, source and supported relations. Compatibility differences remain explicit. | Pilot for exact 2.4.10 + Gradle, one compilation. Other profiles are read-only. |
| JavaJDK 17+ · Gradle / Maven | Compiler-backed declarations, calls, types and Spring entry points. | Read-only preview. |
| RustOne Cargo target | Bounded syntax and declaration ranges. No resolved call graph; cfg and macros remain explicit limits. | Conditional pilot with Cargo validation. |
| PythonExplicit import and source roots | Bounded syntax, declarations, imports and call names. No runtime import or type resolution. | Conditional pilot with native Python validation. |
| TypeScript / JavaScriptProject-local TypeScript 5 · tsconfig | Compiler facts for TypeScript and checked JavaScript. Unchecked JavaScript has weaker, explicit evidence. | Read-only preview. |
Conditional changes: Rust and Python require a reviewed diff, successful native validation and acknowledgement of unresolved obligations. Passing tests does not turn syntax facts into compiler proof.
Feature scope: saved-edit reports cover Kotlin and Rust. Service documentation in v0.11.1 supports committed Python, Java and Kotlin source without a build, with optional compiler enrichment, service sections, internal-flow visuals, linked decision tables, entity dataflows and protected notes. Multi-repository analysis supports 2–8 repositories and is read-only.
Check your installed version with clew capabilities --human. Exact profiles and setup ↗
Your code. Your environment.
Curiosity can
stay local.
Codeclew analyzes code locally and needs no hosted model or API key. Your chosen agent writes the explanations; its own data and model settings still apply.
Support summaries omit source and other sensitive fields by design. You decide what to share.
How diagnostics are handled →Look under the hood
Every claim needs a place to stand.
Read the implementation, inspect release fixtures, or explore earlier case studies with their methods and limits.
Follow your first thread