Automation and Go

Isolate Wago state

Set WAGO_HOME to place manager configuration, installed runtimes, and caches under one root:

WAGO_HOME="$PWD/.wago-ci" wago version current

Give concurrent CI jobs separate directories. Inspect paths rather than guessing:

wago status --json
wago version which
wago cache dir

Automation flags

Flag	Meaning
--no-input	Never prompt; fail if input is missing
--dry-run	Show a supported mutation plan
--json	Emit machine-readable output where supported
--locked	Refuse manifest or lockfile changes
--offline	Use installed and cached resources only

For a prepared repeatable build:

wago run --locked --offline app.wasm

Describe the command surface programmatically:

wago commands --json

Shell completions

wago config completions zsh
wago config completions zsh --install

Use --output for a specific completion file and --rc for a particular startup file. Preview installation with --dry-run.

Configure the Go API

cfg := wago.NewRuntimeConfig().
	WithCoreFeatures(wago.CoreFeaturesV3).
	WithMemoryLimitPages(256).
	WithFunctionWorkers(0)

if err := cfg.Validate(); err != nil {
	return err
}

rt := wago.NewRuntime(wago.WithRuntimeConfig(cfg))

Use WithBoundsChecks, WithDeferBoundsChecks, and WithOptimization for narrower compiler choices. Use WithPolicy during instantiation for guest authority and declared resource limits.

Next

• Pin runtimes in CI
• Configure project settings
• Return to Configuration