codebase-memory-tracing

Trace function call paths across a codebase by using graph-based queries to discover targets and traverse inbound callers or outbound callees. You can set depth limits to map dependencies and understand complex relationships.

Function call tracing reveals which functions call others, helping debug and understand complex dependencies. By mapping inbound and outbound relationships, you can assess a function's impact and locate inter-module references.

Yes, you can retrieve full context for a function, including cross-service HTTP calls and inter-module references. Graph-based queries traverse bidirectional call paths to expose these dependencies.

Find the exact function name by running a regex-based search to locate targets within the knowledge graph. This ensures accurate traversal of inbound callers and outbound callees.

Limit the depth of a call path trace by specifying depth limits during your graph query. This constrains the traversal of callers and callees to a chosen level, keeping the dependency map manageable.

Yes, codebase tracing supports bidirectional analysis to map both inbound callers and outbound callees. It uses graph queries to traverse dependencies and retrieve relevant code snippets for inspection.