bug: ACP Registry installation and authentication bugs on Windows (Goose 1.46.0)

[OK85-hub]

OS

Windows 10 Professional

Poracode version

1.6.4

Agents involved

Goose 1.46.0

Reproduction steps

1. Open Poracode Settings.
2. Navigate to Agents → Agent Registry.
3. Select Goose 1.46.0.
4. Click Install or Update.
5. Observe that Poracode downloads the ZIP archive but fails while extracting it with PowerShell.
6. Manually extract Goose to Poracode’s expected ACP Registry directory and configure it as an ACP agent.
7. Confirm that goose.exe --version returns 1.46.0.
8. Confirm that goose doctor reports goose is ready.
9. Restart Poracode and open the Goose agent settings.
10. Observe that Poracode shows “Authentication required,” reports 0/0 visible models, and the Login action fails.

Expected behavior

Poracode should successfully download and extract the Goose ZIP archive on Windows, register Goose as installed, and start it as an ACP agent.

If Goose already has a working provider configuration, Poracode should recognize it as authenticated or provide a working way to acknowledge externally managed authentication.

Actual behavior

The installation fails while Poracode invokes PowerShell with a command similar to:

powershell.exe -NoLogo -NoProfile -Command Expand-Archive -LiteralPath $args[0] -DestinationPath $args[1] -Force ...

$args[0] is empty, so Expand-Archive fails because LiteralPath has no value. The ZIP is downloaded, but Goose is not extracted or registered successfully.

After manually extracting and registering Goose, Poracode can start the agent, but it incorrectly displays:

Authentication required

The Login action then fails with:

Error invoking remote method 'poracode:authenticate-acp-agent':
Error: ACP authentication was not completed.

This happens even though Goose is already configured and:

goose doctor

reports:

goose is ready

As a workaround, Goose had to be extracted manually and added to acpRegistryInstalledAgents and agentInstances. Poracode only recognized the existing authentication after the following property was added to the Goose agent instance:

"authAcknowledged": {
  "native": true
}

After restarting Poracode, Goose 1.46.0 worked correctly.

Logs or screenshots

PowerShell extraction command:

powershell.exe -NoLogo -NoProfile -Command Expand-Archive -LiteralPath $args[0] -DestinationPath $args[1] -Force

Observed extraction problem:

$args[0] is empty
Expand-Archive: Cannot bind argument to parameter 'LiteralPath' because it is null or empty.

Authentication error:

Error invoking remote method 'poracode:authenticate-acp-agent':
Error: ACP authentication was not completed.

Goose validation:

goose.exe --version
1.46.0

goose doctor
goose is ready

A screenshot showing “Authentication required,” 0/0 visible models, and the authentication error is attached.

Logs or screenshots

[SDSLeon]

Fixed in v1.6.5.

• PR: Support ACP registry install directories and agent auth updates #587 — Support ACP registry install directories and agent auth updates
• Branch: poracode/fair-lemur-8353a395

Both halves of the report are covered:

• Extraction failure — the registry installer no longer passes the archive/destination through $args[0]/$args[1], which were empty under powershell.exe -Command. The paths are now handed to Expand-Archive via $env:PORACODE_ACP_ARCHIVE_PATH / $env:PORACODE_ACP_INSTALL_DIR, plus support for custom registry install directories and update probing.
• False "Authentication required" — auth handling was reworked so an agent with a working external session (e.g. goose doctor reporting ready) is no longer asked to log in again, and an agent that reports a sign-in Poracode cannot confirm now explains how to finish setup instead of surfacing the raw ACP authentication was not completed error. The manual authAcknowledged workaround is no longer needed.

Please update to v1.6.5 and reopen if Goose 1.46.0 still misbehaves on your setup.