CliWrap 3.4.4

CliWrap

🟢 Project status: active^[?]

CliWrap is a library for interacting with external command line interfaces. It provides a convenient model for launching processes, redirecting input and output streams, awaiting completion, handling cancellation, and more.

Terms of use

By using this project or its source code, for any purpose and in any shape or form, you grant your implicit agreement to all the following statements:

• You condemn Russia and its military aggression against Ukraine
• You recognize that Russia is an occupant that unlawfully invaded a sovereign state
• You support Ukraine's territorial integrity, including its claims over temporarily occupied territories of Crimea and Donbas
• You reject false narratives perpetuated by Russian state propaganda

To learn more about the war and how you can help, click here. Glory to Ukraine! 🇺🇦

Install

• 📦 NuGet: dotnet add package CliWrap

Features

• Airtight abstraction over System.Diagnostics.Process
• Fluent configuration interface
• Flexible support for piping
• Fully asynchronous and cancellation-aware API
• Designed with strict immutability in mind
• Provides safety against typical deadlock scenarios
• Tested on Windows, Linux, and macOS
• Targets .NET Standard 2.0+, .NET Core 3.0+, .NET Framework 4.6.1+
• No external dependencies

Usage

Video guide

📺 Watch Intro to CliWrap on YouTube for a deep look into the library and its features!

Quick overview

Similarly to a shell, CliWrap's base unit of work is a command — an object that encodes instructions for running a process. To build a command, start by calling Cli.Wrap(...) with the executable path, and then use the provided fluent interface to configure arguments, working directory, or other options. Once the command is configured, you can run it by calling ExecuteAsync():

using CliWrap;

var result = await Cli.Wrap("path/to/exe")
    .WithArguments("--foo bar")
    .WithWorkingDirectory("work/dir/path")
    .ExecuteAsync();

// Result contains:
// -- result.ExitCode        (int)
// -- result.StartTime       (DateTimeOffset)
// -- result.ExitTime        (DateTimeOffset)
// -- result.RunTime         (TimeSpan)

The code above spawns a child process with the configured command line arguments and working directory, and then asynchronously waits for it to exit. After the task has completed, it resolves to a CommandResult object that contains the process exit code and other related information.

⚠️ CliWrap will throw an exception if the underlying process returns a non-zero exit code, as it usually indicates an error. You can override this behavior by disabling result validation using WithValidation(CommandResultValidation.None).

By default, the process's standard input, output and error streams are routed to CliWrap's equivalent of the null device, which represents an empty source and a target that discards all data. You can change this by calling WithStandardInputPipe(...), WithStandardOutputPipe(...), or WithStandardErrorPipe(...) to configure pipes for the corresponding streams:

var stdOutBuffer = new StringBuilder();
var stdErrBuffer = new StringBuilder();

// ⚠ This particular example can also be simplified with ExecuteBufferedAsync().
// Continue reading below!
var result = await Cli.Wrap("path/to/exe")
    .WithArguments("--foo bar")
    .WithWorkingDirectory("work/dir/path")
    .WithStandardOutputPipe(PipeTarget.ToStringBuilder(stdOutBuffer))
    .WithStandardErrorPipe(PipeTarget.ToStringBuilder(stdErrBuffer))
    .ExecuteAsync();

// Contains stdOut/stdErr buffered in-memory as string
var stdOut = stdOutBuffer.ToString();
var stdErr = stdErrBuffer.ToString();

This example command is configured to decode the data written to standard output and error streams as text, and append it to the corresponding StringBuilder buffers. After the execution is complete, these buffers can be inspected to see what the process has printed to the console.

Handling command output is a very common use case, so CliWrap offers a few high-level execution models to make these scenarios simpler. In particular, the same thing shown above can also be achieved more succinctly with the ExecuteBufferedAsync() extension method:

using CliWrap;
using CliWrap.Buffered;

// Calling `ExecuteBufferedAsync()` instead of `ExecuteAsync()`
// implicitly configures pipes that write to in-memory buffers.
var result = await Cli.Wrap("path/to/exe")
    .WithArguments("--foo bar")
    .WithWorkingDirectory("work/dir/path")
    .ExecuteBufferedAsync();

// Result contains:
// -- result.StandardOutput  (string)
// -- result.StandardError   (string)
// -- result.ExitCode        (int)
// -- result.StartTime       (DateTimeOffset)
// -- result.ExitTime        (DateTimeOffset)
// -- result.RunTime         (TimeSpan)

⚠️ Be mindful when using ExecuteBufferedAsync(). Programs can write arbitrary data (including binary) to output and error streams, which may be impractical to buffer in-memory. For more advanced scenarios, CliWrap also provides other piping options, which are covered in the piping section.

Command configuration

The fluent interface provided by the command object allows you to configure various options related to its execution. Below list covers all available configuration methods and their usage.

💡 Command is an immutable object — all configuration methods listed here create a new instance instead of modifying the existing one.

WithArguments(...)

Sets the command line arguments passed to the child process.

Default: empty.

Examples:

• Set arguments from a string:

var cmd = Cli.Wrap("git")
    .WithArguments("commit -m \"my commit\"");

• Set arguments from a list — each element is treated as a separate argument and spaces are escaped automatically:

var cmd = Cli.Wrap("git")
    .WithArguments(new[] {"commit", "-m", "my commit"});

• Set arguments using a builder — same as above, but also works with non-string arguments and can be enhanced with your own extension methods:

var cmd = Cli.Wrap("git")
    .WithArguments(args => args
        .Add("clone")
        .Add("https://github.com/Tyrrrz/CliWrap")
        .Add("--depth")
        .Add(20));

⚠️ String overload of WithArguments(...) only works well when the arguments are short, simple, and not expected to change. In all other scenarios, both the array and builder overloads of WithArguments(...) offer a far more flexible alternative.

WithWorkingDirectory(...)

Sets the working directory of the child process.

Default: current working directory, i.e. Directory.GetCurrentDirectory().

Example:

var cmd = Cli.Wrap("git")
    .WithWorkingDirectory("c:/projects/my project/");

WithEnvironmentVariables(...)

Sets additional environment variables exposed to the child process.

Default: empty.

Examples:

• Set environment variables from a dictionary:

var cmd = Cli.Wrap("git")
    .WithEnvironmentVariables(new Dictionary<string, string?>
    {
        ["GIT_AUTHOR_NAME"] = "John",
        ["GIT_AUTHOR_EMAIL"] = "john@email.com"
    });

• Set environment variables using a builder:

var cmd = Cli.Wrap("git")
    .WithEnvironmentVariables(env => env
        .Set("GIT_AUTHOR_NAME", "John")
        .Set("GIT_AUTHOR_EMAIL", "john@email.com"));

💡 Environment variables configured using WithEnvironmentVariables(...) are applied on top of those inherited from the parent process. If you need to remove an inherited variable, simply set its value to null.

WithCredentials(...)

Sets domain, name and password of the user, under whom the child process is started.

Default: no credentials.

Examples:

• Set credentials directly:

var cmd = Cli.Wrap("git")
    .WithCredentials(new Credentials(
        "some_workspace",
        "johndoe",
        "securepassword123"
    ));

• Set credentials using a builder:

var cmd = Cli.Wrap("git")
    .WithCredentials(creds => creds
       .SetDomain("some_workspace")
       .SetUserName("johndoe")
       .SetPassword("securepassword123"));

⚠️ Running a process under a different username is supported across all platforms, but the domain and password options only work on Windows.

WithValidation(...)

Sets the strategy for validating the result of an execution.

Accepted values:

• CommandResultValidation.None — no validation
• CommandResultValidation.ZeroExitCode — ensures zero exit code when the process exits

Default: CommandResultValidation.ZeroExitCode.

Examples:

• Enable validation — will throw an exception if the process exits with a non-zero exit code:

var cmd = Cli.Wrap("git")
    .WithValidation(CommandResultValidation.ZeroExitCode);

• Disable validation:

var cmd = Cli.Wrap("git")
    .WithValidation(CommandResultValidation.None);

WithStandardInputPipe(...)

Sets the pipe source that will be used for the standard input stream of the process.

Default: PipeSource.Null.

Read more about this method in the piping section.

WithStandardOutputPipe(...)

Sets the pipe target that will be used for the standard output stream of the process.

Default: PipeTarget.Null.

Read more about this method in the piping section.

WithStandardErrorPipe(...)

Sets the pipe target that will be used for the standard error stream of the process.

Default: PipeTarget.Null.

Read more about this method in the piping section.

Piping

CliWrap provides a very powerful and flexible piping model that allows you to redirect process's streams, transform input and output data, and even chain multiple commands together with minimal effort. At its core, it's based on two abstractions: PipeSource which provides data for standard input stream, and PipeTarget which reads data coming from standard output or standard error streams.

By default, command's input pipe is set to PipeSource.Null and the output and error pipes are set to PipeTarget.Null. These objects effectively represent no-op stubs that provide empty input and discard all output respectively.

You can specify your own PipeSource and PipeTarget instances by calling the corresponding configuration methods on the command:

await using var input = File.OpenRead("input.txt");
await using var output = File.Create("output.txt");

await Cli.Wrap("foo")
    .WithStandardInputPipe(PipeSource.FromStream(input))
    .WithStandardOutputPipe(PipeTarget.ToStream(output))
    .ExecuteAsync();

Alternatively, pipes can also be configured in a slightly terser way by using pipe operators:

await using var input = File.OpenRead("input.txt");
await using var output = File.Create("output.txt");

await (input | Cli.Wrap("foo") | output).ExecuteAsync();

Both PipeSource and PipeTarget have many factory methods that let you create pipe implementations for different scenarios:

• PipeSource:
  • PipeSource.Null — represents an empty pipe source
  • PipeSource.FromStream(...) — pipes data from any readable stream
  • PipeSource.FromFile(...) — pipes data from a file
  • PipeSource.FromBytes(...) — pipes data from a byte array
  • PipeSource.FromString(...) — pipes from a text string
  • PipeSource.FromCommand(...) — pipes data from standard output of another command
• PipeTarget:
  • PipeTarget.Null — represents a pipe target that discards all data
  • PipeTarget.ToStream(...) — pipes data into any writable stream
  • PipeTarget.ToFile(...) — pipes data into a file
  • PipeTarget.ToStringBuilder(...) — pipes data as text into StringBuilder
  • PipeTarget.ToDelegate(...) — pipes data as text, line-by-line, into Action<string> or Func<string, Task>
  • PipeTarget.Merge(...) — merges multiple outbound pipes by replicating the same data across all of them

⚠️ Using PipeTarget.Null results in the corresponding stream (standard output or standard error) not being opened for the underlying process at all. In the vast majority of cases, this behavior should be functionally equivalent to piping to a null stream, but without the performance overhead of consuming and discarding unneeded data. This may be undesirable in certain situations — in which case it's recommended to pipe to a null stream explicitly using PipeTarget.ToStream(Stream.Null).

Below you can see some examples of what you can achieve with the help of CliWrap's piping feature:

• Pipe a string into stdin:

var cmd = "Hello world" | Cli.Wrap("foo");
await cmd.ExecuteAsync();

• Pipe stdout as text into a StringBuilder:

var stdOutBuffer = new StringBuilder();

var cmd = Cli.Wrap("foo") | stdOutBuffer;
await cmd.ExecuteAsync();

• Pipe a binary HTTP stream into stdin:

using var httpClient = new HttpClient();
await using var input = await httpClient.GetStreamAsync("https://example.com/image.png");

var cmd = input | Cli.Wrap("foo");
await cmd.ExecuteAsync();

• Pipe stdout of one command into stdin of another:

var cmd = Cli.Wrap("foo") | Cli.Wrap("bar") | Cli.Wrap("baz");
await cmd.ExecuteAsync();

• Pipe stdout and stderr into stdout and stderr of the parent process:

await using var stdOut = Console.OpenStandardOutput();
await using var stdErr = Console.OpenStandardError();

var cmd = Cli.Wrap("foo") | (stdOut, stdErr);
await cmd.ExecuteAsync();

• Pipe stdout into a delegate:

var cmd = Cli.Wrap("foo") | Debug.WriteLine;
await cmd.ExecuteAsync();

• Pipe stdout into a file and stderr into a StringBuilder:

var buffer = new StringBuilder();

var cmd = Cli.Wrap("foo") |
    (PipeTarget.ToFile("output.txt"), PipeTarget.ToStringBuilder(buffer));

await cmd.ExecuteAsync();

• Pipe stdout into multiple files simultaneously:

var target = PipeTarget.Merge(
    PipeTarget.ToFile("file1.txt"),
    PipeTarget.ToFile("file2.txt"),
    PipeTarget.ToFile("file3.txt")
);

var cmd = Cli.Wrap("foo") | target;
await cmd.ExecuteAsync();

• Pipe a string into stdin of one command, stdout of that command into stdin of another command, and then stdout and stderr of the last command into stdout and stderr of the parent process:

var cmd =
    "Hello world" |
    Cli.Wrap("foo").WithArguments("aaa") |
    Cli.Wrap("bar").WithArguments("bbb") |
    (Console.WriteLine, Console.Error.WriteLine);

await cmd.ExecuteAsync();

Execution models

CliWrap provides a few high-level execution models that offer alternative ways to reason about commands. These are essentially just extension methods that work by leveraging the piping feature shown earlier.

Buffered execution

This execution model lets you run a process while buffering its standard output and error streams in-memory. The buffered data can then be accessed after the command finished executing.

In order to execute a command with buffering, call the ExecuteBufferedAsync() extension method:

using CliWrap;
using CliWrap.Buffered;

var result = await Cli.Wrap("path/to/exe")
    .WithArguments("--foo bar")
    .ExecuteBufferedAsync();

var exitCode = result.ExitCode;
var stdOut = result.StandardOutput;
var stdErr = result.StandardError;

By default, ExecuteBufferedAsync() assumes that the underlying process uses default encoding (Console.OutputEncoding) for writing text to the console. To override this, specify the encoding explicitly by using one of the available overloads:

// Treat both stdout and stderr as UTF8-encoded text streams
var result = await Cli.Wrap("path/to/exe")
    .WithArguments("--foo bar")
    .ExecuteBufferedAsync(Encoding.UTF8);

// Treat stdout as ASCII-encoded and stderr as UTF8-encoded
var result = await Cli.Wrap("path/to/exe")
    .WithArguments("--foo bar")
    .ExecuteBufferedAsync(Encoding.ASCII, Encoding.UTF8);

Pull-based event stream

Besides executing a command as a task, CliWrap also supports an alternative model, in which the execution is represented as an event stream. This lets you start a command and react to the events it produces in real-time.

Those events are:

• StartedCommandEvent — received just once, when the command starts executing (contains process ID)
• StandardOutputCommandEvent — received every time the underlying process writes a new line to the output stream (contains the text as string)
• StandardErrorCommandEvent — received every time the underlying process writes a new line to the error stream (contains the text as string)
• ExitedCommandEvent — received just once, when the command finishes executing (contains exit code)

To execute a command as a pull-based event stream, use the ListenAsync() extension method:

using CliWrap;
using CliWrap.EventStream;

var cmd = Cli.Wrap("foo").WithArguments("bar");

await foreach (var cmdEvent in cmd.ListenAsync())
{
    switch (cmdEvent)
    {
        case StartedCommandEvent started:
            _output.WriteLine($"Process started; ID: {started.ProcessId}");
            break;
        case StandardOutputCommandEvent stdOut:
            _output.WriteLine($"Out> {stdOut.Text}");
            break;
        case StandardErrorCommandEvent stdErr:
            _output.WriteLine($"Err> {stdErr.Text}");
            break;
        case ExitedCommandEvent exited:
            _output.WriteLine($"Process exited; Code: {exited.ExitCode}");
            break;
    }
}

The ListenAsync() method starts the command and returns an object of type IAsyncEnumerable<CommandEvent>, which you can iterate using the await foreach construct introduced in C# 8. When using this execution model, back pressure is facilitated by locking the pipes between each iteration of the loop, preventing unnecessary buffering of data in-memory.

💡 Similarly to ExecuteBufferedAsync(), you can specify custom encoding for ListenAsync() using one of its overloads.

Push-based event stream

Similarly to the pull-based stream, you can also execute a command as a push-based event stream instead:

using CliWrap;
using CliWrap.EventStream;
using System.Reactive;

await cmd.Observe().ForEachAsync(cmdEvent =>
{
    switch (cmdEvent)
    {
        case StartedCommandEvent started:
            _output.WriteLine($"Process started; ID: {started.ProcessId}");
            break;
        case StandardOutputCommandEvent stdOut:
            _output.WriteLine($"Out> {stdOut.Text}");
            break;
        case StandardErrorCommandEvent stdErr:
            _output.WriteLine($"Err> {stdErr.Text}");
            break;
        case ExitedCommandEvent exited:
            _output.WriteLine($"Process exited; Code: {exited.ExitCode}");
            break;
    }
});

In this case, Observe() returns a cold IObservable<CommandEvent> that represents an observable stream of command events. You can use the set of extensions provided by Rx.NET to transform, filter, throttle, or otherwise manipulate this stream.

Unlike with the pull-based event stream, this execution model does not involve any back pressure, meaning that the data is pushed to the observer at the rate it becomes available.

💡 Similarly to ExecuteBufferedAsync(), you can specify custom encoding for Observe() using one of its overloads.

Combining execution models with custom pipes

The different execution models shown above are based on the piping model, but those two concepts are not mutually exclusive. When running a command this way, existing pipe configurations are preserved and extended using PipeTarget.Merge().

This means that you can, for example, pipe a command to a file and also execute it as an event stream without any issues:

var cmd =
    PipeSource.FromFile("input.txt") |
    Cli.Wrap("foo") |
    PipeTarget.ToFile("output.txt");

// Iterate as an event stream and pipe to a file at the same time
// (pipes are combined, not overriden)
await foreach (var cmdEvent in cmd.ListenAsync())
{
    // ...
}

Timeout and cancellation

Command execution is asynchronous in nature as it involves a completely separate process. In many cases, it may be useful to implement an abortion mechanism to stop the execution before it finishes, either through a manual trigger or a timeout.

To do that, just pass the corresponding CancellationToken when calling ExecuteAsync():

using var cts = new CancellationTokenSource();

// Cancel automatically after a timeout of 10 seconds
cts.CancelAfter(TimeSpan.FromSeconds(10));

var result = await Cli.Wrap("path/to/exe").ExecuteAsync(cts.Token);

In the event of a cancellation request, the underlying process gets killed and ExecuteAsync() throws an exception of type OperationCanceledException (or its derivative, TaskCanceledException). You will need to catch this exception in your code to recover from cancellation:

try
{
    await Cli.Wrap("path/to/exe").ExecuteAsync(cts.Token);
}
catch (OperationCanceledException)
{
    // Command was cancelled
}

💡 Similarly to ExecuteAsync(), cancellation is also supported by ExecuteBufferedAsync(), ListenAsync(), and Observe().

💡 You can read more about CancellationToken in .NET here.

Retrieving process ID

The task returned by ExecuteAsync() and ExecuteBufferedAsync() is in fact not a regular Task<T>, but an instance of CommandTask<T>. This is a special awaitable object that contains additional information related to the currently executing command.

You can inspect the task while it's running to get the ID of the process that was started by the associated command:

var task = Cli.Wrap("path/to/exe")
    .WithArguments("--foo bar")
    .ExecuteAsync();

// Get the process ID (for example, for logging purposes)
var processId = task.ProcessId;

// Wait for the task to complete
await task;