Skip to main content

Workspaces

Workspaces let you return to a repository workflow without rebuilding the same file selection and instructions from scratch.

What it does​

An PastePrompt workspace can save repository-specific context-building settings such as:

  • Repository path.
  • Selected files and folders.
  • Preferred output format.
  • Prompt instructions.
  • Prompt template choice.
  • Custom excludes.
  • Include ignored paths allowlist.
  • Token budget preference.
  • Git diff settings when applicable.

Workspaces are local app data. They are intended to make repeatable workflows faster while keeping source code on your machine.

Why it matters​

Audit and code review work rarely happens in one sitting. You may need to return to the same repository across triage, audit passes, sponsor fixes, retests, and report writing.

Workspaces help you:

  • Preserve review scope.
  • Rebuild a known context bundle.
  • Share a repeatable process within a small team without relying on memory.
  • Avoid reselecting the same files repeatedly.
  • Keep project-specific excludes and instructions close to the repository workflow.

How to use it​

  1. Select a repository.
  2. Choose the files, folders, Git metadata, and format you want.
  3. Add prompt instructions or apply a template.
  4. Add custom excludes for generated files, irrelevant directories, or client-specific noise.
  5. Add include ignored paths only for dependency folders or files that are intentionally hidden by .gitignore or .pastepromptignore.
  6. Save the current setup as a workspace.
  7. Reopen the workspace when you return to the review.
  8. Check for missing, moved, renamed, or deleted files before generating a new bundle.

Saved selected paths​

Workspaces should save paths relative to the repository root where possible. Relative paths make the workspace easier to validate against the selected repository and reduce accidental dependence on absolute local machine paths.

Custom excludes​

Custom excludes are useful when .gitignore is not specific enough for audit context. For example, you might exclude generated out/ artifacts, snapshots, fixture dumps, or large vendored files that are not part of the review.

Include ignored paths​

Include ignored paths are explicit allowlist patterns for files that PastePrompt would normally hide because of .gitignore or .pastepromptignore. Use them when a repository ignores a dependency folder that you still need for context.

Example:

lib/forge-std/src/**
vendor/reviewed-package/src/**

Keep these patterns narrow. They are saved with the workspace and apply on refresh, preview, dependency resolution, copy, export, and secret scanning.

Missing files​

If a selected file is deleted, renamed, moved, or ignored after the workspace is saved, PastePrompt should show the missing path instead of silently dropping it. Missing files matter because they can change the meaning of a reproduced bundle.

Example workflow​

  1. Open a security review repository.
  2. Select src/, tests/session.test.ts, package.json, and key interfaces.
  3. Exclude out/, cache/, and unrelated fixtures.
  4. Add vendor/reviewed-package/src/** as an include ignored paths pattern if the repo ignores vendored dependencies required for review.
  5. Apply the Critical/High Confidence Only prompt template.
  6. Save the workspace as Vault Audit - Core Review.
  7. Reopen it later after sponsor fixes arrive.
  8. Check missing files and changed Git state before exporting the next bundle.

Limitations​

  • Workspaces reference local repository paths and may need repair if the repository moves.
  • A workspace does not freeze file contents by itself unless a snapshot/export workflow explicitly stores generated output.
  • Saved selections can become stale after refactors, renames, or branch changes.
  • Include ignored paths can expose files that the repository intentionally hides. Review the allowlist and generated bundle before pasting it into an LLM tool.
  • Full source contents should not be stored in history by default.
  • Workspaces are not cloud sync and do not replace version control.