Menu
How to pause/sleep in shell commands on macOS, Linux, and Windows — use this when the agent needs to wait before running the next command.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Helps users connect and use a service in Rebel when it isn't already in the built-in connector catalog. Acts as an expert advisor — runs the full build-vs-buy check (catalog, MCP Registry, community) before scaffolding a custom MCP server and guiding research, implementation, security review, and contribution.
Add, update, or remove connectors (MCP servers) in Rebel. Searches the built-in connector catalog first before suggesting custom builds. Handles setup, configuration, and security review for community connectors.
Capture citable sources (meetings, documents, files, media, web content) as structured files in memory/sources/ with provenance metadata for traceability.
Rules for writing error messages, toasts, banners, and recovery copy in Rebel's voice — dry, calm, helpful, and never apologetic. Use whenever you add or rewrite any user-facing error string.
Guides users through adding new tools or capabilities to an existing connector (MCP server). Handles eligibility, workspace setup, connector research, implementation via Software Engineer workflow, local testing, and PR submission with an extension-specific template.
Help users celebrate impactful wins and surface important learnings by analyzing their recent communications and activities.
| name | cross-platform-shell-delay-sleep-wait |
| description | How to pause/sleep in shell commands on macOS, Linux, and Windows — use this when the agent needs to wait before running the next command. |
| last_updated | "2026-02-13T00:00:00.000Z" |
When the agent needs to wait for a period of time (e.g., waiting for a port to release, a process to exit, or a file to become available), use the correct delay command for the user's platform.
| Platform | Command | Notes |
|---|---|---|
| macOS / Linux | sleep <seconds> | POSIX standard; supports decimals (sleep 0.5) |
| Windows (cmd.exe) | timeout /t <seconds> /nobreak | Built-in; /nobreak prevents user from skipping |
| Windows (PowerShell) | Start-Sleep -Seconds <seconds> | Native cmdlet; also supports -Milliseconds |
Use && to chain a delay before the next command:
macOS / Linux:
sleep 2 && npm run dev
Windows (cmd.exe):
timeout /t 2 /nobreak && npm run dev
Windows (PowerShell):
Start-Sleep -Seconds 2; npm run dev
When Node.js is available (always true in this Electron project), this works on all platforms:
node -e "setTimeout(() => {}, 5000)"
Or inline before another command (use && on macOS/Linux/cmd, ; in PowerShell):
node -e "setTimeout(() => process.exit(), 2000)" && npm run dev
The codebase already uses a standard pattern for async delays:
const sleep = (ms: number) => new Promise((resolve) => setTimeout(resolve, ms));
await sleep(2000);
See src/main/services/demoModeService.ts for the canonical example of platform-branching with process.platform.
Branch on process.platform when spawning shell commands:
const delay = process.platform === 'win32'
? 'timeout /t 2 /nobreak &&'
: 'sleep 2 &&';