Workflows

A workflow is a persistent session in which an agent (or a team of agents) works through a task on your behalf. Unlike a quick query or a one-shot Pulse trigger, a workflow is designed for work that takes multiple steps, may require your input at decision points, and produces deliverables that belong to a record in your workspace.

Starting a workflow

You describe the task in plain language and select an agent. The agent begins working immediately — reading relevant records, taking actions, and producing outputs. You can watch the session as it progresses or step away and return to review the results.

The session transcript is permanent. Every reasoning step the agent took, every tool it called, every record it read or wrote, and every file it produced is logged in full. You can review the transcript to understand exactly what happened and why.

Human-in-the-loop

Workflows are designed to pause at the right moments. There are two types of pause:

Approval requests. When an agent is about to write to a sensitive record type — a financial record, a person's data, a legal matter — the Kernel pauses the session and presents you with an approval card. The card shows exactly what the agent intends to write. You approve or reject. If you reject, the agent is informed and adjusts its approach. The session continues either way.

Questions. Some agents need a decision from you before they can proceed: "Which client does this belong to?" or "Should I send the demand letter today or wait for the imaging records?" When an agent asks a question, the Kernel pauses and surfaces a question card. Your answer is fed directly back to the agent, and the run resumes.

These interruptions are not failures. They are the designed behavior for work that should not proceed without a human judgment call.

Injecting into a running session

You can send a message into a running workflow at any time — not just when the agent is paused. This is useful when you have new information the agent should know, when you want to redirect the task, or when you simply want to provide context mid-run. The agent incorporates your message into its next reasoning step.

Subtasks

Agents can decompose complex work into subtasks. Each subtask is a named checkpoint with a status — pending, in progress, done, or blocked. You can see the subtask list at any time to understand the agent's plan and track progress. If a subtask is blocked, the agent says so explicitly rather than silently getting stuck.

Delegation within a session

When a specialist agent can handle part of the work better than the current agent, the current agent can delegate a subtask to the specialist. The specialist runs as a child session, completes its work, and returns results to the parent. The full chain is visible in the session transcript.

Delegation is bounded by the rules described in the Agents section: clearance ceilings, delegation caps, and cycle prevention all apply. The parent agent cannot bypass these by delegating to itself or to a higher-clearance agent.

Round Table

Some tasks benefit from multiple agents working together simultaneously. A Round Table is a session format where several agents take turns contributing to a shared task, with a moderator agent deciding the ordering and determining when the work is complete.

Each participant produces its own output in its own turn. The moderator reads those outputs and routes the conversation — asking one agent to follow up on another's work, combining outputs, or calling the session complete. You can send messages into the round table at any time, and the moderator incorporates your input in the next routing decision.

Deliverables

When an agent produces a file that you should receive — a demand letter, a case summary, a financial report — it marks that file as a deliverable. Deliverables appear in the session's file panel and are linked to the relevant records in your workspace. They are permanent: they remain attached to the workspace even after the session is archived.

Reviewing past sessions

Every workflow session, past or present, is accessible from the Workflows interface. You can:

• ▸Read the full transcript
• ▸Download deliverable files
• ▸See which records were written and by whom
• ▸Replay the approval sequence
• ▸Understand where the agent spent its time (a session analytics view shows time per step)

Sessions are searchable by agent, status, date, and the records they touched.

When to use Workflows vs. Pulse

Use Workflows when:

• ▸A human needs to be involved at decision points
• ▸The task takes multiple steps and spans a session
• ▸You want to review the reasoning, not just the output
• ▸The work produces named deliverables

Use Pulse when:

• ▸The trigger fires automatically without a human initiating it
• ▸The logic is deterministic enough to run unattended
• ▸The output is a record update or a notification, not a deliverable requiring review