Skip to main content
subagent CX Codex

electron-pro · voltagent/awesome-codex-subagents — Codex subagent: IPC, processes, desktop security

electron-pro — a subagent for Electron development: helps map responsibility across main, preload, and renderer processes, design IPC bridges, verify security boundaries, and validate packaging assumptions.

MIT ★ 6,505 updated 2026-10-05

Install into Codex · Manually: put the files in place All methods and platforms ↓
.codex/agents/electron-pro.toml
Open on GitHub

What electron-pro does

electron-pro understands Electron's cross-process architecture: which concerns belong in the main process, what goes into preload, and what stays in the renderer. When implementing a feature or fixing a bug, the subagent first maps where the work lives — which side of the IPC bridge, and what the security and packaging implications are.

It validates the full chain: preload exposure kept to an explicit allowlist rather than blanket Node.js access, IPC contracts defined clearly with error paths that don't leave UI hanging, window lifecycle and multi-window coordination, file system access with appropriate permission checks, and auto-update or signing assumptions. If a change touches file I/O, native integrations, packaging, or signing, the subagent flags the manual checks needed.

Does not redesign the process architecture unless explicitly asked: works within the boundaries you already have.

What it helps with

  • debug IPC messaging and data flow between main and renderer processes
  • minimize Node.js surface in preload to close security gaps
  • ensure IPC failures don't deadlock or freeze the UI
  • validate that code changes remain compatible with app signing and distribution
  • understand window lifecycle, multi-window state, and startup/shutdown behavior

Example prompts for the agent

  • Help me understand the boundary between main and renderer, and how to safely pass data across the IPC bridge
  • Show me how to move file-save logic to the main process and report back the path to the renderer
  • Review my preload script: what actually needs to be there, and what's a security risk

How to install electron-pro

Manually: put the files in place

.codex/agents/electron-pro.toml

Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about electron-pro

How do I install electron-pro in Codex?

Create .codex/agents/electron-pro.toml at the project root.

What does electron-pro do?

It helps you navigate Electron's process architecture: clarifies responsibility split between main, preload, and renderer; designs and validates IPC contracts; checks preload attack surface; and flags packaging or signing assumptions you may have broken.

How does electron-pro handle security?

It enforces a minimal, explicit allowlist for preload APIs instead of exposing all Node.js; validates IPC error handling and trust boundaries; and calls out CSP and session-config implications.

Source text

electron-pro.toml · MIT
# electron-pro

Use when a task needs Electron-specific implementation or debugging across main/renderer/preload boundaries, packaging, and desktop runtime behavior.

Treat Electron work as cross-process desktop engineering with security-sensitive bridges.

Working mode:
1. Map responsibility split across main process, preload bridge, and renderer.
2. Implement the narrowest process-aware fix or feature change.
3. Validate runtime behavior, IPC integrity, and packaging impact.

Focus on:
- ownership split between main, preload, and renderer
- IPC contract shape, error handling, and trust boundaries
- preload exposure minimization and context-isolation safety
- window lifecycle, multi-window coordination, and startup/shutdown behavior
- file system/native integration and permission-sensitive operations
- auto-update, packaging, signing, and env-config assumptions when touched

Security checks:
- avoid unnecessary Node surface in renderer
- enforce explicit allowlist behavior for bridge APIs
- call out CSP/session/security-preference implications

Quality checks:
- validate one normal interaction path and one failure/retry path
- verify IPC failures do not dead-end UI state
- ensure changed behavior is coherent in packaged-app assumptions
- document manual checks required for signing/update flows

Return:
- affected Electron process paths and files
- implementation or diagnosis
- validation performed
- remaining security/runtime/packaging caveats

Do not redesign app architecture across processes unless explicitly requested.

© VoltAgent · MIT · VoltAgent/awesome-codex-subagents

Similar subagents

All subagents for Agent setup: memory, context, orchestration →

electron-pro by other authors comes first.

electron-pro VoltAgent Community electron-pro — a subagent for building desktop software on Electron 27+. Enforces context isolation, secure IPC via preload scripts, auto-updaters, and signed installers. CX Codex 376installs electron-pro qdhenry A Claude subagent that runs an Electron project written in TypeScript: main and renderer processes, IPC through a preload bridge, packaging with electron-builder. CX Codex ★ 1,357repo stars electron-development davila7 electron-development — a Claude skill for building Electron desktop apps: context isolation, safe IPC through preload, electron-builder packaging and auto-update. CX Codex +1 98installs electron-dev pedronauck electron-dev guides agents through building Electron apps with Electron Vite and Electron Builder. It focuses on process separation, IPC safety, and native dependencies. CX Codex +1 311installs electron gentleman-programming Guides desktop app development in Electron with secure IPC patterns, typed channels, and clear separation between main and renderer processes. CX Codex +1 175installs electron-skills llama-farm Electron 28 and electron-vite patterns for desktop software. Guides context isolation, secure IPC bridges, and cross-platform builds. CX Codex +1 1installs electron-expert 0xfurai electron-expert — a Claude subagent for Electron desktop apps: main and renderer split, window security, IPC, and packaging for macOS, Windows and Linux. CX Codex ★ 1,029repo stars electron-desktop travisjneuman electron-desktop — a skill for building cross-platform desktop applications with Electron for Windows, macOS and Linux. CX Codex +1 236installs

From the same set176

The whole set →
microservices-architect microservices-architect maps service boundaries, contracts, and failure paths. Use it to review a distributed design or plan a change to service ownership. CX Codex ★ 6,505repo stars graphql-architect graphql-architect — a subagent that audits GraphQL schemas for architectural flaws, performance risks, and security gaps. Guides schema evolution, resolver design, and federation without breaking clients. CX Codex ★ 6,505repo stars fullstack-developer fullstack-developer handles bounded cross-layer features from user actions down to backend effects and UI updates. Useful when a single worker needs to own the full integration path. CX Codex ★ 6,505repo stars frontend-developer frontend-developer — a scoped subagent for frontend changes and UI bug fixes, with checks for state integrity, accessibility, and nearby regressions. CX Codex ★ 6,505repo stars design-bridge design-bridge converts DESIGN.md documents into precise, structured UI instructions for implementation agents. CX Codex ★ 6,505repo stars code-mapper The code-mapper subagent maps code paths, ownership boundaries, and execution flow before edits. Use it when behavior is spread across several layers. CX Codex ★ 6,505repo stars backend-developer backend-developer is a Codex subagent for scoped backend implementation and bug fixes once the owning code path is known. It checks a success case and a high-risk failure path. CX Codex ★ 6,505repo stars api-designer api-designer designs API contracts, plans versioning, and inspects breaking changes before implementation starts in Codex. CX Codex ★ 6,505repo stars

Project sponsors

Companies that keep this analytics open