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

# plugin_dir

Load Claude Code plugins from directories for the current session only.

## Type

**CLI** — one or more path values

## Syntax

```
claude --plugin-dir <path> [<path> ...]
```

## Default

None (only globally installed plugins)

## Description

Loads Claude Code plugins from the specified directories for this session without installing them globally. Each directory should contain a valid Claude Code plugin.

Plugins extend Claude Code with new slash commands, tools, and capabilities. This flag allows using plugins for a specific invocation without the need for `claude plugin install`.

Multiple plugin directories can be specified space-separated, and the flag is repeatable.

## Builder API

Use `with_plugin_dir()` — Repeated-flag: each call adds one plugin directory path.

```rust
use claude_runner_core::ClaudeCommand;

let cmd = ClaudeCommand::new()
  .with_plugin_dir( "/home/user/.claude/plugins" )
  .with_message( "Load plugins from custom dir" );
```

## Examples

```bash
# Load a local plugin for this session
claude --plugin-dir ./my-plugin --print "Use the custom tool"

# Multiple plugin directories
claude --plugin-dir ./plugin-a ./plugin-b --print "Use combined plugins"

# Development workflow: test plugin without installing
claude --plugin-dir ./dev/my-plugin --print "Test the new tool"
```

## Notes

- Plugin directories must contain a valid `package.json` with Claude Code plugin configuration
- Session-only: doesn't persist to global plugin installation
- See `claude plugin install` for permanent plugin installation
- Useful for plugin development and testing workflows