Skip to content

fix: don't pass purpose as prompt when using workspace create --launch#20

Merged
ckrough merged 1 commit intomainfrom
nostalgic-hypatia
Dec 21, 2025
Merged

fix: don't pass purpose as prompt when using workspace create --launch#20
ckrough merged 1 commit intomainfrom
nostalgic-hypatia

Conversation

@ckrough
Copy link
Owner

@ckrough ckrough commented Dec 21, 2025

Summary

  • Fixed bug where workspace create -p "test" --launch was passing purpose as prompt even without --use-purpose
  • Removed purpose parameter from _launch_agent_in_workspace() helper function
  • Now consistent with agent launch which requires explicit --use-purpose flag

Test plan

  • Type check passes (uv run mypy src/agentspaces/cli/workspace.py)
  • All 318 tests pass (uv run pytest tests/)
  • Linting passes (uv run ruff check src/agentspaces/cli/workspace.py)

The --launch flag was passing the workspace purpose as a prompt to Claude
Code even without --use-purpose. This was inconsistent with `agent launch`
which correctly requires explicit --use-purpose flag.

Users who want purpose as prompt should use:
  agentspaces agent launch <workspace> --use-purpose
@ckrough ckrough merged commit a5d0920 into main Dec 21, 2025
5 checks passed
@ckrough ckrough deleted the nostalgic-hypatia branch December 27, 2025 19:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant