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

# ide

Automatically connect to an IDE on startup if exactly one valid IDE is available.

## Type

**CLI** — boolean flag

## Syntax

```
claude --ide
```

## Default

off

## Description

When set, Claude Code attempts to connect to an active IDE integration on startup. If exactly one valid IDE connection is available (e.g., a VS Code or JetBrains instance with the Claude Code extension installed and running), it connects automatically.

If multiple IDEs are available, connection is ambiguous and the flag has no effect (or prompts for selection depending on the version).

Use cases:
- Launching Claude from a terminal within a development workflow where IDE context should be injected
- Automated scripts that should augment an active editor session

## Builder API

Use `with_ide()` — Boolean flag: auto-connect to IDE on startup.

```rust
use claude_runner_core::ClaudeCommand;

let cmd = ClaudeCommand::new()
  .with_ide( true )
  .with_message( "Run with IDE integration" );
```

## Examples

```bash
# Launch with IDE context if one is running
claude --ide "Help me with this file"

# In a development alias
alias cide='claude --ide'
```

## Notes

- Requires the Claude Code IDE extension installed in the connected IDE
- Only auto-connects when exactly one valid IDE is running; multiple IDEs require manual selection
- The IDE integration provides file context, cursor position, and active editor state to Claude