Skip to main content
SelfTune has two different background jobs. The local service keeps the dashboard runtime available. Scheduling runs periodic observation and health work. Enable only the one you need.

​
Persistent local service

The service runs under your operating system’s user-level supervisor. It does not require a Cloud connection. Use service uninstall to remove the supervisor definition while preserving local SelfTune data.

​
Scheduled health work

Before enabling a schedule, review its frequency, commands, model usage, write behavior, and whether any remote destination is configured. Start with observation and reporting before allowing automatic skill changes.

​
Ask your agent

​
Success criteria

  • The owner, executable, state directory, and schedule are explicit.
  • Restarting the machine does not create duplicate runtimes.
  • Status and health checks can distinguish registered from actually healthy.
  • Disabling the background job preserves user data unless deletion is requested.