electrobun

Name: electrobun
Availability: InStock
Author: Goddard

Unifies Bun-based main process code with browser views and typed RPC contracts for desktop apps.

Updated Mar 2, 2026

Search Tags:#bun #desktop #rpc #ipc #webview #electrobun

Ready to run

npx skills add https://github.com/goddard-ai/goddard --skill electrobun-goddard-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: electrobun
Source: https://github.com/goddard-ai/goddard/tree/main/app/.agents/skills/electrobun
Command: npx skills add https://github.com/goddard-ai/goddard --skill electrobun-goddard-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Electrobun streamlines building desktop apps by combining Bun main-process code with browser windows, webviews, and typed RPC contracts, reducing friction between Bun, BrowserWindow, and UI layers.

Core Features & Use Cases

Provides a structured pattern for cross-boundary communication between Bun, the renderer, and native UI integrations like menus, trays, and dialogs.
Includes example playbooks and references to guide building, reviewing, and extending Electrobun-based apps.
Use cases span building Electrobun desktop apps that avoid Electron APIs while embracing webviews, RPC schemas, and native integrations.

Quick Start

Create a new Electrobun app using the provided templates, then start the Bun main process and load a BrowserWindow with typed RPC.

Frequently Asked Questions about electrobun

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I build desktop apps with Bun and webviews using typed RPC?▼

Build desktop apps with Bun by unifying main-process code with browser views and typed RPC contracts. Electrobun provides structured patterns for cross-boundary communication, avoiding Electron-specific APIs while enabling reliable IPC and rich UI integration.

What is the best way to handle IPC between a Bun main process and a browser view?▼

Handle IPC between Bun and browser views using typed RPC contracts. This approach ensures reliable cross-boundary communication, replacing Electron-specific APIs with structured schemas that connect the Bun main process directly to renderer layers.

Can I use native UI integrations like menus and trays in a Bun-based desktop app?▼

Yes, you can use native UI integrations like menus and trays in a Bun-based desktop app. Electrobun supports native integrations alongside BrowserWindow and BrowserView components, managed through typed RPC schemas and the Bun main process.

Does Electrobun work without using Electron-specific APIs?▼

Electrobun works entirely without Electron-specific APIs. It combines Bun-based main-process code with browser windows and webviews, using typed RPC contracts to handle cross-process communication and native integrations instead of relying on Electron's API surface.

How do I debug cross-process communication in a Bun desktop app?▼

Debug cross-process communication in a Bun desktop app by leveraging Electrobun's typed RPC contracts. The structured RPC schemas provide predictable, traceable interactions between the Bun main process and browser views, facilitating reliable cross-process debugging.

What are the limitations of using webviews with Bun for desktop applications?▼

Limitations of using webviews with Bun include avoiding Electron-specific APIs and requiring defined frontmatter entries in SKILL.md. Apps must rely on stable RPC schemas for cross-boundary communication, which demands strict contract management between the Bun process and UI layers.