[Bug]: Mobile notifications require T3 Connect even for direct server connections #29726

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

apps/mobile

Steps to reproduce

1. Open T3 Code mobile app.
2. Connect to a self-hosted T3 Code server or direct environment without T3 Connect.
3. Enable device notifications in Settings → Notifications.
4. Trigger an agent completion, approval request, or error event.
5. Observe whether the mobile device receives a push notification.

Expected behavior

Mobile notifications should work for a direct T3 Code connection without requiring a T3 Connect account. The device should be able to register and receive background notifications for agent events when the server is reachable.

Actual behavior

The app requires T3 Connect and does not enable mobile notifications for direct server connections. In practice, notifications only work with the T3 Connect setup, even when the app is connected to a local or self-hosted T3 Code server.

Impact

Minor bug or occasional failure

Version or commit

main

Environment

iOS or Android app; direct T3 Code connection; T3 Connect not configured/enabled

Logs or stack traces

Screenshots, recordings, or supporting files

No response

Workaround

No response