LUPERSON

Quickstart

A tutorial-style introduction to the basic workflow.

Quickstart

This quickstart walks through the core ClipReplace workflow with the same order you will follow in the app: finish onboarding, create a profile, add rules, run replacement, and then try the secret and per-run input flows.

Introduction

ClipReplace is easiest to understand when you treat it as a copy-time post-processor. You prepare text with placeholders, copy it, run replacement, and then paste the ready-to-use result.

aws ssm start-session \
  --target {{BASTION_INSTANCE_ID}} \
  --profile {{AWS_PROFILE}} \
  --region {{REGION}}

If your rules provide values for those placeholders, ClipReplace can turn that snippet into a command that fits your own environment immediately after you copy it.

1. Initial setup

On first launch, review the onboarding screens and grant only the permissions that are required for the workflow you want to use.

  1. Choose the app language.
  2. Review the privacy policy.
  3. Read the brief usage explanation.
  4. Decide whether to enable the global shortcut.
  5. Decide whether to allow notifications.
Language selection screen Shortcut setup screen

Clipboard access

ClipReplace reads the clipboard only when you explicitly run replacement from the menu bar or the global shortcut.

2. Create a profile

Profiles let you group rules by environment or purpose, such as personal, work, or staging.

  1. Open the profile list.
  2. Add a new profile.
  3. Give it a name that matches the context where the rules will be used.
  4. Keep it enabled if you want its rules to participate in replacement immediately.
Profile list screen Add profile screen

3. Replace plain-text values

Start with a normal text rule before trying secrets.

  1. Add a rule to the profile.
  2. Set the keyword, for example {{AWS_PROFILE}}.
  3. Set the replacement value, for example dev-admin.
  4. Repeat for the other placeholders used in your snippet.
  5. Copy a snippet that contains those keywords.
  6. Run replacement from the menu bar or the global shortcut.
  7. Paste the result into your terminal, editor, or chat tool.
Before:
kubectl config use-context {{CLUSTER_NAME}}

After:
kubectl config use-context my-team-dev
Plain-text rule settings screen Replacement result notification

4. Use a secret value

Secret values are for tokens, passwords, and other sensitive items that should not live as plain text in your rules.

  1. Add a new rule or edit an existing one.
  2. Change the value type to a secret value.
  3. Store the secret through the app so it is handled through Keychain.
  4. Copy a snippet that contains the related keyword.
  5. Run replacement and complete the macOS authentication step when prompted.
Secret rule settings screen Secret authentication flow

After replacement, the result goes back to the clipboard and is cleared automatically after 90 seconds if it contains secret content.

5. Enter values at replacement time

Some values should be entered each time instead of being stored at all.

  1. Set the rule value source to per-run input.
  2. Copy a snippet that contains the keyword.
  3. Run replacement.
  4. Enter the requested value in the prompt window.
  5. Paste the result.

This is useful for MFA codes, temporary IDs, and values that change every time you run the command.

Per-run input rule settings screen Replacement input dialog