Skip to main content

Local Dependency Resolver

PastePrompt can inspect selected files locally and suggest nearby source dependencies so context bundles include the helper code, types, modules, and tests that explain the selected path.

Why it matters

  • LLM review quality often drops when a selected file depends on omitted helpers, types, or local modules.
  • Manual dependency chasing is slow in large repositories and easy to repeat inconsistently.
  • A local resolver keeps dependency selection inside the same reviewable workflow as token budgeting, prompts, and export.

How it works

  • Start with selected files in a scanned local repository.
  • Use Add Local Imports to inspect common local import patterns.
  • Review the added files in the selected-files panel and remove anything that is not useful.
  • Check the updated token budget before copying or exporting the bundle.

Example workflow

  1. Open a repository and select a source file under review.
  2. Click Add Local Imports.
  3. Review files added through JavaScript/TypeScript, Python, or Rust-style local references.
  4. Remove broad or low-signal dependencies if the token budget gets crowded.
  5. Generate the final XML or Markdown context bundle.

Example added context

Selected:
  src/auth/session.ts

Added local imports:
  src/auth/types.ts
  src/auth/crypto.ts
  src/shared/time.ts

Selection reason:
  Via src/auth/session.ts -> src/auth/crypto.ts -> src/shared/time.ts

Limitations

  • The resolver is best-effort and intentionally conservative.
  • It is not a compiler, build system, package manager, or full language server.
  • Package imports, aliases, generated code, custom module loaders, and unusual monorepo setups may need manual selection.
  • Ignored, binary, unreadable, or out-of-repository files are not added by default.

Build a repeatable context workflow.

Download the macOS app, review the docs, and contact support for Founder or Pro licensing during launch.