Choose the right attachment model

Host & Process Sessions

Use one session model from isolated command testing to a running Avalonia process.

Explore source ↗

Parent systemInspector

StatusActive

Modules2

RepositoryInspector/Inspector.Transport

Capability

Host mode targets an instrumented local runtime; process mode resolves an existing application by PID or name and consumes published live snapshots; stub mode supplies deterministic fixtures for workflow validation.

01
Instrumented host endpoints
02
PID or process-name targeting
03
Live snapshot availability signal
04
Deterministic stub fixtures

How it composes

From intent
to working system.

Resolve

Mode-specific arguments select a host endpoint, running process, or fixture.

Authorize

Client identity, version, secret, and requested scopes establish boundaries.

Persist

The returned session id survives across CLI invocations.

Fallback

Process mode reports whether live UI snapshots exist and otherwise exposes process metadata honestly.

Quick start

Adopt this
capability.

Start with the primary module, then add the related packages only when the application needs those layers. Replace VERSION with the current NuGet version.

dotnet add package Inspector.Host
dotnet add package Inspector.Transport

<PackageReference Include="Inspector.Host" Version="VERSION" />

<PackageVersion Include="Inspector.Host" Version="VERSION" />

# Instrumented application endpoint
inspector connect --mode host --address local://inspector --json

# Already-running application
inspector connect --mode process --name Inspector.SampleApp --json

# Deterministic command-flow fixture
inspector connect --mode stub --client-id tests --json