Manage your app
Settings
Manage, then Settings: the app's name, its history, fixing runtime errors automatically, your public profile, the rules the assistant always follows, the source code, and deleting the app.
Settings holds the preferences of this app, and how the assistant builds it: open Manage, then Settings.
| Card | What it does |
|---|---|
| Rename | The top card shows the app's name and description. Rename takes you to Overview, where the name is changed, as it appears in My Projects. |
| Earlier versions | Open History: every change is kept, named by what it did, and you can go back to any of them. |
| Fix runtime errors automatically | See below. |
| Show on my public profile | Published apps are listed on your profile page. Turn this off to keep this one off it. |
| AI rules & frozen files | Edit: rules the assistant follows on every change of this app, and files it must never touch. See Rules the app always follows. |
| Source code | Open code: read the files, or export them to GitHub or GitLab, on a paid plan. |
| Delete this app | It goes to the trash in My Projects, where you can put it back for 30 days. After that it and its uploaded files are gone. |
Fix runtime errors automatically
When someone using your published app runs into an error, Setherion can fix it without waiting for you: it reads the error, writes the fix, and publishes the app again.
- It is off until you turn it on, and it is on a paid plan.
- A fix costs you no credits.
- At most 3 fixes a day for each app, and 10 a day across your apps.
- Each fix goes through the same checks as a change you ask for. The version before it is kept, and if publishing the fix fails, the app goes back to it by itself.
- It starts only once at least two different visitors have hit the same error. Anyone can open a published site, so one person repeating an error they made up is not enough to change your app.
- Every fix, and how it ended, is listed under Automatic fixes in Logs.
The switch is for errors that real visitors hit. To fix something yourself, tell Setherion in the chat what you see.
The errors window
Every published app's card in My Projects has a label in its top corner: a green Live when visitors have hit no errors in the last day, a red one with the number when they have. Click either to open the app's errors window. It shows the last 7 days, grouped by message, with how many times each happened, to how many visitors, and on which page.
| Part | What it does |
|---|---|
| Auto-heal | The same switch as in Settings. |
| Auto-fix now | Runs one fix straight away, under the same rules as the automatic ones: a paid plan, no credits, the same daily limits. It takes a minute or three, and when it ends the window says what came of it, whether that is fixed and published again, nothing new to fix, or why it stopped. |
| Fix in the editor | Opens the app with the errors written into the chat box, so you can read the request before you send it. It costs credits like any change you ask for. |
| Auto-heal history | Each fix, and how it ended. Undo takes the app back to the version from before that fix and publishes it again. |
Fixes look only at errors that happened since you last published. An error from before then came from a version that is no longer online, and the publish may already have fixed it, so the window lists it apart under Before your last publish, faded, and Auto-fix leaves it alone. If it happens again on the version that is online now, it moves up with the others.
Undo replaces the app as it is now, which may be days of changes after the fix. Those changes are not lost: before anything is undone, the app as it stood is saved as a version in History, where you can open it or bring it back. If that copy cannot be saved, nothing is undone and the window says so.
The errors come from your visitors' browsers, and anyone who can open your site can make one up. Setherion treats their text as a report to look into, never as an instruction, and Fix in the editor shows you the request before anything is sent.
Was this page helpful?