Skip to main content

Launch troubleshooting

Compatibility failures return reason_ids. They identify a check that did not pass; they are not instructions to disable the check. Fix the cause and repeat the dry-run or probe.

ReasonMeaningCheckSafe action
gateway_not_installedThe gpt2giga package or executable is missinggiga doctor and the GigaLoom installation methodReinstall the published gigaloom[gpt2giga] package
gateway_incompatibleThe gateway version or API is outside the supported windowThe gpt2giga version and configuration inspectionInstall a compatible version; do not override the check
gateway_models_unavailableThe gateway did not return a valid model list/models, the gateway address, and authenticationRepair the gateway or credentials and explicitly refresh the route
agent_has_no_configurable_provider_contractThe ACP agent cannot safely change its model providerprovider_bridge.status in inspectLaunch with the native provider, without --with or --model
acp_provider_adapter_version_mismatchThe built-in adapter is not verified for this agent versionThe installed version and probe resultUpgrade or roll back to a supported version, then probe again
acp_provider_set_rejectedThe agent rejected or did not confirm the selected model providerThe supported protocol and probe readbackFix the agent configuration or use native launch; do not enable an unverified fallback
acp_model_selector_unavailableThe agent accepted the provider but cannot select the requested modelModel-selection capability in inspectUse a supported agent version or native launch
gateway_upstream_credentials_unavailableGigaChat credentials are absent from the current processAuthentication variables in the same terminalExport credentials and repeat the dry-run without printing secrets
gateway_sidecar_port_busyAnother process owns the managed gateway portThe port owner and active gateway profilesStop the known process or select an explicitly configured external gateway
gateway_route_catalog_staleStored model or capability information is staleGateway reachability and the last refresh timeRestore connectivity and refresh explicitly; stale data cannot authorize a launch

A concrete JSON response can use a more specific reason in the same class. Do not publish complete diagnostics until you have checked them for local paths and secrets.

Quick checks

Inspect GigaLoom and the agent:

giga doctor
giga agent list --json
giga agent inspect AGENT_ID --json
giga agent probe AGENT_ID --json

Inspect a route without launching the agent:

giga --with gpt2giga --model MODEL_ALIAS --dry-run --json AGENT_ID

Return to the agent's native model provider:

giga AGENT_ID

This rollback does not require restoring the agent's native configuration, because GigaLoom does not modify it. For local service, backup, or state-upgrade problems, continue with Operations.