Plan/1737 connection status indicator

[bashrusakh]

No description provided.

[gemini-code-assist]

Code Review

This pull request introduces a compact, aggregated ConnectionStatusIndicator component in the header to track and display connection health across two hops: Frontend to OpenChamber runtime, and OpenChamber runtime to OpenCode. It adds the corresponding state management in useConfigStore, integrates browser-level online/offline listeners in sync-context.tsx, and provides localized messages and unit tests. The review feedback highlights a bug where navigatorOfflineRef is never updated after mount, suggesting reading navigator.onLine dynamically instead. Additionally, the reviewer recommends avoiding prop-drilling the translation function t by using the useI18n hook directly inside the memoized body component, and suggests mirroring the active connectionPhase in sync-context.tsx rather than hardcoding a "disconnected" phase to prevent overriding active reconnection states.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

The navigatorOfflineRef is initialized once on mount and its value is never updated. As a result, navigatorOffline remains constant throughout the component's lifecycle.

If the application is mounted while offline, navigatorOffline will be permanently stuck at true. Even after the network is restored and the transport successfully reconnects, the view model will continue to evaluate navigatorOffline as true and display the "Disconnected" status.

Since ConnectionStatusIndicator already re-renders whenever runtimeTransport or openCodeRuntime changes (which is guaranteed to happen on network changes due to the listeners in sync-context.tsx), we can safely read navigator.onLine dynamically during render instead of using a stale ref.

  const navigatorOffline =
    typeof navigator === 'object' && navigator !== null && navigator.onLine === false;

[gemini-code-assist]

Simplify the ConnectionStatusIndicatorBodyProps type definition by removing the t translation function prop, as it will be consumed internally via the useI18n hook.

type ConnectionStatusIndicatorBodyProps = {
  viewModel: ConnectionStatusViewModel;
};

[gemini-code-assist]

Instead of passing the t translation function as a prop from the parent, you can call useI18n() directly inside ConnectionStatusIndicatorBody.

Since ConnectionStatusIndicatorBody is wrapped in React.memo, removing the t prop ensures it is memoized purely on the viewModel reference. When the locale changes, the i18n context will automatically trigger a re-render of ConnectionStatusIndicatorBody anyway, keeping the translations up-to-date without prop-drilling.

Suggested change

	const ConnectionStatusIndicatorBody = React.memo(function ConnectionStatusIndicatorBody({
	viewModel,
	t,
	}: ConnectionStatusIndicatorBodyProps) {
	const ConnectionStatusIndicatorBody = React.memo(function ConnectionStatusIndicatorBody({
	viewModel,
	}: ConnectionStatusIndicatorBodyProps) {
	const { t } = useI18n();

[gemini-code-assist]

Remove the t prop passed to ConnectionStatusIndicatorBody to match the updated signature that uses useI18n() internally.

Suggested change

	return <ConnectionStatusIndicatorBody viewModel={viewModel} t={t} />;
	return <ConnectionStatusIndicatorBody viewModel={viewModel} />;

[gemini-code-assist]

Currently, when the transport disconnects, runtimeTransportState is updated with phase: "disconnected". However, the event pipeline is actually in a "reconnecting" or "connecting" phase (as tracked by connectionPhase).

By hardcoding "disconnected", the connection status indicator will immediately show the red "Disconnected" dot instead of the neutral/muted "Reconnecting" dot during active reconnection attempts. This makes the "reconnecting" and "connecting" phases in the view model dead code.

We should mirror the active connectionPhase (which uses hasEverConnected ? "reconnecting" : "connecting") so the indicator can accurately reflect the transitional states.

        useConfigStore.getState().setRuntimeTransportState({
          phase: hasEverConnected ? "reconnecting" : "connecting",
          reason,
          updatedAt: Date.now(),
        })