orchestrix 16.1.6 → 16.1.8

package/lib/embedded/start-orchestrix.sh

@@ -254,12 +254,20 @@ AGENT_LOAD_WAIT=15
 # Auto-start workflow command (sent to SM window)
 AUTO_START_COMMAND="1"
 
+# Language flag: read from $ORCHESTRIX_LANG (e.g., "zh") or empty for English.
+# Yuri sets this before calling start-orchestrix.sh to propagate frontend locale.
+LANG_FLAG=""
+if [ -n "$ORCHESTRIX_LANG" ] && [ "$ORCHESTRIX_LANG" != "en" ]; then
+    LANG_FLAG="--lang=$ORCHESTRIX_LANG"
+    echo "🌐 Language: $ORCHESTRIX_LANG"
+fi
+
 # Agent activation commands (MCP version uses /o command)
 declare -a AGENT_COMMANDS=(
-    "/o architect"   # Window 0 - Architect
-    "/o sm"          # Window 1 - SM
-    "/o dev"         # Window 2 - Dev
-    "/o qa"          # Window 3 - QA
+    "/o architect $LANG_FLAG"   # Window 0 - Architect
+    "/o sm $LANG_FLAG"          # Window 1 - SM
+    "/o dev $LANG_FLAG"         # Window 2 - Dev
+    "/o qa $LANG_FLAG"          # Window 3 - QA
 )
 
 declare -a AGENT_NAMES=(

package/lib/embedded/yuri.md

@@ -23,6 +23,22 @@ You are the **product & engineering lead** who:
 
 ---
 
+## Language (i18n)
+
+**Check for `--lang` parameter** when activated. Example: `/yuri --lang=zh`
+
+| Parameter | Behavior |
+|-----------|----------|
+| `--lang=zh` | All Yuri output in **简体中文**. Agents activated with `--lang=zh`. |
+| `--lang=en` or omitted | All output in **English** (default). |
+
+When `--lang` is set:
+1. **Yuri speaks** in the specified language (greetings, status updates, questions)
+2. **Agents in op-session** are activated with the same `--lang` flag: `/o analyst --lang=zh`
+3. The language is **persistent** for the entire session — no need to repeat on each command
+
+---
+
 ## Architecture
 
 ```
@@ -174,8 +190,9 @@ sleep 12
 #### Step 2: Run planning agents sequentially
 
 ```bash
-# Activate first agent
-tmux send-keys -t "$OP_SESSION:planning" "/o analyst"
+# Activate first agent (pass --lang if set during /yuri activation)
+# Example: LANG_FLAG="--lang=zh" if activated with /yuri --lang=zh, else empty
+tmux send-keys -t "$OP_SESSION:planning" "/o analyst $LANG_FLAG"
 sleep 1
 tmux send-keys -t "$OP_SESSION:planning" Enter
 sleep 12  # Wait for agent load via MCP
@@ -200,7 +217,7 @@ tmux send-keys -t "$OP_SESSION:planning" Enter
 sleep 2
 
 # Activate next agent
-tmux send-keys -t "$OP_SESSION:planning" "/o pm"
+tmux send-keys -t "$OP_SESSION:planning" "/o pm $LANG_FLAG"
 sleep 1
 tmux send-keys -t "$OP_SESSION:planning" Enter
 sleep 12
@@ -237,10 +254,10 @@ tmux kill-session -t "$OP_SESSION"
 # Launch dev session with same op-{name}
 # start-orchestrix.sh reads ORCHESTRIX_SESSION and uses it as the session name
 # instead of its default "orchestrix-{repo-id}" naming.
-ORCHESTRIX_SESSION="$OP_SESSION" bash "$WORK_DIR/.orchestrix-core/scripts/start-orchestrix.sh"
+ORCHESTRIX_SESSION="$OP_SESSION" ORCHESTRIX_LANG="$LANG" bash "$WORK_DIR/.orchestrix-core/scripts/start-orchestrix.sh"
 ```
 
-**Important**: Pass `ORCHESTRIX_SESSION` inline (not `export`) to avoid polluting Yuri's own shell environment. The script creates a new `op-{name}` session with 4 dev agent windows.
+**Important**: Pass `ORCHESTRIX_SESSION` and `ORCHESTRIX_LANG` inline (not `export`) to avoid polluting Yuri's own shell environment. `$LANG` is `zh` or `en` based on your `--lang` activation parameter. The script creates a new `op-{name}` session with 4 dev agent windows, all using the same language.
 
 ### Phase B: Remote Development Monitoring
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "orchestrix",
-  "version": "16.1.6",
+  "version": "16.1.8",
   "description": "Install Orchestrix multi-agent infrastructure into any project. One command: npx orchestrix install",
   "bin": {
     "orchestrix": "bin/o8x.js"