0.74.0

triggerdotdev/trigger.dev0.74.0Jun 25, 2026by takahirom

AI Summary

Arbigent improves iOS testing reliability by warming up the simulator on connection and enhances security by masking sensitive values in CLI help output.

Key Highlights

  • Warms up iOS simulator on connect to prevent cold-start crashes
  • Masks sensitive option values (e.g., API keys) in CLI help output
  • Switched CLI E2E model to gemma-4-31b-it

New Features

  • Simulator warm-up mechanism
  • Secret masking in CLI help text

Full Release Notes

## More reliable iOS runs
Arbigent now warms up the iOS simulator when connecting to it. A freshly booted simulator can crash the XCTest runner on the first interaction ("App crashed or stopped while executing flow"), which was a common source of flaky iOS runs.
Arbigent waits for the device to become responsive and settle before the first scenario, so cold-start crashes are avoided — no extra setup needed on your side.

## Masked secrets in CLI help
Sensitive option values (such as API keys) are now masked in the CLI `--help` output, so they won't leak when you share your help text or logs.

## What's Changed
* Mask sensitive option values in CLI help output by @takahirom in https://github.com/takahirom/arbigent/pull/380
* Switch CLI E2E model to gemma-4-31b-it by @takahirom in https://github.com/takahirom/arbigent/pull/381
* Recover iOS device crashes by reconnecting and retrying by @takahirom in https://github.com/takahirom/arbigent/pull/382
* Revert iOS reconnect-retry; warm up the simulator instead by @takahirom in https://github.com/takahirom/arbigent/pull/383
* Warm up iOS simulator on connect to avoid cold-start runner crashes by @takahirom in https://github.com/takahirom/arbigent/pull/384


**Full Changelog**: https://github.com/takahirom/arbigent/compare/0.73.0...0.74.0