Start Orchestrator

Start the Orchestrator 3 Stream backend and frontend in background mode.

Updated Dec 25, 2025
One-click install
npx skills add https://github.com/PytaichukBohdan/DanaCockFightBot --skill start-orchestrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Start Orchestrator
Source: https://github.com/PytaichukBohdan/DanaCockFightBot/tree/main/.claude/skills/start-orchestrator
Command: npx skills add https://github.com/PytaichukBohdan/DanaCockFightBot --skill start-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Starts the Orchestrator 3 Stream application (backend + frontend) in background mode, enabling a quick boot of the full stack. This helps users respond to requests like "start the orchestrator", "launch orchestrator", or "open the orchestrator UI" without manual, multi-step setup.

Core Features & Use Cases

  • Background startup: Launches backend (FastAPI) and frontend (Vue/Vite) servers in the background.
  • Session and CWD flags: Supports --session and --cwd flags for the backend.
  • Unified UI access: Opens the frontend UI after both services are running.

Quick Start

To start the orchestrator, run the following:

  • Basic start: cd /path/to/apps/orchestrator_3_stream && ./start_be.sh & and ./start_fe.sh &
  • Open UI: open -a "Google Chrome" "http://127.0.0.1:5175"
  • Resume a session: cd /path/to/apps/orchestrator_3_stream && ./start_be.sh --session <session-id> &

Frequently Asked Questions about Start Orchestrator

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

FAQPage Schema
How do I start the Orchestrator backend and frontend in the background?

Start Orchestrator automates launching both the FastAPI backend and Vue/Vite frontend in background mode. Run the Skill to initialize both services simultaneously, which applies the necessary flags and opens the UI at http://127.0.0.1:5175 once both are ready.

What do I need installed to run the Orchestrator application?

Orchestrator requires Python with uv (Astral UV), Node.js with npm, PostgreSQL running, and the orchestrator located at apps/orchestrator_3_stream. The Skill verifies these prerequisites before starting the backend on port 8002 and frontend on port 5175.

Can I start an Orchestrator session from a specific working directory?

Yes, Start Orchestrator supports both --session and --cwd flags for the backend, allowing you to resume saved sessions and specify the working directory where the backend initializes.

What ports does the Orchestrator use, and can they be customized?

The backend runs on port 8002 (with fallback to 9403) and the frontend on port 5175. Start Orchestrator honors these defaults and supports configurable backend port settings through the automation.

How does automating Orchestrator startup save time over manual steps?

Manual startup requires running separate start_be.sh and start_fe.sh scripts, managing background processes, and opening the browser manually. Start Orchestrator consolidates these into one action, coordinating both services and opening the UI automatically.