Workflows
A workflow is a plan attached to one terminal. Each step names the steps it waits on, so some steps run one after another and others can run at the same time. Launch it from a template, and the agent in that terminal works through it, reporting each step as running, done, failed, skipped, or waiting on you. Terminay draws the progress beside the terminal and never runs a step itself.

Steps And Dependencies
Every step has a list of the earlier steps it waits on. A step is ready once each of those is done or skipped, and the agent may work on any number of ready steps at the same time, for example with sub-agents. A plan such as "propose, have two reviewers look at it, then amend" has one step, then two that each wait on it, then one that waits on both.
- A step can only wait on steps above it, so a plan can never loop.
- A plain list of steps runs one after another: each waits on the step above it.
- Starting a step before everything it waits on is done or skipped is refused. A step already under way can always report and finish.
- A workflow is finished when every step is done or skipped. Skipped steps count as done in its progress.
Templates

Workflow templates live in Settings. Choose your server's tile in the rail, then Automation → Workflows, and choose New workflow. Fill in:
- Name, Description, and an optional Category.
- Opening prompt: the goal the whole workflow serves.
- Steps: one to 50, each with a title, a prompt, and an optional icon such as an eye, a lightbulb, a wrench, a flask, a bug, or a pull request.
The steps are edited as an outline, drawn the way the workflow panel draws them. The outline sets what each step waits on:
- + then adds a step directly after this one.
- + alongside adds a step that runs at the same time as this one, inside a bracket.
- + another track alongside adds another track to a bracket.
- + Add step at the end adds a step that waits on everything before it.
Click a step's title to rename it, its icon to pick another, and open its prompt to edit it beneath the row. Drag a step's handle to move it within its track, or focus the handle and press Alt+↑ or Alt+↓. Removing a track's last step removes the track.
A template made over MCP can hold a dependency the outline cannot draw. The editor shows it as "after" and the step titles beneath the step, and keeps it while you edit only names, icons, and prompts. Adding, removing, or moving a step sets every dependency from the outline instead.
The editor shows the exact text launching the template will type into the terminal. Templates belong to the server and are shared by every device attached to it. Their order in Settings is their order in the Command Bar. Filter the list by any name, prompt, or step.
Launching A Workflow

Focus the terminal that runs your agent, open the Command Bar, and choose a template. It is listed under its category, or under Workflows when it has none. Terminay attaches a copy of the template to that terminal with every step not started, then types one line into the terminal and submits it:
/goaland the template's opening prompt;- an instruction to call
get_workflow, start a step only once every step it waits on is done or skipped, work on ready steps at the same time where it can, set each step to running before starting it, and mark it done with a one-line note, failed with the reason, needs input when it needs you, or skipped when it does not apply.
The line is typed as keystrokes, not pasted, so agents such as Claude Code receive it as a command. The agent needs Terminay MCP installed to report progress. A terminal holds one workflow at a time; launching another over an unfinished one asks you first, naming the one it would replace. Later edits to a template never change a workflow already launched from it.
The Workflow Panel
A terminal with a workflow shows it inside its pane, in one of two layouts. The terminal ends before it, so nothing is covered. Choose the layout from the ⋯ menu at the panel's top right. It applies to every terminal on this device.
Vertical
The vertical layout is a panel along the right edge of the pane.
- Expanded: the workflow's name, how many steps are done, running, and waiting on you, the time since the first step started, the opening prompt as a collapsible brief, and each step's title, duration or running time, and note. Steps that run one after another are joined by a line. Steps that can run at the same time sit side by side in a bracket, coloured red if any of them failed or needs you, amber while one runs, and green once all are done. Every running step is highlighted. Hover or focus a step to highlight what it waits on and what waits on it.
- Collapsed: a narrow rail of one marker per step, with each bracket drawn as a capsule and the workflow's name along the bottom. Markers are green when done, amber while running, red when failed or waiting on you, grey before they start, and dashed and dimmed when skipped.

Drag the expanded panel's left edge to resize it, or focus the edge and press ← or →. A pane too narrow for the expanded panel beside a 60-column terminal shows the rail, and expanding it there opens the panel over the terminal until you press Escape or click back into the terminal.
Horizontal

The horizontal layout is a drawer along the bottom of the pane that draws the workflow as a metro map. Each step is a station, placed one column to the right of the furthest step it waits on, so the line splits where steps run side by side and joins where a step waits on several. A line turns solid green once the step it leaves is done. Select a station, by clicking it or with Tab, the arrow keys, and Enter, to read its status, time, and note in full beneath the map. Collapsed, the drawer is a one-row strip with the map drawn small and the names of the steps under way.
The ⋯ Menu
- Show as: Vertical or Horizontal. Each layout remembers whether it is collapsed.
- Step notes (vertical): Full, 2 lines, or Current only, which shows only the notes of steps that are running, failed, or waiting on you.
- Remove workflow… ends the workflow after you confirm, without touching the terminal.
Skipping A Step
The expanded panel, and a selected station in the drawer, offer Skip on a step that has not started or has failed, and Restore on a skipped step. A skipped step is struck through and lets the steps that wait on it start. Neither types anything into the terminal.
Progress Elsewhere
The terminal's tab, its row in the Tabs sidebar, and its row in the phone switcher show a small progress dial, filled to the share of steps done. It is amber while a step runs, red while a step has failed or needs you, and green when the workflow is finished. Hover it for the current step, how many steps are done, and for how long. A finished workflow's dial goes once you have looked at the terminal. The collapse, layout, width, and note settings all apply to every terminal on this device.
The Workflows section of Home shows every terminal's workflow on the server side by side, so you can see which are moving and which need you.
Lifetime
A workflow lasts as long as its terminal session. It follows the terminal when you move it to another project, survives server restarts while the terminal keeps running, and ends when the terminal closes. Remove it from the ⋯ menu to end it without touching the terminal.
Workflows Over MCP
Agents use these Terminay MCP tools. Each acts on the calling terminal unless it names another one within its reach, and addresses steps only by id.
| Tool | What it does |
|---|---|
get_workflow | Reads the terminal's workflow: every step with its status, note, times, and after list, the ready_step_ids that can be worked now, and the step to resume from. |
update_workflow_step | Sets a step to not_started, running, done, failed, needs_input, or skipped, with an optional one-line note. Any number of steps can be running at once. Starting a step whose dependencies are not all done or skipped fails with step_blocked, naming them. |
create_workflow | Attaches a workflow, either a copy of a template by template_id or one the agent writes itself. Each step may carry an id and an after list naming earlier steps by those ids; a step without after waits on the step above it. Nothing is typed into the terminal. |
list_workflow_templates, get_workflow_template | Read the server's templates, including each step's after. |
create_workflow_template, update_workflow_template, delete_workflow_template | Change templates, exactly as Settings does, with after on steps as for create_workflow. These are in the Workflow Templates permission group, which asks you first by default. |
Pixel, agent chats, and bots with Terminay MCP access can use the workflow tools too, naming the terminal they mean.
Workflows, Macros, And Automations
A macro types steps into a terminal for you. An automation starts on its own from a schedule or an event. A workflow is a plan an agent follows and reports on; Terminay only keeps score.