Skip to main content

Exporting Context

PastePrompt can copy generated context to the clipboard or export it as a Markdown file. Both actions can move source-code context outside the app, so treat them as privacy-sensitive.

Copy vs export​

Use copy when:

  • You want to paste directly into an LLM chat or agent.
  • The bundle is temporary.
  • You do not need a durable local artifact.

Use export when:

  • You want a reviewable .md file.
  • You need to attach context to audit notes.
  • You want to preserve a context bundle for a sponsor fix or team handoff.
  • You want the output hash and file artifact to line up with your review notes.

Markdown export​

Markdown export is useful when the context bundle should be read by humans as well as LLM tools. A Markdown bundle can include:

  • File map.
  • Git metadata.
  • Token estimates.
  • Selected file contents.
  • User instructions.
  • Prompt template text.
  • Output hash when available.

Store Markdown exports as sensitive source-code artifacts.

Secret scanner flow​

Before copy or export:

  1. PastePrompt scans selected files, diffs, and user instructions.
  2. You review each warning.
  3. You decide whether to redact, exclude, or cancel.
  4. PastePrompt generates the final output only after the warning flow is handled.

Redaction, exclusion, and cancel​

  • Redact when the file is needed but a specific value should not be shared.
  • Exclude when the whole file should not be part of the bundle.
  • Cancel when the selection needs a broader review before any context leaves the app.
Redaction is not a substitute for review

After redaction, inspect the generated bundle. Related secrets can appear in comments, tests, config, diffs, or instructions.

Store exported bundles safely​

  1. Save exports outside shared or synced folders unless sharing is intentional.
  2. Use clear filenames that identify repo, scope, date, and branch without exposing client secrets.
  3. Delete temporary bundles when the review is done.
  4. Avoid committing exports to the audited repository.
  5. Treat exports like source code when sending them to other people or services.