A delayed chat can make a sent message or new output appear late even though Oysterun is already retrying. Use the visible sync banner to identify the state, keep the original work unchanged, and complete one bounded recovery before deciding that the Session needs help.

1. Recognize the visible sync state

The task-owned Session shows the exact Reconnecting... banner while its original message, result, and composer remain visible.
Visible checkpoint: Reconnecting... appears in the same Session without hiding the original message, result, or composer.

Starting screen: the intended Session chat with its name and timeline visible. The composer may be empty or may contain an unsent draft.

  1. Confirm the Session name in the header.
  2. Note the last visible message or result. If you already sent a message, note a short, nonprivate phrase from it.
  3. Look for a banner above the chat.
Visible stateMeaning for this recovery
No sync bannerThe chat is prepared or syncing normally. Initial loading or an Agent still working is not, by itself, a delayed-sync warning.
Reconnecting...Chat recovery is underway. Keep the page open and wait.
Connection Lost. Still retrying.The recovery has remained continuous long enough to require the bounded reachability check below.

2. Let the ordinary reconnect finish

  1. If Reconnecting... is visible, keep the same chat open.
  2. Wait without reloading, clearing data, or sending another message.
  3. Watch for the banner to disappear.

If the banner changes to Connection Lost. Still retrying., continue with the reachability check.

3. Confirm Oysterun is reachable

Use another desktop tab, or return to the app's main view without discarding the affected chat.

  1. Open the normal Oysterun dashboard or main view.
  2. Look for the Sessions list or the normal sign-in screen.
  3. If Sessions appears, note the affected Session name and return to its chat.
  4. If the sign-in screen appears, sign in through that normal screen, open Sessions, and reopen the same Session.

If neither the Sessions list nor sign-in screen loads, stop this chat-sync path. The visible problem is broader reachability, so keep the evidence and ask for help without restarting anything.

4. Give the same chat one bounded recovery window

The same task-owned Session shows the exact Connection Lost. Still retrying. banner with its original message, result, and composer unchanged.
Visible checkpoint: Connection Lost. Still retrying. remains above the same Session and its unchanged message context.
  1. After confirming reachability, keep the affected Session chat open.
  2. Let Oysterun continue retrying automatically.
  3. Wait no more than five minutes for Connection Lost. Still retrying. to disappear.

During this window, do not use Clear Cache and Reload, clear browser storage, restart the Host, or create a replacement Session. Those actions can remove useful context and do not prove whether the original message was already accepted.

5. Confirm recovery before doing more work

The same task-owned Session has recovered: the sync banner is gone, the original message appears once, and its newest result remains visible.
Visible checkpoint: the banner is gone from the same Session; its one original message and newest result remain visible.
  1. Confirm the sync banner is gone.
  2. If Jump to Latest is visible, select it once and wait.
  3. Find the short phrase you noted from the original message, if you had already sent one.
  4. Check the newest output and any visible working or stop state.

A missing response with no sync banner can mean the current work is still running. Wait for its visible activity or terminal result instead of repeating the request.

6. Stop safely after the bound

If the same reachable Session still shows Connection Lost. Still retrying. after five minutes, stop waiting and record only nonsecret evidence: