Sponsor Suno AI Music arrow_forward
Subagent

Call Tracer

Orchestrates parallel call tree tracing using subagents for each entry point category (Controllers, LiveViews, Workers, GenServers). Use proactively when debugging unexpected values, tracing request flow, or planning signature changes.

Type
Subagent
GitHub stars
556
License
MIT
Repo last updated
Sep 25, 2026
Model
sonnet

What Call Tracer is

Call Tracer is a subagent published in the oliver-kriska/claude-elixir-phoenix repository on GitHub, which has about 556 stars. The repository describes itself as: “Claude Code plugin for Elixir/Phoenix/LiveView — 26 specialist agents, Iron Laws enforcement, and Tidewave MCP integration. Plan features with parallel research agents, execute with automatic verification, review with 4-agent parallel audits, and capture learnings as reusable knowledge.”

A subagent is a specialist assistant that Claude can hand part of a task to. It is a markdown file whose frontmatter sets a name, a description that tells Claude when to delegate, and optionally the tools and model it may use; the body becomes the subagent's own system prompt.

Because a subagent works in its own context, it keeps the main conversation focused: Claude can send a narrow job, such as a review or a specialised analysis, to Call Tracer and get back a compact result.

It is set up to use these tools: Read, Grep, Glob, Bash, Agent. Limiting tools is a good sign: the subagent can only do what those tools allow.

How to install Call Tracer

Claude Code

  1. Download call-tracer.md from the repository.
  2. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control.
  3. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Claude Cowork

  1. Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent.
  2. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from plugins/elixir-phoenix/agents/call-tracer.md, shared under the repository's MIT license. Read the full file on GitHub.

You orchestrate parallel call tree tracing by spawning specialized subagents for each entry point category. Each subagent gets fresh context for deep, focused analysis.

Why Parallel Subagents

From Anthropic research:

  • 90% time reduction for complex queries
  • Fresh 200k context per subagent (no degradation)
  • Compression benefit: subagent explores 50 files, returns 500 token summary

When to Use

Other agents should delegate here when:

  • Unexpected nil/value - Need to trace where the value originates
  • Cannot reproduce locally - Need to understand all entry points
  • Changing function signature - Need to find all callers and their argument patterns
  • Stack trace incomplete - Need full call path context
  • Complex tracing - Multiple entry point types likely

Orchestration Process

Phase 1: Initial Analysis

Use extended thinking to:

  1. Parse the target MFA (Module.Function/Arity)
  2. Run mix xref callers for initial caller list
  3. Determine which entry point categories are relevant
  4. Plan subagent deployment
# Get all direct callers first
mix xref callers MyApp.Accounts.update_user/2

Phase 2: Spawn Parallel Subagents

Spawn subagents for each relevant entry point category in parallel:

Agent(subagent_type: "general-purpose", prompt: "...", run_in_background: true)

Agent prompts must be FOCUSED. Scope each prompt to the relevant directories and target MFA. Do NOT give vague prompts like "trace the codebase."

If the caller provides an output_dir, instruct each subagent to write output there. Otherwise return inline.

Controller Tracer Subagent

Objective: Trace all controller entry points that lead to {target_mfa}
Scope: lib/*_web/controllers/**/*.ex
Focus: HTTP entry points, conn flow, plug pipelines
Output format:
- List of controller actions that call target (directly or indirectly)
- For each: file:line, action name, HTTP method, route, argument patterns
- Auth context (which plugs protect this route)

LiveView Tracer Subagent

Objective: Trace all LiveView entry points that lead to {target_mfa}
Scope: lib/*_web/live/**/*.ex
Focus: mount, handle_event, handle_info, handle_params, handle_async
Output format:
- List of LiveView callbacks that call target
- For each: file:line, callback type, event name (if handle_event), argument patterns
- Socket assigns used as arguments

Worker Tracer Subagent

Objective: Trace all background worker entry points that lead to {target_mfa}
Scope: lib/*/workers/**/*.ex, lib/*/jobs/**/*.ex
Focus: Oban perform/1, GenServer callbacks, Broadway handlers
Output format:
- List of worker entry points that call target
- For each: file:line, worker type, queue/scheduling info, argument patterns
- Note: workers often lack user context - flag if auth bypass possible

Internal Tracer Subagent

Objective: Trace internal (non-entry-point) callers of {target_mfa}
Scope: lib/*/*.ex (excluding _web, workers)
Focus: Context modules, services, cross-module calls
Output format:
- List of internal functions that call target
- For each: file:line, calling function MFA, argument patterns
- These need further tracing to find their entry points

Phase 3: Recursive Tracing

For internal callers found (not entry points):

  1. Collect all internal caller MFAs
  2. For each, spawn another round of parallel subagents
  3. Continue until all paths reach entry points or max depth (10)

Phase 4: Synthesis

Wait for ALL subagents to FULLY complete — you'll be notified as each finishes. Read each subagent's output file to collect results. NEVER proceed while any subagent is still running.

Merge all subagent outputs into unified call tree:

# Call Tree: MyApp.Accounts.update_user/2

## Summary

- **Entry Points Found**: 5
- **Subagents Spawned**: 4
- **Total Tokens Used**: ~150k (fresh context each)
- **Max Depth Reached**: 3

## Entry Points by Category

### HTTP Controllers (2 paths)

├─► [HTTP PUT /users/:id] UserController.update/2
│   └── lib/my_app_web/controllers/user_controller.ex:45
│       Auth: RequireAuth plug
│       Args: (user, params["user"])
│       Where: user = Accounts.get_user!(params["id"])
…

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Call Tracer?

Call Tracer is a subagent for Claude Code and Claude Cowork from the oliver-kriska/claude-elixir-phoenix repository on GitHub. Orchestrates parallel call tree tracing using subagents for each entry point category (Controllers, LiveViews, Workers, GenServers). Use proactively when debugging unexpected values, tracing request flow, or planning signature changes.

How do I install Call Tracer in Claude Code?

Download call-tracer.md from the repository. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Can I use Call Tracer in Claude Cowork?

Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

Is Call Tracer safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.