Troubleshooting Sessions and Background Activity

Symptom: a session shows "needs resume"

Likely cause: the underlying process was ended by the system — commonly after the app or device restarted, or Android reclaimed background resources.
What to try: reopen the session; Deputy Shell will start a new process for it. Its workspace and recent output are unaffected.
Data preserved: the session's workspace folder and recent retained output remain; only the live process needed restarting.

Symptom: a background session stops unexpectedly

Likely cause: Android or your device manufacturer's battery-management system ended the background process. This is more common on devices with aggressive battery optimization.
What to try: check your device's battery-optimization and background-activity settings for Deputy Shell, and consider exempting it if your device offers that option.
Data preserved: as above — workspace and recent context remain; the session shows as needing resume.

Symptom: no ongoing notification appears for a running session

Likely cause: notification permission was declined, or notifications for Deputy Shell are disabled in Android Settings.
What to try: enable notifications for Deputy Shell in Android's app settings. The session itself keeps running either way — this only affects whether you see the ongoing notification.

When to contact support

If sessions are ending unexpectedly even with battery optimization disabled for Deputy Shell, export diagnostics and reach support@deputyshell.com with your device model and manufacturer.