feat: Implement automatic backend server streaming in fullstack development mode

- Add intelligent terminal command routing for Python/backend commands
- Backend servers automatically start when running fullstack apps
- Frontend servers automatically start when running fullstack apps
- Terminal output streams server startup and command execution
- Fix preview panel conflicts by using proper app running process
- Add comprehensive terminal integration documentation

Resolves: Backend server streaming in Backend/Fullstack development modes

Author: SFARPak

src/ipc/utils/development_orchestrator.ts

@@ -571,6 +571,8 @@ Please generate a well-structured backend application with:
 IMPORTANT: Use proper dyad-write tags to create files. Always include the "path" attribute.
 For backend files, use paths like "backend/main.py" or "backend/server.js" etc.
 
+**DO NOT attempt to run backend servers manually.** The system automatically handles server startup when users click the "Run App" button. Focus ONLY on creating code files. The system will automatically detect the framework and start the appropriate server.
+
 Current AI_RULES.md contains development guidelines. Follow them strictly.
 `;
 

src/prompts/system_prompt.ts

@@ -181,15 +181,9 @@ When working with Django applications:
 - Use <read_file> to examine existing Django files (models.py, views.py, urls.py, settings.py)
 - Use <search_replace> for precise edits to Django code
 - Use <write_to_file> for creating new Django apps, models, views, etc.
-- Use <dyad-run-backend-terminal-cmd> to execute Django management commands automatically in the backend terminal:
-  - <dyad-run-backend-terminal-cmd description="Install Python dependencies">pip install -r requirements.txt</dyad-run-backend-terminal-cmd>
-  - <dyad-run-backend-terminal-cmd description="Create database migrations">python manage.py makemigrations</dyad-run-backend-terminal-cmd>
-  - <dyad-run-backend-terminal-cmd description="Apply database migrations">python manage.py migrate</dyad-run-backend-terminal-cmd>
-  - <dyad-run-backend-terminal-cmd description="Start development server">python manage.py runserver 8000</dyad-run-backend-terminal-cmd>
-  - <dyad-run-backend-terminal-cmd description="Create new Django app">python manage.py startapp <app_name></dyad-run-backend-terminal-cmd>
 - Use <grep_search> to find patterns across Django codebase
 
-Always explain what you're doing and why, then use the appropriate tools to implement Django solutions. When setting up Django projects, use terminal commands to run migrations and start servers.
+**CRITICAL: DO NOT use <dyad-run-backend-terminal-cmd> tags during development.** The system automatically handles all server startup, dependency installation, and terminal commands when users click "Run App". Your role is ONLY to create and modify code files.
 
 # Django Development Guidelines
 
@@ -203,9 +197,11 @@ When working with Django applications:
 - **Security**: Implement CSRF protection, authentication, and authorization
 - **Testing**: Write comprehensive unit and integration tests
 
-# Django Terminal Commands
+# IMPORTANT: Server Management
 
-When you need to execute Django commands, use the <dyad-run-backend-terminal-cmd> tags above. The system will automatically run these commands in the backend terminal for you. Do not show commands in chat - use the dyad tags instead.
+**DO NOT attempt to run the Django server manually.** The system automatically handles server startup when users click the "Run App" button. You should focus on creating code files and using terminal commands only for installation, migrations, and other setup tasks. The system will automatically start the server using: \`python manage.py runserver 0.0.0.0:<available_port>\`
+
+**NEVER output <dyad-run-backend-terminal-cmd> tags in your responses.** These are handled automatically by the system.
 
 # Django Best Practices
 
@@ -229,14 +225,9 @@ When working with FastAPI applications:
 - Use <read_file> to examine existing FastAPI files (main.py, routes, schemas, models)
 - Use <search_replace> for precise edits to FastAPI code
 - Use <write_to_file> for creating new routes, schemas, models, etc.
-- Use <dyad-run-backend-terminal-cmd> to execute FastAPI development commands automatically in the backend terminal:
-  - <dyad-run-backend-terminal-cmd description="Install Python dependencies">pip install -r requirements.txt</dyad-run-backend-terminal-cmd>
-  - <dyad-run-backend-terminal-cmd description="Start FastAPI server">uvicorn main:app --reload --host 0.0.0.0 --port 8000</dyad-run-backend-terminal-cmd>
-  - <dyad-run-backend-terminal-cmd description="Create database migrations">alembic revision --autogenerate -m "migration message"</dyad-run-backend-terminal-cmd>
-  - <dyad-run-backend-terminal-cmd description="Apply database migrations">alembic upgrade head</dyad-run-backend-terminal-cmd>
 - Use <grep_search> to find patterns across FastAPI codebase
 
-Always explain what you're doing and why, then use the appropriate tools to implement FastAPI solutions. When setting up FastAPI projects, use terminal commands to install dependencies and start servers.
+**CRITICAL: DO NOT use <dyad-run-backend-terminal-cmd> tags during development.** The system automatically handles all server startup, dependency installation, and terminal commands when users click "Run App". Your role is ONLY to create and modify code files.
 
 # FastAPI Development Guidelines
 
@@ -249,9 +240,15 @@ When working with FastAPI applications:
 - **Documentation**: Leverage FastAPI's automatic OpenAPI documentation
 - **Testing**: Write async tests using pytest and httpx
 
-# FastAPI Terminal Commands
+# IMPORTANT: Server Management
+
+**DO NOT attempt to run the FastAPI server manually.** The system automatically handles server startup when users click the "Run App" button. You should focus on creating code files and using terminal commands only for installation, migrations, and other setup tasks. The system will automatically start the server using: \`uvicorn main:app --reload --host 0.0.0.0 --port <available_port>\`
+
+**NEVER output <dyad-run-backend-terminal-cmd> tags in your responses.** These are handled automatically by the system.
+
+# IMPORTANT: Server Management
 
-When you need to execute FastAPI commands, use the <dyad-run-backend-terminal-cmd> tags above. The system will automatically run these commands in the backend terminal for you. Do not show commands in chat - use the dyad tags instead.
+**DO NOT attempt to run backend servers manually.** The system automatically handles server startup when users click the "Run App" button. You should focus on creating code files and using terminal commands only for installation, migrations, and other setup tasks. The system will detect the framework and start the appropriate server (uvicorn for FastAPI) automatically.
 
 # FastAPI Best Practices
 
@@ -276,16 +273,9 @@ When working with Flask applications:
 - Use <read_file> to examine existing Flask files (app.py, routes, models, templates)
 - Use <search_replace> for precise edits to Flask code
 - Use <write_to_file> for creating new routes, models, templates, etc.
-- Use <dyad-run-backend-terminal-cmd> to execute Flask development commands automatically in the backend terminal:
-  - <dyad-run-backend-terminal-cmd description="Install Python dependencies">pip install -r requirements.txt</dyad-run-backend-terminal-cmd>
-  - <dyad-run-backend-terminal-cmd description="Start Flask development server">python app.py</dyad-run-backend-terminal-cmd>
-  - <dyad-run-backend-terminal-cmd description="Alternative Flask start">flask run --host=0.0.0.0 --port=5000</dyad-run-backend-terminal-cmd>
-  - <dyad-run-backend-terminal-cmd description="Initialize Flask-Migrate">flask db init</dyad-run-backend-terminal-cmd>
-  - <dyad-run-backend-terminal-cmd description="Create database migrations">flask db migrate -m "migration message"</dyad-run-backend-terminal-cmd>
-  - <dyad-run-backend-terminal-cmd description="Apply database migrations">flask db upgrade</dyad-run-backend-terminal-cmd>
 - Use <grep_search> to find patterns across Flask codebase
 
-Always explain what you're doing and why, then use the appropriate tools to implement Flask solutions. When setting up Flask projects, use terminal commands to install dependencies and start servers.
+**CRITICAL: DO NOT use <dyad-run-backend-terminal-cmd> tags during development.** The system automatically handles all server startup, dependency installation, and terminal commands when users click "Run App". Your role is ONLY to create and modify code files.
 
 # Flask Development Guidelines
 
@@ -298,9 +288,11 @@ When working with Flask applications:
 - **Extensions**: Leverage Flask extensions for common functionality (SQLAlchemy, Login, etc.)
 - **Configuration**: Manage different configurations for development and production
 
-# Flask Terminal Commands
+# IMPORTANT: Server Management
 
-When you need to execute Flask commands, use the <dyad-run-backend-terminal-cmd> tags above. The system will automatically run these commands in the backend terminal for you. Do not show commands in chat - use the dyad tags instead.
+**DO NOT attempt to run the Flask server manually.** The system automatically handles server startup when users click the "Run App" button. You should focus on creating code files and using terminal commands only for installation, migrations, and other setup tasks. The system will automatically start the server using the appropriate Flask command.
+
+**NEVER output <dyad-run-backend-terminal-cmd> tags in your responses.** These are handled automatically by the system.
 
 # Flask Best Practices
 
@@ -325,15 +317,9 @@ When working with Node.js applications:
 - Use <read_file> to examine existing Node.js files (server.js, routes, models, controllers)
 - Use <search_replace> for precise edits to Node.js code
 - Use <write_to_file> for creating new routes, models, controllers, middleware, etc.
-- Use <dyad-run-backend-terminal-cmd> to execute Node.js development commands automatically in the backend terminal:
-  - <dyad-run-backend-terminal-cmd description="Install Node.js dependencies">npm install</dyad-run-backend-terminal-cmd>
-  - <dyad-run-backend-terminal-cmd description="Start production server">npm start</dyad-run-backend-terminal-cmd>
-  - <dyad-run-backend-terminal-cmd description="Start development server">npm run dev</dyad-run-backend-terminal-cmd>
-  - <dyad-run-backend-terminal-cmd description="Run server directly">node server.js</dyad-run-backend-terminal-cmd>
-  - <dyad-run-backend-terminal-cmd description="Run with nodemon">npx nodemon server.js</dyad-run-backend-terminal-cmd>
 - Use <grep_search> to find patterns across Node.js codebase
 
-Always explain what you're doing and why, then use the appropriate tools to implement Node.js solutions. When setting up Node.js projects, use terminal commands to install dependencies and start servers.
+**CRITICAL: DO NOT use <dyad-run-backend-terminal-cmd> tags during development.** The system automatically handles all server startup, dependency installation, and terminal commands when users click "Run App". Your role is ONLY to create and modify code files.
 
 # Node.js Development Guidelines
 
@@ -346,9 +332,11 @@ When working with Node.js applications:
 - **Database**: Choose appropriate database solutions (MongoDB, PostgreSQL, etc.)
 - **Testing**: Write unit and integration tests using Jest or Mocha
 
-# Node.js Terminal Commands
+# IMPORTANT: Server Management
+
+**DO NOT attempt to run the Node.js server manually.** The system automatically handles server startup when users click the "Run App" button. You should focus on creating code files and using terminal commands only for installation, migrations, and other setup tasks. The system will automatically start the server using the appropriate Node.js command.
 
-When you need to execute Node.js commands, use the <dyad-run-backend-terminal-cmd> tags above. The system will automatically run these commands in the backend terminal for you. Do not show commands in chat - use the dyad tags instead.
+**NEVER output <dyad-run-backend-terminal-cmd> tags in your responses.** These are handled automatically by the system.
 
 # Node.js Best Practices
 
@@ -465,40 +453,21 @@ const FULLSTACK_AI_RULES = `# Full Stack Development
 - **Framework-Specific Commands**: Use appropriate commands based on the selected backend framework
 - **Clear Labeling**: Label each terminal command block with whether it's for frontend or backend
 
-## Framework-Specific Terminal Commands
-
-### Django Commands (Backend Terminal)
-- Install dependencies: <dyad-run-backend-terminal-cmd description="Install Python dependencies">pip install -r requirements.txt</dyad-run-backend-terminal-cmd>
-- Run migrations: <dyad-run-backend-terminal-cmd description="Apply database migrations">python manage.py migrate</dyad-run-backend-terminal-cmd>
-- Create migrations: <dyad-run-backend-terminal-cmd description="Create database migrations">python manage.py makemigrations</dyad-run-backend-terminal-cmd>
-- Start server: <dyad-run-backend-terminal-cmd description="Start Django development server">python manage.py runserver 8000</dyad-run-backend-terminal-cmd>
-- Create superuser: <dyad-run-backend-terminal-cmd description="Create Django superuser">python manage.py createsuperuser</dyad-run-backend-terminal-cmd>
-- Collect static files: <dyad-run-backend-terminal-cmd description="Collect static files">python manage.py collectstatic</dyad-run-backend-terminal-cmd>
-
-### FastAPI Commands (Backend Terminal)
-- Install dependencies: <dyad-run-backend-terminal-cmd description="Install Python dependencies">pip install -r requirements.txt</dyad-run-backend-terminal-cmd>
-- Start server: <dyad-run-backend-terminal-cmd description="Start FastAPI server">uvicorn main:app --reload --host 0.0.0.0 --port 8000</dyad-run-backend-terminal-cmd>
-- Run with hot reload: <dyad-run-backend-terminal-cmd description="Run FastAPI with hot reload">uvicorn main:app --reload</dyad-run-backend-terminal-cmd>
-- Generate client: <dyad-run-backend-terminal-cmd description="Generate OpenAPI client">python -c "from main import app; print(app.openapi())"</dyad-run-backend-terminal-cmd>
-
-### Flask Commands (Backend Terminal)
-- Install dependencies: <dyad-run-backend-terminal-cmd description="Install Python dependencies">pip install -r requirements.txt</dyad-run-backend-terminal-cmd>
-- Start server: <dyad-run-backend-terminal-cmd description="Start Flask development server">python app.py</dyad-run-backend-terminal-cmd>
-- Start with Flask CLI: <dyad-run-backend-terminal-cmd description="Start Flask with CLI">flask run --host=0.0.0.0 --port=5000</dyad-run-backend-terminal-cmd>
-- Initialize database: <dyad-run-backend-terminal-cmd description="Initialize Flask-Migrate">flask db init</dyad-run-backend-terminal-cmd>
-
-### Node.js Commands (Backend Terminal)
-- Install dependencies: <dyad-run-backend-terminal-cmd description="Install Node.js dependencies">npm install</dyad-run-backend-terminal-cmd>
-- Start server: <dyad-run-backend-terminal-cmd description="Start production server">npm start</dyad-run-backend-terminal-cmd>
-- Development mode: <dyad-run-backend-terminal-cmd description="Start development server">npm run dev</dyad-run-backend-terminal-cmd>
-- Build for production: <dyad-run-backend-terminal-cmd description="Build for production">npm run build</dyad-run-backend-terminal-cmd>
-
-### Frontend Commands (Frontend Terminal)
-- Install dependencies: <dyad-run-frontend-terminal-cmd description="Install frontend dependencies">npm install</dyad-run-frontend-terminal-cmd>
-- Start development server: <dyad-run-frontend-terminal-cmd description="Start frontend development server">npm run dev</dyad-run-frontend-terminal-cmd>
-- Build for production: <dyad-run-frontend-terminal-cmd description="Build frontend for production">npm run build</dyad-run-frontend-terminal-cmd>
-- Run tests: <dyad-run-frontend-terminal-cmd description="Run frontend tests">npm test</dyad-run-frontend-terminal-cmd>
-- Lint code: <dyad-run-frontend-terminal-cmd description="Lint frontend code">npm run lint</dyad-run-frontend-terminal-cmd>
+## IMPORTANT: Terminal Command Management
+
+**CRITICAL RULE: You must NEVER output <dyad-run-*-terminal-cmd> tags in your responses.** These tags are for system-internal use only and will cause errors if you attempt to use them.
+
+The system automatically handles ALL terminal operations:
+- Server startup when users click "Run App"
+- Dependency installation during app creation
+- Database migrations and setup
+- All other terminal commands
+
+Your role is strictly limited to creating and modifying code files. Do not attempt to execute any terminal commands.
+
+## Server Management
+
+**DO NOT attempt to run backend servers manually.** The system automatically handles server startup when users click the "Run App" button. You should focus on creating code files and using terminal commands only for installation, migrations, and other setup tasks. The system will detect the framework and start the appropriate server automatically.
 
 ## Integration Best Practices
 - Design clean API contracts between frontend and backend
@@ -631,6 +600,10 @@ const FASTAPI_AI_RULES = `# FastAPI Backend Development
 - Use background tasks for long-running operations
 - Implement rate limiting and security measures
 - Add proper authentication and authorization
+
+## Server Management
+
+**DO NOT attempt to run the FastAPI server manually.** The system automatically handles server startup when users click the "Run App" button. You should focus ONLY on creating and modifying code files. All server operations, dependency installation, and terminal commands are handled automatically by the system.
 `;
 
 const FLASK_AI_RULES = `# Flask Backend Development