nimodocs

Connect

Short answer

Explains Cloudflare OAuth, read-only setting review, the three-audit learning phase, supported edge optimization suggestions, explicit approval, apply, rollback approval, and verification.

Markdown sourceFull docs bundle

Cloudflare optimization

When your site runs behind Cloudflare, nimo can review read-only settings, suggest edge fixes, save your approval, apply approved safe actions when they are enabled for your account, and require separate approval before rollback.

Connect Cloudflare

Open Settings

Go to Integrations and choose Cloudflare.

Authorize access

Sign in with Cloudflare and allow account read, analytics read, zone read, and zone settings read scopes.

Wait for nimo to learn

nimo needs enough audit history before it suggests infrastructure changes.

Learning phase

nimo waits for a three-audit baseline before suggesting Cloudflare changes. That gives it enough history to avoid changing settings because of one noisy run.

Hint

The learning phase is deliberate. nimo should understand the page, stack, and metric trend before changing infrastructure.

Supported fixes

Image Polish and WebP

Improve image delivery at the edge when images are a real bottleneck.

Brotli compression

Compress text assets so pages transfer less data.

Early Hints

Let browsers begin loading important resources sooner.

Auto Minify

Minify HTML, CSS, or JavaScript when it is safe for the site.

Browser Cache TTL

Improve repeat visits by caching static assets longer.

Approve, apply, and roll back

Approval saves who approved the change and the test-run details. It prepares an expiring approval request; it does not change Cloudflare settings from public chat. When safe actions are enabled for your account, a signed-in apply action can apply an approved request through backend code.

  1. nimo suggests a fix and explains why.
  2. You approve or reject the suggestion; approval saves the test-run details.
  3. If approved and safe actions are enabled, you trigger the signed-in apply action.
  4. nimo records success only when Cloudflare confirms the desired value.
  5. Rollback is separate: nimo requires an available rollback reference and a second explicit approved rollback request before changing settings back.
  6. Rollback success is recorded only when Cloudflare confirms the restored value.
  7. Run a new audit or wait for verification to check the result.
  8. nimo logs the before-after result when verification data exists.

Approval prompt

Show me the Cloudflare fixes you recommend, the expected impact, and the rollback plan.

Safety constraints

Cloudflare write actions are unavailable unless safe actions are enabled for your account. Public docs, public chat, and unauthenticated agents cannot apply or roll back Cloudflare settings. Every apply or rollback should include scope, approval, a rollback or forward plan, Cloudflare confirmation, and verification.

Connect Cloudflare

Let nimo review Cloudflare settings, suggest edge fixes, and save approval history.

Get started