Sali Now Does the Fix for You: Allow Once and Undo

Your build fails and Sali can only tell you why

Your app build stops with an error like ext-intl is missing, and the fix is one setting away. Until now Sali explained what was wrong and offered a button, and you did the work yourself. Now Sali can do the fix for you, as you, once you say yes. At the end of this you will be able to let Sali change a setting, deploy again, and undo it for 24 hours if you change your mind.

This is written for anyone running an app on Tanzahost who hits a build, DNS, domain, database, or limits problem and wants it fixed without doing every step by hand.

What's new

• A card before anything happens. Sali shows exactly what it will do. Nothing changes until you answer the card.

• Fixes in a few steps. Sali can add a missing PHP extension and deploy again, add or change DNS records, set variables, add a domain, connect a database, change limits, or add a worker.

• Variables stay private. When a fix needs variables, you type the values. Sali never sees them.

• Money and risky steps are asked every time. The button shows the price from our price list, or you type the app's name to confirm.

• Undo for 24 hours. The Undo control sits on the card and in your activity.

• Your permissions, never more. Sali can do only what you could do yourself. It never deletes anything and never touches payments.

Read the full entry at /changelog/2026-10-28-sali-does-the-work.

What you need before you start

• An app on Tanzahost that you can already build and deploy. In this walkthrough it is a Laravel app called duka-web.

• The name of the thing you want changed. For a build like Asha's, that is the missing PHP extension: intl.

• The rights to make that change yourself. Sali can only do what you could do yourself.

• For anything that costs money or carries risk, a moment to confirm. The price comes from our price list and sits on the button. Sali never touches payments.

Steps: let Sali fix the build and deploy again

Asha runs a small shop on a Laravel app. Her build fails and she wants the new version live today.

Ask Sali why the build failed

Asha's Laravel build fails with ext-intl is missing. She asks Sali why. Sali explains the problem and prepares a fix. Nothing has changed yet.

Read the card before anything happens

Sali shows a card with exactly what it will do. Asha's card says: Add the PHP extension intl to duka-web and deploy again. Read the card fully. It is the only place that says what will change.

Choose Allow once, Always allow, or Not now

The card gives you three answers:

• Allow once — Sali does this one thing, this one time.

• Always allow — in the project, for small, safe things. Good when you trust the small fixes in this project.

• Not now — nothing happens, and Sali stops.

Asha taps Allow once.

Confirm the steps that cost money or carry risk

Money and risky steps are asked every time, even after Always allow. The button shows the price from our price list, or you type the app's name to confirm. Asha's extension fix is a settings change and a deploy, so it goes through on the card alone. If a step of yours involves money, expect a second question, and answer it yourself. Sali never touches payments.

Type the values for any variables the fix needs

If the fix needs variables, you type the values. Sali never sees them. It only records what you set.

Let Sali deploy, then read your activity

Sali adds the extension and deploys again. The new version goes live. Asha's activity says: Asha (with Sali) added intl to duka-web. The wording matters: the change is under her name, with Sali noted as the helper.

Undo it if you change your mind

Undo is on the card and in your activity. It puts the settings back and restores the version before. Asha taps Undo when she wants the previous version again, and her settings and version return. The window is 24 hours.

What to check that it worked

• The build that failed with ext-intl is missing now passes and the new version is live.

• Your activity shows the change under your name, like Asha (with Sali) added intl to duka-web.

• The settings on the app match the card you approved. If they do not, use Undo.

• The Undo control is still there. It stays for 24 hours, on the card and in your activity.

Mistakes people make and how to fix each

Approving without reading the card. The card is the only place that says what will happen before anything happens. Read it, then answer.

Tapping Not now and expecting the fix later. Not now stops Sali, and nothing has changed. Ask again when you are ready.

Expecting Sali to delete something. Sali never deletes anything. Deleting is yours to do.

Expecting Sali to handle money. Sali never touches payments. Money and risky steps are asked every time, with the price from our price list on the button, or the app's name typed to confirm.

Expecting Sali to see your variable values. You type the values. Sali never sees them. That is on purpose.

Expecting Sali to go past your own permissions. Sali can do only what you could do yourself. If it cannot do a step, neither can your account.

Waiting longer than 24 hours to undo. The undo window is 24 hours. After that, change the setting yourself and deploy the version you want.

Using Always allow for things you want to review. Always allow covers small, safe things in the project. Use Allow once when you want to see every card.

Next

• The full announcement, with the list of fixes Sali can do: /changelog/2026-10-28-sali-does-the-work