From 6faaf35113ea9d9933819ad64665dcfe9b5b34f0 Mon Sep 17 00:00:00 2001 From: Garry Tan Date: Sun, 5 Apr 2026 09:46:53 -0700 Subject: [PATCH] fix: add gstack-upgrade to OpenClaw dispatch routing Ensures "upgrade gstack" routes to a Claude Code session with /gstack-upgrade instead of Wintermute trying to handle it conversationally. --- openclaw/agents-gstack-section.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/openclaw/agents-gstack-section.md b/openclaw/agents-gstack-section.md index 3e4fef10..15d9b214 100644 --- a/openclaw/agents-gstack-section.md +++ b/openclaw/agents-gstack-section.md @@ -28,7 +28,7 @@ When asked for coding work, pick the dispatch tier: **HEAVY:** needs a specific gstack methodology → sessions_spawn(runtime: "acp", prompt: "Load gstack. Run /qa https://...") - Skills: /cso, /review, /qa, /ship, /investigate, /design-review, /benchmark + Skills: /cso, /review, /qa, /ship, /investigate, /design-review, /benchmark, /gstack-upgrade **FULL:** build a complete feature, multi-day scope, needs planning + review → sessions_spawn(runtime: "acp", prompt: "\n\n") @@ -46,5 +46,6 @@ When asked for coding work, pick the dispatch tier: - Can it be done in <10 lines of code? → **SIMPLE** - Does it touch multiple files but the approach is obvious? → **MEDIUM** - Does the user name a specific skill (/cso, /review, /qa)? → **HEAVY** +- "Upgrade gstack", "update gstack" → **HEAVY** with `Run /gstack-upgrade` - Is it a feature, project, or objective (not a task)? → **FULL** - Does the user want to PLAN something without implementing yet? → **PLAN**