Add semantic router factory

[jeffmaury]

Is your feature request related to a problem? Please describe

In order to connect semantic router to workspaces, we need a way to create inference connections when starting a semantic router

Describe the solution you'd like

In the extension API, extends the Provider interface with:

interface SemanicRouterCreateParams {
  name: string;
  config: string;
}

interface SemanticRouterFactory extends ProviderConnectionFactory {
  readonly type: string; //semantic-router,...
  create(params: SemanicRouterCreateParams, logger?: Logger, token?: CancellationToken): Promise<void>;
}

setSemanticRouterConnectionFactory(semanticRouterConnectionFactory: SemanticRouterFactory): Disposable

Describe alternatives you've considered

No response

Additional context

No response

[fullsend-ai-triage]

🤖 Finished Triage · ✅ Success · Started 11:52 AM UTC · Completed 11:55 AM UTC
Commit: 0e5e19b · View workflow run →

[fullsend-ai-triage]

Triage Summary

Category: Feature · Severity: Medium

Problem

The extension API Provider interface lacks a factory for semantic router connections, preventing extensions from programmatically creating semantic routers for workspace integration.

Analysis

The proposed API follows the well-established ProviderConnectionFactory pattern already used by six other provider types (container, inference, RAG, chunk, Kubernetes, VM). The codebase already has semantic router infrastructure in place (semantic-router-manager, config schemas, UI components), so this is about exposing creation capabilities to extensions.

Recommended Implementation

1. Add SemanticRouterCreateParams and SemanticRouterFactory interfaces to packages/extension-api/src/extension-api.d.ts
2. Add setSemanticRouterConnectionFactory() method to the Provider interface
3. Wire through ProviderRegistry following the same pattern as other factory types
4. Add IPC handler in packages/main/src/plugin/index.ts

Proposed Test

test('should register and invoke SemanticRouterFactory', async () => {
  const factory = { type: 'semantic-router', create: vi.fn() };
  const disposable = provider.setSemanticRouterConnectionFactory(factory);
  
  // Verify factory is registered in ProviderRegistry
  expect(registry.getSemanticRouterConnectionFactory()).toBe(factory);
  
  // Verify create can be called
  await factory.create({ name: 'test-router', config: '{}' });
  expect(factory.create).toHaveBeenCalledWith({ name: 'test-router', config: '{}' });
  
  // Verify cleanup
  disposable.dispose();
  expect(registry.getSemanticRouterConnectionFactory()).toBeUndefined();
});

Related Issues

• Semantic router integration #1945 (Semantic router integration epic)

---

Labels: Feature request extending the extension API with a new semantic router factory, touching extensibility and model areas.

[benoitf]

maybe return an object rather than void with like the id of the router or model being created etc

else LGTM