feat: introduce plugin system for runtime extensibility#8
Open
feat: introduce plugin system for runtime extensibility#8
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
a55ab40 to
6ba0526
Compare
- Add src/plugin/types.ts: IPixelAgentsPlugin, IAgentProvider, IAgentHandle, IMessageBridge, IRuntimeUI, PostMessage, and related interfaces - Add src/plugin/registry.ts: registerPlugin/getPlugin singleton - Add src/vscode/VSCodePlugin.ts: WebviewViewProvider + IPixelAgentsPlugin impl - Add src/vscode/VSCodeAgentProvider.ts: terminal lifecycle via IAgentProvider - Add src/vscode/VSCodeMessageBridge.ts: webview ↔ extension bridge - Add src/vscode/VSCodeRuntimeUI.ts: VS Code dialog/state APIs via IRuntimeUI - Add src/core/agentLifecycle.ts: runtime-agnostic agent + message coordination - Replace vscode.Webview param with PostMessage in fileWatcher, transcriptParser, timerManager, assetLoader - Replace ExtensionContext param with IRuntimeUI in layoutPersistence - Replace AgentState.terminalRef with AgentState.handle (IAgentHandle) - Remove PersistedAgent from types.ts (replaced by PersistedAgentHandle) - Delete PixelAgentsViewProvider.ts and agentManager.ts (replaced by new modules) - Slim extension.ts to only wire up the plugin and lifecycle Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
The /api/dev-assets endpoint was Vite dev-server only (configureServer hook), causing 404 in the production static build on Vercel. Added a generateBundle hook to emit dev-assets.json alongside the JS/CSS artifacts so browser mock asset loading works in production. Also renamed the dev middleware path to /dev-assets.json for consistency. Removed broken /vite.svg favicon reference. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
fc1daaf to
6242e5d
Compare
Owner
Author
|
❗ Collision ❗ What is possible is to write something that collaborates with it. E.g. over an API: WebSocket, RPC, ... . |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
src/plugin/types.ts) that abstractsIAgentProvider,IMessageBridge, andIRuntimeUIsrc/vscode/) —VSCodePlugin,VSCodeAgentProvider,VSCodeMessageBridge,VSCodeRuntimeUIsrc/core/agentLifecycle.ts) that replaces the oldPixelAgentsViewProvider+agentManager— novscode.*importsvscode.Webviewcoupling fromfileWatcher.ts,transcriptParser.ts,timerManager.ts,assetLoader.ts— all now use aPostMessagecallback typelayoutPersistence.tsto acceptIRuntimeUIinstead ofExtensionContextsrc/PixelAgentsViewProvider.tsandsrc/agentManager.ts(fully replaced)Architecture
Community plugins can implement these interfaces to support different environments (browser, other IDEs) or different agent types.
Test plan
npm run build) — verified ✅+ Agent🤖 Generated with Claude Code