Troubleshooting and Upgrading

Interpret failures, upgrade safely, and migrate from the retired package.

Outcome

Classify a stable failure, preserve safe evidence, and upgrade to the current supported client.

Prerequisites

The failing command’s exit code and request ID.
The installed andy-partner version and Node version.
No access token, API key, private Knowledge, or customer conversation in collected evidence.

Interpret the outcome

Exit	Meaning
0	Success
1	Internal or transport failure
2	Invalid input, unsupported command, or unsupported Node runtime
3	Authentication, reauthentication, or User setup required
4	Stable business, authorization, Entitlement, resource, or conflict problem

Upgrade or migrate

bun add --global andy-partner@0.1.2
andy version --json
andy auth status --json

The current client requires Node 20 or newer. If migrating from @jorgemenadev/andy, remove that deprecated package first and create fresh supported credentials; no retired user-scoped key or raw backend configuration is imported.

Machine-readable verification

Require andy version --json to report client 0.1.2, public contract 1, supported Node >=20, and compatible: true. Run andy auth status --json and preserve the request ID if recovery is still required.

Next step

Return to Quickstart, or use Support with the safe evidence above.