> For the complete documentation index, see [llms.txt](https://docs.sealsecurity.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealsecurity.io/using-platform/seal-engineer.md). # The Seal Engineer The Seal Engineer is the automated, schedulable side of the Seal Platform's AI features. Where the [Seal AI Agent](/using-platform/seal-ai-agent.md) is a chatbot you talk to in the UI, the Seal Engineer is a workflow runtime you set up once and let run on a schedule. It executes named **flows** — recurring tasks the Seal Engineer carries out for your team: surveying open vulnerabilities, drafting remediations, summarizing changes, posting results. The Seal AI Agent and the Seal Engineer are distinct features. You **talk to** the Seal AI Agent; you **schedule** the Seal Engineer. Most tenants that use one use both, but they live in different parts of the UI and address different operating patterns. Both features are off by default and only available to tenants that have explicitly enabled AI features in their settings. Customers who do not want AI features have no AI running on their data. ## What a flow is A flow is a named, scheduled task the Seal Engineer carries out repeatedly. Each flow has: * **A task definition.** Either one of the prebuilt **flow templates** (a curated set of common security-engineer tasks) or a **free-text task** you write yourself. The free-text option is for tasks the templates do not cover. * **A persona.** One of four preset personas the flow uses when it does its work and posts results. * **A tone.** One of two preset tone settings. * **A schedule.** See "Scheduling" below. * **An output channel.** Either a Slack channel or an in-app channel. The choice determines where the flow posts and where reviewers interact with it. A configured flow runs at its schedule, executes against your tenant's data, and posts to its configured channel. Manual triggers from the Seal Engineer UI are also available. ## Output channels: Slack and in-app The Seal Engineer posts its output to a Slack channel or to the in-app channel inside the Seal UI. Either way, the post is where reviewers interact with the run. Replies to the post are how a reviewer responds to the Seal Engineer, asks it to refine an output, or approves a proposed change. The full output and the conversation that follows live where the post landed. ## Scheduling A flow's schedule is either: * **Fixed daily or weekly** — pick the days of the week and the time of day. * **Interval-based** — every N hours, with N ≥ 6. The minimum interval is **6 hours**. The platform refuses cadences shorter than that to keep flows from burning through your AI token quota too quickly. Manual triggers from the Seal Engineer UI run a flow out of cycle. ## The UI: three views with a persistent left pane
Seal Engineer UI showing the left pane with a list of flows and the Creating a new flow form in the center

The Seal Engineer UI: a persistent left pane and a switchable center view.

The Seal Engineer UI has a persistent left pane and three main views in the middle of the screen that switch based on what you select. The three views: * **Creating or editing a flow.** A form for defining or modifying a flow: task (template or free-text), persona, tone, schedule, output channel. * **Viewing a flow.** The configuration and run history of an existing flow. * **Viewing a flow run.** A specific past or in-progress run: the original parameters at the time of the run, and the result the flow produced. For flows that require approval (see "Approval", below), the approval moment shows Accept and Deny buttons inline. The flow-run record saves the original parameters and the result for later review. ## Approval Some flow templates ask for approval before they act. The Engineer drafts the proposed change, posts it to the configured channel, and shows **Accept** and **Deny** buttons; the change commits only after Accept. Other flow templates act autonomously. For example, the **Auto-seal & notify** template creates a Sealing Rule to remediate the vulnerability it found, then notifies the channel that the rule was created. There is no per-run approval gate; the notification is after the fact. The template's description in the Flows UI says whether it acts or proposes. If you want a stricter posture, prefer templates that propose and wait. If you want more automation, use the autonomous templates and review the notifications. ## Connecting Slack A Slack connection is needed before a flow can post to a Slack channel. Three places set it up: * **Settings → Integrations** — connect Slack directly from the Settings page. The result is available to every flow afterward. * **Through the Seal AI Agent** — when you ask the Seal AI Agent to create a Seal Engineer flow that posts to Slack and no Slack connection exists yet, the Agent shows a link to start the Slack OAuth install. * **In the Seal Engineer UI** — when you are creating a flow whose output channel is Slack and no Slack connection exists yet, the UI shows a button to install the Slack integration before the flow can save. Slack belongs to the Seal Engineer's workflow output. It is not used by the Seal AI Agent itself. ## Creating a flow through the Seal AI Agent The Seal AI Agent can create a Seal Engineer flow on your behalf. Ask the Agent to set up a recurring task — "every Monday at 9am, summarize last week's new vulnerable packages and post to #security" — and the Agent drafts the flow configuration and presents it for your approval before creating it. ## When to use the Seal Engineer instead of the Seal AI Agent * **Use the Seal AI Agent** for ad-hoc questions and one-off actions a person is sitting in front of. Quick, interactive, conversational. * **Use the Seal Engineer** for recurring work you want to delegate. A weekly inventory pass, a daily summary, an autonomous re-seal cycle. Both features coexist; many tenants use the Engineer for routine work and the Agent for specific questions about a run. ## Related * [The Seal AI Agent](/using-platform/seal-ai-agent.md): the chatbot side of the AI features. * [Sealing Rules](/using-platform/sealing-rules.md): the rule mechanic the Engineer's write actions go through.