An interactive architecture explorer for codebases.
Explore the hierarchy. Follow a connection. Open the source behind it.
One connected map for your browser, terminal, and coding agent.
No account · Offline-ready · Six themes · Source-linked
Website · Terminal & MCP · 中文 · Release notes
| Your question | Your next move |
|---|---|
| Where does this fit? | Expand from systems to modules and components. Keep parent and global context in view. |
| Where should I start reading? | Choose a source guide by its entry file or symbol, relationship type and module. See the same objects highlighted in the tree. |
| What connects these points? | Build a route with chosen intermediate stops, inspect each relationship, and compare bounded alternatives. |
| What happens along this flow? | Walk through curated scenarios with animated direction cues and connected details. |
| Where is the evidence? | Open source excerpts, commit-pinned links, inputs, outputs, and individual edge details. |
| How can I explain it? | Save your reading position or use presentation mode to guide someone through the map. |
Actual app recording. Animation shows direction in the source map; it is not live execution or measured traffic.
- Download the Web app.
- Extract the
skylense-webfolder. - Open
standalone.htmlin a modern desktop browser.
No Node.js installation, API key, account, or build step is needed for the Web app. Prefer to try it first? Open the live app.
0.4 source indexing. Open your own folder, selected files, public GitHub repository or webpage. Full indexing is the default, with 24 bundled syntax grammars, incremental syntax reuse and project-aware relationships. Version 0.4.1 also verifies and reuses unchanged public GitHub files while rebuilding the complete source map. Source previews, parser diagnostics, unresolved targets and external dependencies remain explicit. The interface is primarily Chinese. Source guide and evidence boundaries.
In the Web app, choose 打开来源 / Open source. Select a folder or files, enter a public URL, or paste text/HTML. Review the coverage report, then enter the same full workbench.
With the Agent toolkit installed:
skylense open /path/to/project
skylense open https://github.com/owner/repo
skylense open https://example.com
skylense analyze /path/to/project --output architecture.jsonThe toolkit includes the complete Web app. Local open handles public webpages that block direct browser CORS; it never executes source code or website scripts. The default indexes every eligible file, including supported declarations after the former preview limits. An explicit --max-files 300 requests a smaller partial preview. Existing Skylense JSON opens with its authored contracts, scenarios and source evidence intact. Source guide · Agent model authoring.
- Syntax and hierarchy: Tree-sitter declarations keep real file, class, function and nested-scope boundaries. Unchanged file syntax is reused locally by content hash.
- Project relationships: included manifests help resolve local imports and aliases. JavaScript/TypeScript call sites use the TypeScript checker when a target is available in the indexed source.
- Julia method sets: static bindings expose possible methods separately as dispatch candidates. Candidate edges share a call-site identity; runtime argument dispatch is not guessed.
- External references: package nodes are explicitly unfetched. Source collection completeness, parser errors and preview shortening are reported separately.
The same full workbench handles generated and curated maps. Static dependency guides support exploration; they do not claim an observed execution order. Full indexing stops explicitly when a resource ceiling is reached instead of silently dropping the rest of a repository. Detailed capabilities and ceilings.
The module tree shows where code lives. Source guides show which connected objects to read together. In 0.4.2, cards use a short file or symbol name, compact module context, relationship purpose and exact object/edge counts. Source modules appear first; examples, tests, documentation and tools are grouped separately.
Switch between the current module and all guides. Opening a guide highlights its objects and ancestor folders in the tree; selecting an object in the graph or the guide's dropdown keeps the reading position in sync. Use 在目录中定位 / Locate in tree to inspect its location, or 返回原位置 / Return to resume your previous view. Existing exported JSON also receives readable guide cards without changing its authored nodes, relationships or evidence.
Guides are selected static neighborhoods with possible branches, not execution traces. Every original relationship remains available in the full map and path search.
| Map | What you can explore |
|---|---|
| autoresearch → | Research iterations, GPT training, optimization, and evaluation. |
| LangGraph → | Graph compilation, Pregel execution, state channels, and checkpoints. |
| vLLM → | Requests, inference scheduling, KV cache, and GPU execution. |
These are selected core paths through fixed source revisions, with authored reading groups and attributed excerpts. Source and license notices.
Porcelain · Jade · Sandstone · Midnight · Graphite · Aurora
Switch with T while preserving your selection, reading position, and zoom. Surfaces, typography, and geometry change together; component identities and relationship meanings stay intact.
Use the same model in an interactive terminal, through JSON output, or from a compatible coding agent.
Download the Agent & Terminal toolkit. With Node.js 22+, install the downloaded file:
npm install -g /absolute/path/to/skylense-0.4.2.tgz
skylense tui autoresearchArrow keys navigate; Enter expands; Tab switches panels; u / d follows upstream or downstream relations; / searches.
# Ask a focused question
skylense search autoresearch optimizer --json
# Follow the original directed relationships
skylense trace autoresearch AR_train --depth 2 --json
# Print local MCP connection settings
skylense configNine MCP tools let an agent analyze sources, export models, list, search, inspect, traverse, plan waypoint paths, read scenarios, and open visual views. Use skylense config --root /path/to/project to explicitly grant local source access. Custom/analyzed models open in the complete local workbench. Copy the generated configuration into a client supporting local stdio MCP. Each client has its own configuration location.
Agent setup and local Web links → · Terminal controls →
| Download | Includes | Requires |
|---|---|---|
| Web ZIP | Interactive explorer, six themes, all three maps, offline HTML | Modern desktop browser |
| Agent toolkit | Source analyzer, full local Web app, CLI, terminal and MCP server | Node.js 22+ |
| Checksums | SHA-256 for both files | Optional integrity check |
Choose the named ZIP or TGZ above, rather than GitHub's automatically generated source archives. A native macOS installer is not included yet.
The downloaded Web app can run offline. Imported model JSON stays in the current page session; reusable syntax facts are cached locally. The CLI reads selected folders/files or public URLs. MCP local source access is confined to an explicitly configured root. Neither executes the displayed repositories or page scripts.
A connected agent receives query results and may send them to its configured model provider. Browser imports do not automatically sync to that process. Data boundaries.
Report a confusing connection or a bug. Include the example, selected object, and steps to reproduce. Share a public-example screenshot with a teammate who is learning the same codebase.
Share Skylense: An interactive code architecture explorer. Follow layers and connections, inspect the source, and use the same map in your browser, terminal, and coding agent.
Preview distribution. You may download and run the provided unmodified application preview. Skylense is not offered under an open-source license; source licensing and commercial rights remain reserved. Upstream example materials retain their own licenses. Preview notice.
Skylense · See every layer. Follow every connection.



