Fix TaskModal lint failure by removing synchronous state update in effect

[Copilot]

The lint GitHub Actions job failed due to react-hooks/set-state-in-effect in TaskModal.jsx, where component state was being synchronously set inside an effect. This change removes that anti-pattern while preserving task-stream initialization behavior.

• Root cause addressed: TaskModal effect state sync

  • Reworked TaskModal task-state initialization so it no longer calls setDetail(task) directly in the useEffect body that opens the EventSource stream.
  • Kept existing stream lifecycle behavior (snapshot, progress, token, provider_switch, complete, error) intact.

• State flow cleanup

  • detail now derives from the current task input/state transition pattern instead of being force-set synchronously at effect start.
  • Reset logic for transient streaming state (streamingResult, provider-switch banner, token buffer) remains coupled to task changes.

useEffect(() => {
  if (!task) return;

  // removed synchronous setDetail(task) here
  setStreaming('');
  setSwitch(null);
  tokenBufferRef.current = '';

  const es = new EventSource(`${API_BASE}/api/tasks/${task._id}/stream`, { withCredentials: true });
  // ...existing stream event handling...
}, [task]);

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
cortex	Ready	Preview	Aug 4, 2026 3:44pm