Bug: kugetsu start fails - opencode message argument must come before flags #53

New Issue

shoko · 2026-03-31T23:25:40+02:00

shoko commented

2026-03-31 23:25:40 +02:00

Bug

kugetsu start fails to pass message to opencode.

Root Cause

opencode CLI requires message BEFORE flags:

opencode run "message" --session sid --workdir /path  # WORKS
opencode run --session sid "message" --workdir /path  # FAILS - shows help

But kugetsu puts message AFTER flags:

opencode run --fork --session "$base_session_id" "$message" --workdir "$worktree_path"

This causes opencode to ignore the message and show help instead.

Evidence

$ opencode run "Test message" --session ses_xxx
> build · MiniMax-M2.7
Test acknowledged.  # WORKS

$ opencode run --session ses_xxx "Test message"
opencode run [message..]
run opencode with a message

Positionals:
  message  message to send  [array] [default: []]
  # Shows help, message ignored

Impact

kugetsu start always fails to start dev agents
All task delegation via kugetsu start is broken
Dev agents can only be started via direct opencode run with correct argument order

Fix

In kugetsu script, change line 864 (and similar):

# BEFORE (broken):
opencode run --fork --session "$base_session_id" "$message" --workdir "$worktree_path"

# AFTER (correct):
opencode run "$message" --fork --session "$base_session_id" --workdir "$worktree_path"

Same fix needed for lines 862, 944, 946, 950, 952.

Workaround

Use direct opencode with message first:

opencode run "task description" --session sid --fork --workdir /path

## Bug `kugetsu start` fails to pass message to opencode. ## Root Cause opencode CLI requires message BEFORE flags: ```bash opencode run "message" --session sid --workdir /path # WORKS opencode run --session sid "message" --workdir /path # FAILS - shows help ``` But kugetsu puts message AFTER flags: ```bash opencode run --fork --session "$base_session_id" "$message" --workdir "$worktree_path" ``` This causes opencode to ignore the message and show help instead. ## Evidence ```bash $ opencode run "Test message" --session ses_xxx > build · MiniMax-M2.7 Test acknowledged. # WORKS $ opencode run --session ses_xxx "Test message" opencode run [message..] run opencode with a message Positionals: message message to send [array] [default: []] # Shows help, message ignored ``` ## Impact - `kugetsu start` always fails to start dev agents - All task delegation via `kugetsu start` is broken - Dev agents can only be started via direct `opencode run` with correct argument order ## Fix In `kugetsu` script, change line 864 (and similar): ```bash # BEFORE (broken): opencode run --fork --session "$base_session_id" "$message" --workdir "$worktree_path" # AFTER (correct): opencode run "$message" --fork --session "$base_session_id" --workdir "$worktree_path" ``` Same fix needed for lines 862, 944, 946, 950, 952. ## Workaround Use direct opencode with message first: ```bash opencode run "task description" --session sid --fork --workdir /path ```

shoko referenced this issue from a commit

2026-03-31 23:29:45 +02:00

fix: opencode message argument must come before flags

shoko referenced a pull request that will close this issue

2026-03-31 23:29:58 +02:00

fix: opencode message argument must come before flags #54

shoko closed this issue

2026-03-31 23:35:34 +02:00

shoko referenced this issue from a commit

2026-04-01 02:00:14 +02:00

fix: opencode message argument must come before flags in init

shoko referenced this issue