mode

Prompy — Mode Toggle

Switches Prompy's operating mode between the three options, persistently across sessions.

When invoked

The user types /prompy:mode [auto-pilot|co-pilot|off], or asks to "switch prompy", "turn prompy off", "what mode is prompy in", etc.

What to do

Step 1 — Read $ARGUMENTS

Strip whitespace. The argument should be one of: auto-pilot, co-pilot, off.

Step 2 — If $ARGUMENTS is empty or invalid

Show the current state and the options:

1. Read ~/.claude/prompy-mode if it exists (otherwise default = co-pilot)
2. Check if PROMPY_MODE env var is set (this overrides the file)
3. Show:

Prompy is currently in: [current mode] mode
[Source: env var PROMPY_MODE / file ~/.claude/prompy-mode / default]

Options:
  /prompy:mode auto-pilot  — silently rewrites and runs improved prompts
  /prompy:mode co-pilot    — shows a one-line nudge with approval prompt (default)
  /prompy:mode off         — disables Prompy intervention entirely

Then STOP. Do not perform any further action.

Step 3 — If $ARGUMENTS is valid (auto-pilot, co-pilot, or off)

1. Ensure ~/.claude/ exists: mkdir -p ~/.claude
2. Write the new mode to ~/.claude/prompy-mode (single line, no trailing newline preferred but tolerated)
3. Acknowledge in one line:

Prompy is now in [new mode] mode. Saved to ~/.claude/prompy-mode.

4. If PROMPY_MODE env var is set AND different from the new mode, add a warning line:

Note: PROMPY_MODE env var is set to "[env value]" and will override this file. Unset it (`unset PROMPY_MODE`) to use the file value.

5. For the remainder of THIS session, adjust your behavior to match the new mode starting from your next response. (Hook context is fixed for this session, but you can follow the new mode behaviorally.)

6. STOP. Do not perform any further work.

Mode descriptions

• auto-pilot — Silently grades, rewrites, and runs improved prompts. One-line trace at the top of the response shows what changed. Best for users who trust Prompy's rewrites and want zero approval friction.
• co-pilot (default) — Grades silently, shows a one-line nudge with the improved prompt, waits for y/n/edit approval. Best for users who want visibility and control before each rewrite runs.
• off — Disables all hook-based intervention. The deep-dive skill (/prompy:prompy) remains available for manual use.

Persistence

• The mode file ~/.claude/prompy-mode is read by the SessionStart hook at the start of every new Claude Code session.
• The environment variable PROMPY_MODE (set in your shell profile) overrides the file. Use this if you want different modes per project.
• If neither is set, the default is co-pilot.

Examples

User: /prompy:mode auto-pilot Response: Prompy is now in auto-pilot mode. Saved to ~/.claude/prompy-mode.

User: /prompy:mode Response (showing current state):

Prompy is currently in: co-pilot mode
Source: default (no file, no env var)

Options:
  /prompy:mode auto-pilot
  /prompy:mode co-pilot
  /prompy:mode off

User: /prompy:mode whatever Response: same as the no-argument case (treats invalid input as a query).