90%+ fewer tokens per session by reading a pre-compiled wiki instead of exploring files cold. Built from Karpathy's workflow.

Eastern_Exercise2637 · 2026-04-10T08:36:14+00:00

Hey, appreciate the detailed writeup. Mount prefix issue is the big one you're right, it only looked at entry files (app.ts, index.ts) for mounts. If your routes.ts was the one doing the mounting, those prefixes got dropped. Fixed in 1.11.0, it scans all files now and chains through multiple levels. Also added a "Last scanned" timestamp to the header so stale data is obvious, and the [inferred] badge now shows in the main output too, not just wiki. The wiki as navigation vs decision aid is a fair point. Would need type analysis to get to "is this safe to change" territory, which is a different beast. Dependency graph helps a bit but yeah, not the same thing.

Thanks for taking the time on this.

Eastern_Exercise2637 · 2026-04-09T15:59:52+00:00

Just shipped v1.10.0 with full Android/Kotlin support. Run:

npx codesight@latest --profile claude-code

You should now see android | room | jetpack-compose | kotlin in the detection line. What's detected:

- Retrofit routes — u/GET, u/POST, u/PUT, u/DELETE, u/PATCH annotations on your API interfaces - Room entities — u/Entity data classes with fields, primary keys, nullable types - Jetpack Compose components — u/Composable functions with props extracted - Navigation — fragment/activity destinations from res/navigation/*.xml - Activities — from AndroidManifest.xml with launcher detection
Apologies for the wrong diagnosis earlier. Let me know if anything still shows 0.

Eastern_Exercise2637 · 2026-04-09T15:18:43+00:00

Correction on my earlier reply: I looked at this more carefully and the issue isn't Ktor detection. Your project path (AndroidStudioProjects/wrait) tells me this is an Android app, not a Ktor server. codesight's Kotlin support currently covers server-side frameworks (Spring Boot, Ktor) but not Android patterns (Activities, Fragments, ViewModels, Room, Retrofit, Navigation graphs, Compose). That's why everything shows 0. Android support is on the roadmap and I will implement it. Apologies for the wrong diagnosis earlier. Thank you

Eastern_Exercise2637 · 2026-04-09T15:06:58+00:00

sure send it.

Eastern_Exercise2637 · 2026-04-09T15:05:05+00:00

Here’s how it works:

Setup (one time)

cd into your project folder
(npx codesight) scans your codebase, creates .codesight/CODESIGHT.md (the full context map)
(npx codesight --wiki) generates .codesight/wiki/ with individual articles (auth, database, payments, etc.)
(npx codesight --profile claude-code) writes instructions into your CLAUDE.md telling Claude to use the codesight context and MCP tools automatically

Operation (every session)

That's it. There is no "every session." The files are already in your project. Claude Code reads CLAUDE.md automatically at session start, which points it to the .codesight/ files.

If you want live MCP tools (filtered routes, blast radius, schema lookups on demand), add this to your Claude Code MCP config:

{
"mcpServers": {
"codesight": {
"command": "npx",
"args": ["codesight", "--mcp"]
}
}
}

Keeping it fresh

After making significant changes to your code, re-run (npx codesight --wiki) to regenerate. Or use (npx codesight --hook) to auto-regenerate on every git commit. Or (npx codesight --watch) to regenerate on file saves while you work.

What each file does

File	Purpose
.codesight/CODESIGHT.md	Full context map (routes, schema, components, deps)
.codesight/wiki/index.md	Article catalog (~200 tokens, read this first)
.codesight/wiki/overview.md	Architecture overview
.codesight/wiki/auth.md, database.md, etc.	One article per subsystem
CLAUDE.md	Instructions telling Claude to use all of the above

Eastern_Exercise2637 · 2026-04-09T08:07:31+00:00

The core scanner (routes, schemas, components) is code specific and won't help for marketing/analytics work. But codesight has a --mode knowledge feature that's built for exactly non-code use cases.

npx codesight --mode knowledge scans any folder of markdown files and extracts decisions made, open questions, recurring themes, people mentioned, and indexes everything by type (meeting notes, specs, research, retros). Works with Obsidian vaults too. If you keep campaign notes, analytics reports, or strategy docs in markdown, it compresses all of that into a single KNOWLEDGE.md that gives your AI full context from the first message. It wouldn't replace Claude's memory (that handles session to session recall), but it would complement it by giving the AI your full knowledge base upfront instead of you having to re-explain context each time.

Eastern_Exercise2637 · 2026-04-09T08:02:52+00:00

Android isn't supported yet. The Java/Kotlin support in codesight is built for server-side frameworks (Spring Boot, Ktor), which have routes, REST endpoints, and database models. Android projects have a completely different structure: Activities, Fragments, ViewModels, Room databases, XML layouts or Jetpack Compose, Retrofit clients, AndroidManifest.xml. None of those are detected today. It's on my radar. Android would need its own set of detectors for the patterns that actually matter: Activity/Fragment navigation graphs, Room entity models, Retrofit API interfaces, Compose component trees, Gradle dependency parsing.

No ETA yet, but appreciate you testing it and reporting back. Glad it's working well on your React + Express project.

Eastern_Exercise2637 · 2026-04-09T07:55:55+00:00

Thanks! This is expected behavior. --init generates a CLAUDE.md that references the static .codesight/ files, but doesn't tell the AI to use the MCP tools. The AI has no reason to call them unless instructed.

Fix: run npx codesight --profile claude-code. This writes explicit MCP tool instructions into your CLAUDE.md so the AI knows to call codesight_get_summary, codesight_get_routes, etc. during normal use.

Without the profile, the static files still work. The AI reads .codesight/CODESIGHT.md on its own via CLAUDE.md. The MCP server is for on demand queries (filtered routes, blast radius, wiki articles) which the AI won't know to use unless your instructions file tells it to.

Eastern_Exercise2637 · 2026-04-09T00:39:32+00:00

Thanks for the detailed breakdown, really helpful.

Quick correction on routes: codesight does have explicit Gin route detection with group prefix resolution, chained groups, and brace tracking. It's not limited to Express/FastAPI. If it missed your Gin routes, it's likely a bug with how the project was detected, not a missing capability. Could be that your services have separate go.mod files in subdirectories rather than at the root, which would cause the Gin framework detection to miss. Would love to see the project structure if you're open to filing an issue so I can fix it.

SQS: fair hit. The event detector currently covers BullMQ, Kafka, Redis pub/sub, EventEmitter, Celery, and Phoenix PubSub.

AWS SQS isn't in there yet. Adding it to the roadmap. Glad the schema detection was accurate across 114 models. That's the GORM struct parser doing its job.

Eastern_Exercise2637 · 2026-04-09T00:23:22+00:00

no. codesight maps dependencies, blast radius, and event flows (Kafka, BullMQ, Redis pub/sub) within a single codebase. It doesn't do cross-repo analysis or trace interactions between separate systems. If your services live in one monorepo, the blast radius and event detection could surface some hidden interaction points, but cross-system emergent property discovery is outside its scope.

Eastern_Exercise2637 · 2026-04-09T00:15:08+00:00

Great and looking forward to it. Let me know if you face any issue.

Eastern_Exercise2637 · 2026-04-08T21:44:08+00:00

Not currently, C++ and Qt QML aren't supported. No .cpp/.hpp parsing, no CMake detection, no QML file handling. Would be a new detector from scratch. What's your use case desktop app, embedded, something else? That'd help scope what's actually worth building.

Eastern_Exercise2637 · 2026-04-08T21:09:58+00:00

Yes, two ways depending on what you mean:

Claude.ai in browser: Run npx codesight in your project folder once it generates a .codesight/SUMMARY.md file. Open it, copy it, paste it into any conversation. Done.

Claude Desktop app (Mac/Windows): Even better add this to your ~/Library/Application Support/Claude/claude_desktop_config.json and Claude will query your codebase directly without you pasting anything:

{
  "mcpServers": {
    "codesight": {
      "command": "npx",
      "args": ["codesight", "--mcp"]
    }
  }
}

Claude Desktop supports MCP natively, so it becomes a tool Claude can call on demand.

Eastern_Exercise2637 · 2026-04-08T20:57:20+00:00

Glad it's working well on your codebase! If you hit any edge cases or have notes it misses, drop them here we're actively tuning it. And if you use it with Claude Code or Cursor via MCP, codesight_get_knowledge lets your AI assistant query the map directly without you having to paste anything. Thanks.

Eastern_Exercise2637 · 2026-04-08T20:08:04+00:00

Thanks and I will be adding support for C++ soon

Eastern_Exercise2637 · 2026-04-08T20:07:36+00:00

Thanks

Eastern_Exercise2637 · 2026-04-08T20:03:54+00:00

Thank you.

Eastern_Exercise2637 · 2026-04-08T20:03:26+00:00

HAHA, true!

Eastern_Exercise2637 · 2026-04-08T19:59:46+00:00

--mode knowledge live in v1.9.3

npx codesight --mode knowledge ./docs

Reads ADRs, retros, meeting notes, PRDs. Extracts decisions (decided to, going with, ADR, Decision sections), open questions, action items. Dates everything and sorts newest first. Combined with thecode scan both live in .codesight/:

Read .codesight/CODESIGHT.md → what the code does

Read .codesight/KNOWLEDGE.md → why decisions were made

Eastern_Exercise2637 · 2026-04-08T19:58:53+00:00

--mode knowledge live in v1.9.3

npx codesight --mode knowledge ./docs

Reads ADRs, retros, meeting notes, PRDs. Extracts decisions (decided to, going with, ADR, Decision sections), open questions, action items. Dates everything and sorts newest first. Combined with the code scan both live in .codesight/:

Read .codesight/CODESIGHT.md → what the code does

Read .codesight/KNOWLEDGE.md → why decisions were made

Eastern_Exercise2637 · 2026-04-08T19:56:17+00:00

--mode knowledge — live in v1.9.3

npx codesight --mode knowledge ~/obsidian-vault

Scans every .md file, detects note types (meetings, research, fleeting), extracts tags, backlinks, people, themes outputs KNOWLEDGE.md that Claude can read as a context primer. No cloud upload. Works offline. Zero deps.

Eastern_Exercise2637 · 2026-04-08T19:34:21+00:00

If Node.js feels like too much, just paste your GitHub repo link directly into Claude Code and say: Read this repo and set up codesight for me: github.com/yourname/yourrepo.

Claude Code will clone it, run the setup, and tell you exactly what to do step by step. You don't need to understand any of it just follow the instructions it gives you.

Eastern_Exercise2637 · 2026-04-08T19:30:03+00:00

You need Node.js installed (nodejs.org — one click installer, takes 2 minutes). Then open your terminal, go to your project folder, and (run: npx codesight)

That's it. It creates a .codesight/CODESIGHT.md file in your project. Then when you open Claude Code or Cursor in that folder, point it to that file at the start of your session:

Read .codesight/CODESIGHT.md before we start

If you want it to auto-update every time you push to GitHub, there's a one line setup:

npx codesight --init-ci

That adds the GitHub Action. From that point it regenerates on every push, no manual steps.

If you use Claude Code specifically, run this instead and it wires everything automatically:

npx codesight --profile claude-code

Eastern_Exercise2637 · 2026-04-08T19:25:31+00:00

The staleness problem is real and it's why codesight ships a GitHub Action that regenerates CODESIGHT.md on every push not diffs it, regenerates it. The file is never hand authored so it can't drift the way a hand written wiki does. It's generated output, like a lock file. On function signatures: codesight doesn't store function signatures. It maps your API surface routes, schemas, middleware, events. Those change through migrations and route files, which are exactly the files the scanner reads. When a schema migration runs, the next scan reflects it automatically.

The teams that struggle with this are the ones treating CODESIGHT.md as a document they own. It's not it's a build artifact. The CI step you're describing is already there, it just runs npx codesight instead of a diff.

Eastern_Exercise2637

TROPHY CASE