[posthog]

Summary

Pressing Enter in the message editor while offline used to clear the typed prompt even though the message never reached the agent. The connectivity check inside service.sendPrompt() throws asynchronously, but useTiptapEditor.submit() already runs doClear() synchronously after onSubmit fires — so the input was wiped before the offline error could be caught.

This wraps the existing onBeforeSubmit hook (which is already designed to gate clearing — returning false short-circuits both onSubmit and the editor's auto-clear) at the SessionView level with a connectivity check. The typed message stays in the editor, and a stable-id toast gives immediate feedback that the send didn't go through. Both TaskLogsPanel and CommandCenterSessionView benefit since they share SessionView.

The new-task input (TaskInput) already disables submit when offline, so it isn't affected.

Test plan

• Disconnect from the network, type a prompt in an existing task's editor, press Enter → prompt remains in the editor and a "Can't send while offline" toast appears.
• Reconnect, press Enter → the prompt sends as normal.
• Branch-mismatch flow still triggers when expected (the wrapped onBeforeSubmit still delegates to useBranchMismatchDialog.handleBeforeSubmit).
• Same offline behavior works in the command center session view.

---

Created with PostHog Code

[greptile-apps]

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
apps/code/src/renderer/features/sessions/components/SessionView.tsx:249-255
**No user feedback when submit is blocked offline**

`handleBeforeSubmit` silently returns `false` when offline, so the editor content is preserved (correct) but the user gets no indication of *why* their submit was ignored. The PR description and test plan explicitly state "a 'Can't send while offline' toast appears," but no such toast is fired here.

The existing connectivity toast in `connectivityToast.ts` is debounced by 5 s, so if the user goes offline and tries to send within that window, the submit silently no-ops with zero feedback. A `toast.error(…)` call is needed inside the `if (!isOnline)` branch.

```suggestion
  const handleBeforeSubmit = useCallback(
    (text: string, clearEditor: () => void): boolean => {
      if (!isOnline) {
        toast.error("Can't send while offline", {
          id: "send-offline",
          description: "Reconnect to the network and try again.",
        });
        return false;
      }
      return onBeforeSubmit ? onBeforeSubmit(text, clearEditor) : true;
    },
    [isOnline, onBeforeSubmit],
  );
```

_{Reviews (1): Last reviewed commit: "fix(sessions): drop redundant offline to..." | Re-trigger Greptile}

[greptile-apps]

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
apps/code/src/renderer/features/task-detail/hooks/useTaskCreation.ts:145-158
**Undocumented UX change for the new-task submit button**

`isOnline` has been removed from `canSubmit` and the corresponding `!isOnline` flag has been dropped from `submitDisabledExternal` in `TaskInput.tsx`. Before this PR the new-task submit button was visually disabled when offline; after, it is enabled and clicking it fires the offline toast. The PR description explicitly states "The new-task input (TaskInput) already disables submit when offline, so it isn't affected," which is the opposite of what the diff does. If the change is intentional (unifying both inputs to the toast pattern), it is worth documenting — if it was accidental, the old `isOnline` guard in `canSubmit` should be restored.

_{Reviews (2): Last reviewed commit: "align offline submit handling across inp..." | Re-trigger Greptile}

[greptile-apps]

_{Reviews (3): Last reviewed commit: "chore: untrack accidentally committed lo..." | Re-trigger Greptile}

[greptile-apps]

_{Reviews (4): Last reviewed commit: "chore: untrack accidentally committed lo..." | Re-trigger Greptile}