fix: notify renderer when api server ready

[defi-failure]

What this PR does

Fixes the race condition where the agent list doesn't render if the API server starts slower than the page load, forcing users to manually switch tab to see the list.

Before this PR:

before.mov

After this PR:

after.mov

Fixes #

Why we need it and why it was done in this way

The following tradeoffs were made:

The following alternatives were considered:

Links to places where the discussion took place:

Breaking changes

If this PR introduces breaking changes, please describe the changes and the impact on users.

Special notes for your reviewer

Checklist

This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

• PR: The PR description is expressive enough and will help future contributors
• Code: Write code that humans can understand and Keep it simple
• Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
• Upgrade: Impact of this change on upgrade flows was considered and addressed if required
• Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature.

Release note

[Copilot]

Pull Request Overview

This PR fixes race condition issues with API server status synchronization by implementing an event-driven approach. Instead of relying on optimistic state updates, the renderer now waits for explicit "ready" events from the main process when the API server actually starts.

• Changed initial state in useApiServer from optimistic to conservative (false instead of config-based)
• Added IPC event mechanism to notify renderer when API server is ready
• Modified SWR key in useAgents to be null when server is not running, preventing premature fetch attempts

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
src/renderer/src/hooks/useApiServer.ts	Changed initial state to false and added effect to listen for API server ready events
src/renderer/src/hooks/agents/useAgents.ts	Made SWR key conditional on server running status to prevent fetching when server is down
src/preload/index.ts	Added onReady method to expose IPC event listener for API server ready notifications
src/main/apiServer/server.ts	Added notification to renderer when API server successfully starts listening
packages/shared/IpcChannel.ts	Added new IPC channel enum value for API server ready event

Comments suppressed due to low confidence (2)

src/main/apiServer/server.ts:89

• The restart() method calls start() which will send the ApiServer_Ready event, but this may cause issues if the renderer isn't properly synchronized. The restart flow already calls checkApiServerStatus() in the renderer's restartApiServer callback, which means the ready event listener will also trigger checkApiServerStatus(), resulting in two concurrent status checks. While not breaking, this creates unnecessary redundant API calls. Consider if the restart event needs special handling or if the ready event should be suppressed during restarts.

  async restart(): Promise<void> {
    await this.stop()
    await config.reload()
    await this.start()
  }

src/renderer/src/hooks/agents/useAgents.ts:39

• The error handling logic in the fetcher is now redundant since swrKey is set to null when apiServerRunning is false. SWR will not call the fetcher when the key is null, so lines 34-39 can never execute with apiServerRunning being false. Consider removing the apiServerRunning checks from the fetcher to simplify the code, keeping only the apiServerConfig.enabled check if it serves a different purpose.

  // Create a more dynamic SWR key that includes server running status
  const swrKey = apiServerRunning ? key : null

  const fetcher = useCallback(async () => {
    // API server will start on startup if enabled OR there are agents
    if (!apiServerConfig.enabled && !apiServerRunning) {
      throw new Error(t('apiServer.messages.notEnabled'))
    }
    if (!apiServerRunning) {
      throw new Error(t('agent.server.error.not_running'))
    }

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[EurFelux]

Note

This issue/comment/review was translated by Claude.

The UI needs some fine-tuning. Currently, it shows an Alert first because it detected 'not running', but it didn't check the loading state, which is actually the actual state.

---

Original Content

UI要微调一下，现在先显示Alert，因为检查到 not running了，没有检查loading，但是实际上是loading的状态