AppClient

1. Install and update

On Windows x64, open an Administrator PowerShell window and run this Store command. It downloads the Suite installer as a verified bootstrap, then uses its install-appclient action to install the separately signed AppClient release. The Suite service is not installed by this command. It can also update an existing AppClient installation.

& ([scriptblock]::Create((irm 'https://store.createrun.ai/installer/developer-tools/appclient/install.ps1')))

Read the Windows script before running it. Both the Suite and AppClient Windows channels need a release; the Suite release must include the new install-appclient command. Existing older Suite installers cannot run this standalone action. The installed payload is under %ProgramFiles%\Createrun\AppClient\current and must contain the CLI and Createrun.AppClient.MSBuild.dll.

2. Diagnose a local build

AppClient has no doctor verb. On Windows, check the installed release marker, executable and MSBuild task together. A version file alone is not enough. Then run the actual app build and read the first CRAPPCLIENT001, 002 or 003 error if generation is blocked.

$appClient = Join-Path $env:ProgramFiles 'Createrun\AppClient\current'
Get-Content (Join-Path $appClient 'release-version.txt')
Test-Path (Join-Path $appClient 'createrun-appclient.exe')
Test-Path (Join-Path $appClient 'Createrun.AppClient.MSBuild.dll')
& (Join-Path $appClient 'createrun-appclient.exe') --help

If the files exist but a clone still points to an old tool path, inspect that clone's generated Directory.Build.props and its Git ignore status. Developer Suite's workspace binding can repair recognized, ignored generated props; it does not overwrite custom or tracked files. A passing --help check proves only that the CLI starts, so verify generation with your app's dotnet build.

3. Uninstall

There is no standalone AppClient uninstall command in the current installer. Close IDEs and builds that use it. On Windows, remove the machine-wide AppClient directory from an Administrator PowerShell window. This removes current and its retained previous release copies; it does not remove Developer Suite or your app source.

$appClientRoot = Join-Path $env:ProgramFiles 'Createrun\AppClient'
if (Test-Path -LiteralPath $appClientRoot) {
    Remove-Item -LiteralPath $appClientRoot -Recurse -Force
}
Test-Path -LiteralPath $appClientRoot

Local app builds that require the CLI or task will fail until AppClient is installed again. A later Suite install or approved AppClient update can restore it. If you are removing both tools, use the Suite uninstall guide for its service and metadata as a separate step.

Platform status

macOS arm64 and Linux x64 have separate macOS and Linux bootstrap scripts. They obtain the Suite installer first, then request only AppClient from its signed platform channel. A matching Mac Store release and real Mac installation/removal have not been verified. There is no published Linux AppClient package or verified Linux install. On macOS the current source uses a per-user Createrun.AppClient.Cli dotnet global tool and task payload under ~/Library/Application Support/Createrun/AppClient; removal uses dotnet tool uninstall -g Createrun.AppClient.Cli and then removal of that payload after closing builds.

When Suite and AppClient releases exist for that platform, these commands use the matching Store scripts:

macOS arm64

bash -c 'set -o pipefail; curl -fsSL https://store.createrun.ai/installer/developer-tools/appclient/install-macos.sh | bash'

Linux x64 (release not yet published)

bash -c 'set -o pipefail; curl -fsSL https://store.createrun.ai/installer/developer-tools/appclient/install-linux.sh | bash'