Skip to main content
Each time a workflow runs, Enclave records what started it, what each step did, what it cost, and what it saved.

Start a run

  • From Research: ask, for example Run the Workflow "Security hunt" on payments-api. Check the inputs and budget on the card, then click Approve.
  • From the workflow: open its menu and click Run now.
  • Automatically: add a trigger.
  • From your AI assistant: connect MCP and ask it to start the workflow. This works for workflows that take no inputs or only findings.
If the workflow’s prompts read event data, the card asks you for a value for each field before you start it.

Follow a run

Open a workflow and click Runs. Click a run to watch its steps update live. Click a step to see its output. To stop a run, click Stop run on the run page, or ask Research and approve the card. Results it already saved stay.

Message a running agent

While a run is working, you can message one of its agents to guide it, for example to point it at a file or narrow what it checks. Messaging needs the Owner or Admin role by default.
  1. Open the agent. On the run page, click a step, then View activity. From Research, click View agents on the run’s card.
  2. Type in the Message box under the agent’s activity and press Enter.
The agent reads your message before its next step. A message guides the agent but can’t stop the run. To stop it, use Stop.

Pause and resume

A run you start from Research, Run now, the API, or the CLI pauses instead of ending:
  • At its budget. The run pauses when it spends its budget. If Research started it, a notice appears in that conversation.
  • When your organization runs out of credits. If the run can pause, it pauses when it needs its next AI model call. Add credits before you click Resume.
  • When you pause it. Click Pause on the run page. The run pauses at its next agent step and keeps its budget.
To continue, click Resume on the run page or in the notice, or ask Research. A run paused at its budget asks for a new budget. The run continues from the step that stopped. A paused run that no one resumes ends. Runs started by a trigger or Enclave, such as automatic PR reviews, end at their budget; if they run out of credits, they may fail instead of pausing.

Approve tool calls

A tool’s Approval setting decides whether its calls wait for a person. You choose it when you create the workflow. See Approval. Approving tool calls needs the Owner or Admin role by default. On the run page, the Approvals tab lists the calls that wait for a decision. Ask first: waits for OK: the agent holds the call and keeps working on the rest of its task. Click Approve to make the call, or Deny to refuse it. You can also answer from Research: click View agents on the run’s card or notice. Ask later: runs once OK’d: Enclave saves the call, and the agent carries on. The run can finish before anyone decides. The person who started the run gets a notification. Click Approve to run the saved call, or Reject to drop it. A call no one decides eventually expires.

Results

Open a run and click Outputs to see what it produced. Outputs appear as the run saves them, so you can open them before it finishes.
  • Saved outputs: the reports and files the run’s agents saved. Click Download to get any output.
  • Findings: the findings the run created. Findings in repositories you can’t see are counted but not listed.
A run that saved no outputs and created no findings shows its last step’s output instead.

Run notifications

When a run fails or times out, the person who started it gets an entry in the notification bell that says why the run stopped. If a trigger started the run, the workflow’s author gets the entry. When a run you started finishes, you get an entry too. Click View run to open the run. Stopped runs and runs of built-in workflows, such as repository scans, don’t add entries. You see an entry only while you can still open its run.

History and restore

The History tab lists every revision with a summary of what changed. Click Restore to roll a custom workflow back.

Archive a workflow

Open a custom workflow’s menu and click Archive. It can’t start new runs, and its past runs stay. Starting, pausing, resuming, stopping, messaging agents, and archiving need the Owner or Admin role by default.