Skip to content

Commit ddf277f

Browse files
sky-xoclaude
andcommitted
docs(spawn): add output and naming details to help text
Clarify that spawn prints the agent name to stdout and explain how the naming system works with --name prefix and ULID suffix. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
1 parent f860da4 commit ddf277f

1 file changed

Lines changed: 12 additions & 1 deletion

File tree

internal/cli/spawn.go

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,18 @@ func newSpawnCmd() *cobra.Command {
2929
cmd := &cobra.Command{
3030
Use: "spawn <type> <task>",
3131
Short: "Spawn an agent",
32-
Long: "Spawn a Codex or Gemini agent to perform a task",
32+
Long: `Spawn a Codex or Gemini agent to perform a task.
33+
34+
On success, prints the agent name to stdout (e.g., "swift-falcon-7d1e").
35+
Use this name with peek, logs, and other commands.
36+
37+
Naming: --name sets a prefix; if omitted, an adjective-noun is auto-generated.
38+
A 4-char suffix is always appended to ensure uniqueness.
39+
40+
Examples:
41+
june spawn codex "fix the tests" --name refactor # Output: refactor-9c4f
42+
june spawn codex "add feature" # Output: swift-falcon-7d1e
43+
june peek swift-falcon-7d1e # Show new output`,
3344
Args: cobra.ExactArgs(2),
3445
RunE: func(cmd *cobra.Command, args []string) error {
3546
agentType := args[0]

0 commit comments

Comments
 (0)