feat: don't apply 'timeout' wrapper on webserver startup commands

Author: MonkeyCode-AI

.ai-ready/rules/no-long-running-commands.md

@@ -10,17 +10,21 @@ When using command execution tools (such as Bash, shell, or terminal tools), do
 - `ping` without count limit (`-c`)
 - `sleep` with large values
 - Infinite loops (`while true`, `for (;;)`)
-- Long-running servers or daemons
-- `npm start`, `yarn start`, `python -m http.server` without background mode
 - Database migrations on large datasets
 - Large file downloads without timeout
 - `find` or `grep` on entire filesystem without path constraints
 
+## Background Commands
+
+These commands should be executed in the background using the `&` operator, instead of the `timeout` command wrapper:
+
+- Long-running servers or daemons (such as webservers: `npm start`, `yarn start`, `python -m http.server`)
+
 ## Best Practices
 
 - Always set timeouts for network operations
 - Use `--timeout` or `-c` flags where available
-- Use `timeout <time_limit> <command>` command to wrap execution with a time limit
+- Use `timeout <time_limit> <command>` command to wrap execution with a time limit (except for server or daemon commands)
 - Run potentially long operations as subagent or with background task
 - Prefer quick, bounded operations
 - If a long-running command is required, inform the user and ask for confirmation first

AGENTS.md

@@ -46,7 +46,7 @@ Do not execute commands that may run for an extended period:
 Best practices:
 
 - Always set timeouts for network operations
-- Use `timeout <time_limit> <command>` to wrap execution with a time limit
+- If the command **is designed to run in background** (such as `&` appended), this rule **can be ignored**. Otherwise Use `timeout <time_limit> <command>` to wrap execution with a time limit
 - Run potentially long operations as background tasks
 - If a long-running command is required, ask the user for confirmation first