Notifications

Stay informed about your tasks without watching the screen. Wallfacer sends notifications through multiple channels when important events happen.

Notification Channels

• Push -- Native push notifications on iOS and Android via Expo.
• Email -- Delivered to your account email address.
• Slack -- Direct messages via the Slack integration. Requires connecting Slack in Settings > Integrations.

Notifications go one direction. To message an agent in Slack and get an answer back, see Agents in Slack.

Events You Can Subscribe To

Notification preferences are organized around account activity that may need your attention, such as task or session failures, snapshot generation results, attachment resolution problems, and account membership changes.

The exact event list can change as new product areas ship. Use the toggles in Settings > Notifications as the current source of truth for which events are available to your account.

Configuring Preferences

Go to Settings > Notifications. Each event has toggles for push, email, and Slack. Enable or disable channels independently per event.

By default, most events send push notifications. Email and Slack are off until you enable them.

Notification Actions

Some push notifications carry quick actions, so you can respond to a task straight from the notification without opening the app. When a notification announces something that needs a single response, the matching action appears on it:

• Retry -- shown when a task or session has failed. Retries it.
• Resume -- shown when a task's implementation is paused. Resumes the task.

Each action appears only on the notification it belongs to, so Retry never shows up on a paused task and vice versa. Tapping the body of the notification, rather than an action, still opens the app to the task as before.

A playbook that is waiting sends no such notification. It is watching a system you already work in, so the thing to respond to is there: submit the review, add the label, and the task continues on its own.

Replying from a Notification

When a session you started in the app goes idle while waiting on you, its push notification carries a Reply action on iOS and Android. Long-press the notification (or pull it down), type your reply in the text field, and send it. The message reaches the session without opening the app.

Wallfacer wakes the app in the background to deliver the reply, so it works straight from the lock screen or notification shade. Sending the reply reactivates the idle session the same way a message sent inside the app does: Wallfacer boots a fresh VM from the environment snapshot and delivers your message once the session is active. See Coding Sessions for how idle sessions resume.

If the reply can't be sent, a "Couldn't send your reply" notification appears. Tap it to open the session and try again.

Answering an Agent's Question

The same Reply field carries an agent's question. When an agent hits a decision only a person can make and has no room and nobody to take it to, the question parks on the task and notifies whoever is accountable for it: the task's owner first, then whoever requested the work, then the account's members. Your account's own agents are never the addressee.

Type the answer into the notification's reply field and the parked session picks it up and carries on. The task's own Waiting on an answer callout shows the same question if you would rather open the app. See Questions and Outreach for where questions go and what happens when nobody answers.

Conversations Another Channel Owns

A conversation that started somewhere other than the app is answered where it started, so Wallfacer does not notify you about it in the app as well. A session that began in Slack or by email sends no push, email, or Slack alert of its own when it goes idle, pauses for you, or receives a new message. The agent's reply is already in the thread you are reading, and the app will not send into a conversation another channel owns, so the Reply action on such a notification could not have worked anyway.

Task-level notifications are unaffected. A task that completes or fails still notifies you in the app whichever channel its conversation started in.

See Agents in Slack and Agents over Email for how those conversations read in the app.

Real-Time Updates

The app uses WebSockets for live updates without polling. Task activity, session status changes, and VM state changes appear instantly in the UI. You don't need to refresh -- the app stays in sync automatically.

Going Offline

The app tracks your device's network connection and adapts when it drops. Losing signal, switching on airplane mode, or dropping off Wi-Fi no longer fires requests against a dead connection.

• Paused activity. New and in-flight fetches pause instead of retrying, and background refreshing stops.
• Automatic catch-up. When the connection returns, paused work resumes and the app refreshes on its own. You don't need to reload or restart. A message send that was still waiting when the connection returns is only completed if it has been waiting less than ten minutes; past that the app hands the text back to you rather than send it twice. See Coding Sessions.

The app shows no standing offline notice. It speaks only once a request has actually failed, with the connection error described in Coding Sessions.

This runs automatically on the iOS and Android apps with no setup. In a web browser the app already follows the browser's own online and offline signal.

Notification Actions (iOS)

On iPhone, push notifications include a View action. Press and hold (or swipe) a Wallfacer notification and tap View to jump straight to whatever the notification is about -- the account, environment, session, or task -- in one tap, instead of opening the app and navigating there yourself.