Auto-fix is now available on self-hosted installs (v6.18.0)

[SebConejo]

Since v6.18.0, Auto-fix works on self-hosted!

What Auto-fix does

When a provider rejects a request with a repairable error (a 400, 404, or 422 such as a malformed body, a renamed model, or an invalid parameter), Manifest sends the failed request to its healing service, receives a patched version, and resends it once to the provider. This happens before your fallback chain, so the fallback chain remains the safety net if healing does not clear the error. One repair attempt per request, nothing more.

What changed in v6.18.0

Self-hosted installs can now use the same hosted healing service as Manifest Cloud, with no configuration. There is no API key to request and nothing to deploy. Your install identifies itself with an anonymous install id.

How to enable it

1. Upgrade to manifestdotbuild/manifest:6.18.0 or later.
2. Open an agent's Settings page and turn on Auto-fix, or use the card in the sidebar that lists agents without it.

It is off by default. Nothing is sent anywhere until you enable it.

What enabling it means for your data

We want to be direct about this, because self-hosting is often a privacy choice. To repair a request, your install sends the failing request, including its message content, together with the provider's error response, to our hosted Auto-fix service. Provider API keys and OAuth tokens are never sent. Requests that succeed are never sent. The full details are in the privacy policy and the terms.

How to turn it off

Per agent from the dashboard at any time, or globally with AUTOFIX_GLOBAL_ENABLED=false, which stops all calls to the Auto-fix service including the boot health check.

Release notes: https://github.com/mnfst/manifest/releases/tag/manifest%406.18.0

Happy to answer questions here.