Anamnesis Cloud

A VS Code extension that builds, uploads, and visualizes Anamnesis knowledge graphs on Anamnesis Cloud. Use it for AI-assisted architecture, dependency analysis, and impact exploration across multi-language codebases.

Key features

Create knowledge graphs — Right-click a workspace folder → Anamnesis: Create Knowledge Graph
Projects tree — Browse graphs stored on the Anamnesis Cloud Server
Dual viewer
- Table view (default): fast render and text filtering for large graphs
- Graph view: Cytoscape.js force-directed, circle, grid, concentric, or preset layouts
Node inspection — Label, kind, community, source file, line, and neighbors
Click to source — Open the original file at the correct line from the graph
AI tools — Anamnesis: Enable AI Tools (MCP + Skill) registers an MCP server and Cursor skill so agents query the graph before searching files
Settings panel — Server URL, credentials, default tag, and Test Connection

Supported project types

Anamnesis scans a workspace folder and produces one unified graph per project. Multiple extractors run in parallel; edges link code, config, build, and documentation layers together.

Application & backend code

Project type	Typical repos	What the graph captures
Node / TypeScript / JavaScript	SPAs, APIs, VS Code extensions, React/Vue apps	Classes, interfaces, functions, methods, imports, call relationships
Java	Spring, OSGi, AEM Sling Models, microservices	Classes, interfaces, methods, imports, method invocations
Maven (Java)	Multi-module Java/Maven monorepos	Project coordinates, parent POM inheritance, modules, dependencies, plugins, properties, profiles — linked to `.java` source nodes
HTML (plain)	Static sites, non-AEM templates	HTML tags, attributes, script blocks

Example: A Spring Boot repo gets Java class/method graphs and Maven module + dependency graphs in the same project graph.

Adobe Experience Manager (AEM)

Layer	File patterns	What the graph captures
HTL / Sightly	`.html` under `apps/.../components/`, or any file with `data-sly-*`	AEM component path, Sling Model bindings (`data-sly-use`), HTL includes/calls, templates, resources
AEM Content XML	`.content.xml` under component paths	Component metadata, `_cq_dialog` / design dialog, dialog tabs & fields, `fieldLabel` / `fieldDescription`, JCR property names, clientlibs, `sling:resourceSuperType` inheritance
Java (Sling Models)	`core/src/.../*.java`	Model classes linked from HTL via `uses_model`
Maven	`ui.apps/pom.xml`, root `pom.xml`	HTL validator plugins, Sling dependencies, module structure

Example: An AEM project like adobexp produces a graph connecting header.html → HeaderModel → _cq_dialog fields → ./headerTitle → Maven modules — enabling AI to find components, dialogs, and models without blind grep.

Infrastructure & DevOps

Project type	File patterns	What the graph captures
Apache Web Server	`.conf`, `.any` (vhosts, dispatcher farms)	VirtualHosts, domains, SSL certs, proxy targets, balancers, backends, credentials, modules
NGINX	`.conf`, `.upstream.conf`	Server blocks, domains, upstreams, backends, locations, SSL, snippets
Bash	`.sh`, `.bash`, shebang scripts	Functions, shell commands, env vars, deploy targets
Jenkins	`Jenkinsfile`, `Jenkinsfile.`, `.jenkinsfile`	Pipelines, stages, steps, environment, deploy servers, Git repos

Apache and NGINX configs are auto-detected by path (sites-available, nginx, upstreams, etc.) and directive syntax.

Architecture documentation

Project type	File patterns	What the graph captures
Markdown architecture	`.md`	Projects, modules, API routes, Mermaid flows, cross-project `uses` edges (st-ck-architecture KG conventions)

Extractors reference

When you run Anamnesis: Create Knowledge Graph, these extractors are applied automatically:

Technology	File patterns	Graph entities
TypeScript / JavaScript	`.ts`, `.tsx`, `.js`, `.jsx`, `.mjs`, `.cjs`	classes, interfaces, functions, methods, imports, calls
Java	`.java`	classes, interfaces, methods, imports, invocations
Maven	`pom.xml`, `*.pom`	`maven_project`, modules, dependencies, plugins, properties, profiles
HTL / Sightly (AEM)	`.html` with `data-sly-*` or under `apps/.../components/`	`htl_component`, `htl_use_model`, `htl_include`, `htl_template`, tags
AEM Content XML	`.content.xml` under AEM component paths	`aem_component`, `aem_dialog`, `aem_dialog_tab`, `aem_dialog_field`, `aem_property`, `aem_clientlib`
HTML	`.html`, `.htm` (non-HTL)	tags, attributes, script blocks
Apache Web Server	`.conf`, `.any`	vhosts, domains, SSL, proxies, backends, modules
NGINX Server	`.conf`, `.upstream.conf`	server blocks, upstreams, backends, locations
Markdown Architecture	`.md`	projects, modules, API routes, mermaid flows
Bash	`.sh`, `.bash`, shebang scripts	functions, commands, env vars, deploy targets
Jenkins Pipeline	`Jenkinsfile`, `*.jenkinsfile`	pipeline, stages, steps, environment

Auto-detection notes

Maven — Detected by pom.xml filename or Maven <project> / modelVersion in .xml files (not generic AEM .content.xml).
HTL — Detected when the path is under apps/.../components/ or the file contains data-sly-* directives (takes precedence over plain HTML extraction).
AEM .content.xml — Detected for JCR content files under jcr_root/apps/ (component definition, _cq_dialog, clientlibs, edit config).
Plain HTML — Used only when the file is not classified as HTL.

Recommended scan settings

For Java/Maven/AEM repos, add build output folders to anamnesis.excludeGlobs to avoid duplicate nodes:

"anamnesis.excludeGlobs": ["target/", "dist/", "node_modules/"]

Default excludes already skip dist/, build/, out/, .git/, and node_modules/.

Quick start

Install the extension and open Anamnesis in the activity bar.
Configure Anamnesis Settings (Server URL, Client Id, Secret Key from Anamnesis Cloud).
Right-click a project folder in the Explorer → Anamnesis: Create Knowledge Graph.
Open the project from the Projects tree to explore the graph.
Optional: run Anamnesis: Enable AI Tools (MCP + Skill) so Cursor/VS Code agents query the graph via MCP.

Configuration

Setting	Default	Description
`anamnesis.serverUrl`	`https://apigateway.anamnesis.cloud`	API base URL (no trailing slash)
`anamnesis.clientId`	`""`	Client Id from Anamnesis Settings → View Credentials
`anamnesis.secretKey`	`""`	Secret Key from Anamnesis Settings → View Credentials
`anamnesis.defaultTag`	`"default"`	Default graph tag when none is selected
`anamnesis.excludeGlobs`	`[]`	Extra path prefixes to skip during graph generation

Anamnesis Cloud

Graphs are stored on Anamnesis Cloud. Create an account at anamnesis.cloud, configure credentials in the extension, and upload graphs directly from VS Code.

License

MIT