Gatexay not initialized when extensions are started

[jeffmaury]

Bug description

Causing issues for extensions registering providers

Operating system

All

Installation Method

None

Version

0.2.3

Steps to reproduce

No response

Relevant log output

Additional context

No response

[fullsend-ai-triage]

🤖 Finished Triage · ✅ Success · Started 5:59 AM UTC · Completed 6:03 AM UTC
Commit: 351c92b · View workflow run →

[fullsend-ai-triage]

Triage Summary

Severity: High | Category: Bug

Problem

OpenshellGateway.init() is called after extensionLoader.start() completes in the plugin system initialization sequence (packages/main/src/plugin/index.ts, lines 3774-3775). Extensions that register providers requiring the gateway during their activation find it uninitialized.

Root Cause

The initialization order in PluginSystem is:

1. extensionLoader.start() (line 3768) -- starts all extensions
2. openshellGateway.init() (line 3774) -- initializes gateway after extensions

The gateway init is also fire-and-forget (catch-only), so even extensions starting slightly later would race against it.

Recommended Fix

Move OpenshellGateway.init() to before extensionLoader.start() and await the promise so the gateway is fully ready when extensions activate. The relevant code block is around lines 3766-3775 in packages/main/src/plugin/index.ts.

Proposed Test Case

Test: PluginSystem initialization order
- Mock OpenshellGateway and ExtensionLoader
- Call PluginSystem initialization
- Assert OpenshellGateway.init() resolves before ExtensionLoader.start() is called
- Assert that if gateway init rejects, extensions still start (graceful degradation)
- Assert gateway init errors are logged

---

Labels: This is a bug in the openshell gateway initialization within the agentic-workspace area, ready for implementation.