Embedded apps (Windows)

Cerevisor can embed real Win32 applications as nodes on the canvas. The actual Outlook, Excel, or Word window appears inside the node; you interact with it normally, and agents in your workflow can pull data from it. Windows-only feature. The macOS build hides this entire surface ( CAPS.embeddedApps is false on Mac). Workflows authored on Windows that include embedded-app nodes will render placeholders on macOS so the .cerevisor file round-trips cleanly. Supported apps The current registry: Outlook : emails, calendar events, contacts. Excel : spreadsheet data, named ranges, sheets. Word : document content. Edge / Explorer / Notepad : generic window embed for visual context. Generic : embed any Win32 app without specialized data extraction. Each app's data-source integration lives in a single registry; adding a new app is a one-entry change. Adding an embedded app to the canvas Two paths: Right-click canvas → Embed app. Opens the Embedded App Picker modal. Embedded Apps Dock in the bottom-left corner of the canvas → + Embed app . The picker shows a grid of supported apps. Click one. For some apps (Outlook), Cerevisor auto-detects the running instance and attaches to its main window. For others (Generic), you're prompted to pick a window. The embedded app appears as a node on your canvas with the app icon + name and a transparent shell over the real native window. Window embedding mechanics Behind the scenes, Cerevisor uses a single shared PowerShell child process running window-embed.ps1 that multiplexes Attach/Move/Detach calls across every active embedded-app node. One PowerShell child handles all your embedded apps (Add-Type compilation is slow; per-embed children would be wasteful). The embedded node: Re-parents the native window to Cerevisor's window region. Resizes/moves the native window to track the canvas node. Forwards mouse and keyboard events to the native window so you interact normally. Connecting embedded apps to agents Drag from the embedded app node to an agent. The Embed Data Selection popup opens, showing which data feeds are available for that app: Outlook: Selected emails, current calendar view, contacts. Excel: Active sheet, named range, selection. Word: Current document text. Generic apps: No structured feeds: connection is rendered as a visual link only. Pick a feed. The connection is created. The agent now reads from the embedded app's live data when it runs. How agents consume embedded data When the workflow runs, the agent's input includes the embedded app's data via Cerevisor's data-source registry. For Outlook, the harness: Calls the Outlook data source's getSelectedMail() (or whichever feed you picked). Serializes the result as text. Injects it as part of the agent's input. The agent reads it via the standard input mechanism, same as any other input. Removing an embedded app Right-click the embedded app node → Delete . The native window detaches and returns to its normal state. The Embedded Apps Dock at the bottom-lef

Back to docs