claude-allow-stop

Disable continuous work mode so Claude waits for explicit user input.

3|Updated Oct 17, 2025
One-click install
npx skills add https://github.com/ManuelKugelmann/BitBot --skill claude-allow-stop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-allow-stop
Source: https://github.com/ManuelKugelmann/BitBot/tree/main/.bitbot/internal/container/templates/bitbot-dev/.claude/skills/claude-allow-stop
Command: npx skills add https://github.com/ManuelKugelmann/BitBot --skill claude-allow-stop

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Allows you to temporarily disable continuous work mode, ensuring Claude pauses and waits for your explicit input. This is crucial for interactive discussions, brainstorming, or when you need to review progress before proceeding.

Core Features & Use Cases

  • Interactive Mode: Switch Claude to a mode where it completes a response and then waits for your next instruction.
  • Controlled Workflow: Prevent automatic continuation during critical decision points or when you need to provide feedback.
  • Use Case: After Claude proposes a solution, use this skill to discuss the pros and cons interactively without it automatically moving to the next step.

Quick Start

Disable continuous work mode and allow Claude to wait for your input. /claude-allow-stop

Frequently Asked Questions about claude-allow-stop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make Claude pause and wait for my input instead of continuing automatically?

Use `/claude-allow-stop` to disable continuous work mode. Claude will complete its response and pause, waiting for your explicit next instruction instead of proceeding automatically to the next task.

When should I use stop behavior to pause Claude during workflow?

Pause Claude at natural stopping points: after proposing a solution, before making critical decisions, when you need to review progress, or during interactive discussions where you want to provide feedback before proceeding.

Can I control when Claude stops working and waits for my input?

Yes. The `/claude-allow-stop` command activates normal stop behavior, enabling you to control the workflow by pausing Claude after task completion, after work is committed and tests pass, or at points where you need to intervene.

How does `/claude-allow-stop` affect continuous work mode?

The command temporarily disables continuous work mode by safely manipulating internal flags with idempotent behavior. Claude switches to interactive mode, completing responses and then pausing for your input instead of auto-continuing tasks.

What's the best way to handle interactive discussions without Claude auto-continuing?

Trigger `/claude-allow-stop` to switch Claude to interactive mode. This prevents automatic progression during brainstorming or decision points, letting you discuss pros and cons and control when work resumes.

Does `/claude-allow-stop` work during active sessions?

Yes. The command requires only session identification and workspace path resolution. It provides clear user messaging and idempotent behavior, so it works reliably during active continuous work sessions.

Related Skills