claude-codes 2.1.165

Typed Rust SDK for the Claude Code agent CLI: serde models of its JSON-Lines (stream-json) protocol with streaming parsing, plus sync and async (Tokio) clients for driving Claude Code sessions, tools, and subagents.
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
59
60
61
62
63
64
65
66
67
68
69
70

# Integration Tests

This directory contains integration tests that interact with real Claude CLI services.

## Running Integration Tests

Integration tests are behind a feature flag and require a working Claude CLI installation.

### Prerequisites

1. Install Claude CLI: `npm install -g @anthropic-ai/claude-cli`
2. Authenticate: `claude login`
3. Verify installation: `claude --version`

### Running Tests

```bash
# Run all integration tests
cargo test --features integration-tests

# Run with output
cargo test --features integration-tests -- --nocapture

# Run a specific test
cargo test --features integration-tests test_async_client_basic_query
```

## Running Corpus Tests

Real Claude Code transcript JSONL coverage is opt-in because the corpus lives
outside the repository and can be large:

```bash
CLAUDE_CODES_CORPUS_DIR="$HOME/.claude/projects" \
  cargo test --features corpus-test parse_configured_claude_transcript_corpus -- --nocapture
```

The corpus test recursively scans every `.jsonl` file under the configured
directory, skips malformed JSON lines, parses valid lines with
`ClaudeOutput::parse_json_tolerant()`, prints counts by message type, and fails
on any valid JSON line that cannot be represented by the crate.

### Test Coverage

The integration tests cover:

- **Version Check**: Verifies Claude CLI is installed and accessible
- **Basic Queries**: Tests simple question/answer interactions with both async and sync clients
- **Conversations**: Tests multi-turn conversations with context retention
- **Tool Use**: Tests Claude's ability to use tools (when available)
- **Error Handling**: Tests behavior with invalid configurations

### CI/CD Note

Integration tests are NOT run in CI by default since they require:
- Claude CLI installation
- Valid authentication
- Network access to Claude services

To run them locally, use the feature flag as shown above.

### Writing New Integration Tests

When adding new integration tests:

1. Always use the `#[cfg(feature = "integration-tests")]` attribute
2. Use reasonable timeouts (30 seconds max)
3. Clean up resources (sessions) when possible
4. Document what the test is validating
5. Handle potential network failures gracefully