# Spawn Process

> Guide for writing subprocess execution code using the vp_command crate

- Skill: `voidzero-dev/spawn-process` (Agent Skill)
- Install (CLI): `npx skillmds@latest add voidzero-dev/spawn-process`
- Raw SKILL.md: https://api.skillmd.com/api/skills/voidzero-dev/spawn-process/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: voidzero-dev (https://skillmd.com/u/voidzero-dev)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/voidzero-dev/spawn-process

---


# Add Subprocess Execution Code

When writing Rust code that needs to spawn subprocesses (resolve binaries, build commands, execute programs), always use the `vp_command` crate. Never use `which`, `tokio::process::Command::new`, or `std::process::Command::new` directly.

## Available APIs

### `vp_command::resolve_bin(name, path_env, cwd)` — Resolve a binary name to an absolute path

Handles PATHEXT (`.cmd`/`.bat`) on Windows. Pass `None` for `path_env` to search the current process PATH.

```rust
// Resolve using current PATH
let bin = vp_command::resolve_bin("node", None, &cwd)?;

// Resolve using a custom PATH
let custom_path = std::ffi::OsString::from(&path_env_str);
let bin = vp_command::resolve_bin("eslint", Some(&custom_path), &cwd)?;
```

### `vp_command::build_command(bin_path, cwd)` — Build a command for a pre-resolved binary

Returns `tokio::process::Command` with cwd, inherited stdio, and `fix_stdio_streams` on Unix already configured. Add args, envs, or override stdio as needed.

```rust
let bin = vp_command::resolve_bin("eslint", None, &cwd)?;
let mut cmd = vp_command::build_command(&bin, &cwd);
cmd.args(&[".", "--fix"]);
cmd.env("NODE_ENV", "production");
let mut child = cmd.spawn()?;
let status = child.wait().await?;
```

### `vp_command::build_shell_command(shell_cmd, cwd)` — Build a shell command

Uses `/bin/sh -c` on Unix, `cmd.exe /C` on Windows. Same stdio and `fix_stdio_streams` setup as `build_command`.

```rust
let mut cmd = vp_command::build_shell_command("echo hello && ls", &cwd);
let mut child = cmd.spawn()?;
let status = child.wait().await?;
```

### `vp_command::run_command(bin_name, args, envs, cwd)` — Resolve + build + run in one call

Combines resolve_bin, build_command, and status().await. The `envs` HashMap must include `"PATH"` if you want custom PATH resolution.

```rust
let envs = HashMap::from([("PATH".to_string(), path_value)]);
let status = vp_command::run_command("node", &["--version"], &envs, &cwd).await?;
```

## Dependency Setup

Add `vp_command` to the crate's `Cargo.toml`:

```toml
[dependencies]
vp_command = { workspace = true }
```

Do NOT add `which` as a direct dependency — binary resolution goes through `vp_command::resolve_bin`.

## Exception

`crates/vp_global_cli/src/shim/exec.rs` uses synchronous `std::process::Command` with Unix `exec()` for process replacement. This is the only place that bypasses `vp_command`.