Maintenance and Diagnostics

Night maintenance

Under Assistela → Settings → Advanced → Maintenance, choose the hour and minute for daily local-data maintenance. Assistela automatically:

removes old operational data according to retention rules,
checks or rebuilds the index used for fast chat search,
summarizes older AI usage data,
removes old temporary files.

The same screen shows the latest maintenance state and file-work summary. Choose a time when the Mac normally runs but you are not actively using it.

Maintenance is not deletion of your memory

The normal automatic run targets operational and temporary data and search performance. It is not a substitute for manually deleting a particular conversation, memory item, or backup.

App History

Advanced → App History contains recent operational events and warnings. Start here when a service used to work and now fails, an automatic task does not run, or an error repeats.

Find the time when the problem occurred.
Review events immediately before the failure.
Note the service name, state, and short error message.
Do not chase isolated informational entries when the feature works normally.

Model Diagnostics

Advanced → Model Diagnostics contains stored model payloads, prompt snapshots, and tool-call transcripts. It is intended for technical troubleshooting: it can show what was sent to the model, how the model responded, and which step failed.

Diagnostic data is sensitive

It may contain parts of your requests, service names, file paths, and working context. Before sharing an export, inspect it and remove personal or secret information. API keys should be redacted, but do not rely on that without your own review.

Life Event Candidates

Advanced → Life Event Candidates is a read-only view of observations waiting to be consolidated into the life chronicle. It can show a title, summary, date, and status such as confirmed, ongoing, completed, or correction. Items leave the active list after successful consolidation.

This is not a task or reminder list. For a concrete action at a particular time, use Calendar or Reminders.

Where to begin with a problem

Verify the AI account and a simple answer in Chat.
Check that the particular service is enabled and has its macOS permission.
Use Advanced → App History to find events at the exact failure time.
Use Model Diagnostics only when the basic checks are not enough.

For a plain-language process and safe diagnostic submission, continue with Help and reporting a bug.

If the problem continues

Create a fresh backup, note the exact failure time, model, service, and reproduction steps. Do not change several advanced options in the meantime. This preserves a state from which the problem can be identified reliably.