Skip to content

wake --model rejects space-separated flag values #63

Description

@ikma-ricon

Problem

sessions wake --model=value ... works, but the documented/help shape with a space-separated flag value fails:

sessions wake --headless --model openai-codex/gpt-5.5 --message "Reply ok" <session>

Observed error:

[wake] ERROR unexpected word: openai-codex/gpt-5.5

Equals form works:

sessions wake --headless --model=openai-codex/gpt-5.5 --message "Reply ok" <session>

and launches pi with:

Model: openai-codex/gpt-5.5

Why it matters

The help text advertises:

--model <model>

which implies both common CLI forms should work. The space-separated form is also what agents naturally write after reading --help, and what existing examples tend to show for flags with values.

This came up while trying to run a local sessions wake peer-review with OpenAI (openai-codex/gpt-5.5) because Claude usage was exhausted.

Reproduction sketch

SMOKE_DIR=$(mktemp -d)
SESSION="model-smoke-$(date +%s)"

sessions new "$SESSION" --cwd "$SMOKE_DIR"

# Fails with unexpected word
sessions wake --headless --model openai-codex/gpt-5.5 --message "Reply ok" "$SESSION"

# Works
sessions wake --headless --model=openai-codex/gpt-5.5 --message "Reply ok" "$SESSION"

Acceptance criteria

  • sessions wake --model foo <session> parses the same as --model=foo.
  • Add a BATS regression test for the space-separated form.
  • If the root cause is a usage parser limitation rather than sessions-specific code, document the limitation and update examples/help accordingly.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions