Skip to main content

Context Bundles

PastePrompt turns selected files, Git metadata, diffs, related files, and prompt instructions into clean context bundles that can be inspected before they are copied or exported.

Why it matters

  • Large codebases need structured input, not ad hoc pasted fragments.
  • A deterministic bundle makes it easier to repeat, compare, and review LLM-assisted analysis.
  • Markdown exports create a readable artifact for audit notes, handoff, or internal review.

How it works

  • Select files and folders from an ignore-aware local repository tree.
  • Choose XML-like structure when the target workflow benefits from labeled sections.
  • Choose Markdown when humans need to read, store, or diff the bundle directly.
  • Enable local secret scanning when needed and review the final output.

Example workflow

  1. Open a local repository and select audit-relevant files.
  2. Add Git diff context, related files, and user instructions when needed.
  3. Choose XML-like or Markdown output.
  4. Run the secret scanner.
  5. Copy the bundle or export it as `.md`.

Example XML-like bundle shape

<file_map>
  src/auth/session.ts
  src/billing/pricing.ts
  tests/session.test.ts
</file_map>
<file_contents>
  <file path="src/auth/session.ts">
    ...
  </file>
  <file path="src/billing/pricing.ts">
    ...
  </file>
</file_contents>
<user_instructions>
  Review authorization, data flow, and integration assumptions.
</user_instructions>

Limitations

  • A bundle is only as useful as the selected files and instructions.
  • Generated context does not guarantee correct LLM output.
  • Users should inspect the final bundle before sending it to an external tool.

Build a repeatable context workflow.

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