claude_runner_core 1.0.0

Claude Code process execution with builder pattern
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58

# session_id

Use a specific session UUID for the conversation.

## Type

**CLI** — UUID string value

## Syntax

```
claude --session-id <uuid>
```

## Default

Auto-generated UUID for each new session

## Description

Forces Claude Code to use a specific UUID as the session identifier instead of auto-generating one. The UUID must be a valid v4 UUID format (`xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx`).

Use cases:
- Deterministic session IDs for testing/reproducibility
- Pre-assigning a session ID before starting the conversation
- Coordinating session IDs across multiple tools or systems

This is distinct from `--resume` — `--session-id` assigns the ID for a new session, while `--resume` selects an existing session to continue.

## Builder API

Use `with_session_id()` — Accepts a UUID string for the session.

```rust
use claude_runner_core::ClaudeCommand;

let cmd = ClaudeCommand::new()
  .with_session_id( "550e8400-e29b-41d4-a716-446655440000" )
  .with_message( "Run with explicit session ID" );
```

## Examples

```bash
# Start a session with a known UUID
claude --session-id 550e8400-e29b-41d4-a716-446655440000

# Use in automated pipeline for traceability
SESSION_ID=$(uuidgen)
claude --session-id "$SESSION_ID" --print "Process this task"
echo "Session: $SESSION_ID" >> pipeline.log
```

## Notes

- Invalid UUIDs will cause claude to reject the argument
- After the session completes, it can be resumed via `--resume 550e8400-...`
- Useful for audit trails where session IDs must be logged before execution begins