In Devin Desktop (formerly Windsurf), how is a Cascade workflow stored and invoked, and why does Cascade never start one on its own?
answer
- a Markdown file of steps
- a slash command by name
- manual by design
- four levels share one name
- skills replace them in Devin Local
basics
~20 sA Cascade workflow is a Markdown file of steps in .devin/workflows/ (legacy .windsurf/workflows/), run only when someone types /workflow-name. It is manual by design; procedures the agent should pick up itself belong in skills, which also replace workflows in Devin Local.
solid answer
~40 sA workflow is a Markdown file with a title, a description and a series of steps, saved in `.devin/workflows/` (or the legacy `.windsurf/workflows/`) and run in Cascade with the slash command `/[workflow-name]`. Cascade then works through the steps in order, and a workflow can call others, such as "Call /workflow-2". Workflows are manual-only: Cascade never invokes one automatically, because a workflow is a runbook you trigger on purpose, and the docs point to skills for procedures the model should pick up itself. Files are limited to 12,000 characters. Workspace workflows are committed; global ones live in `~/.codeium/windsurf/global_workflows/`; IT can deploy system-level ones, which win over workspace, global and built-in workflows of the same name. The Devin Local agent does not support workflows; the Cascade Migration Wizard turns them into skills.
code
markdown · 9 lines# Address PR comments
Work through the review comments on a pull request, one at a time.
1. Check out the PR branch: `gh pr checkout [id]`
2. List the review comments with `gh api` for that pull request.
3. For each comment, make the change before moving to the next one.
If a comment is unclear, ask me instead of changing code.
4. Summarise what changed and which comments need my attention.go deeper
Recall that a workflow is a Markdown file of steps in .devin/workflows/, run with /workflow-name, and never started automatically.
Explain the four storage levels, their precedence for a shared name, the 12,000-character limit, and how workflows differ from rules and skills.
Show you would inventory a repository's workflows before a move to Devin Local, decide which become skills, and check system-level folders were moved rather than duplicated.
Weigh explicit, human-triggered runbooks against model-invoked skills: one gives control over side effects, the other saves prompting but lets the agent decide when to act.
## What a workflow is A **workflow** in Devin Desktop is a saved, repeatable sequence of instructions for the **Cascade** agent: deploying a service, addressing pull-request comments, running the tests and fixing what fails. The docs contrast it with rules: rules give the model persistent guidance **at the prompt level**, while a workflow gives a structured sequence of steps **at the trajectory level**, walking the agent through connected tasks. Each workflow is a Markdown file containing a title, a description and the steps. ## Invoking one - Type `/[workflow-name]` in the Cascade input; Cascade then processes each step in sequence. - A workflow can call other workflows: a step such as "Call /workflow-2" chains them. - Workflows are **manual-only**. The docs state that Cascade will never invoke a workflow automatically, and they are listed as available commands rather than placed in the system prompt. - If the agent should pick a procedure up by itself when a request matches, the docs point to a **skill** instead, which the model invokes from its description. That split is intentional: a workflow is a runbook a person chooses to start, which suits steps with side effects such as a deployment. ## Where workflows live | Scope | Location | Notes | | - | - | - | | Workspace | `.devin/workflows/*.md` (preferred) or `.windsurf/workflows/*.md` | in the workspace, any subdirectory, or a parent up to the git root; committed | | Global | `~/.codeium/windsurf/global_workflows/*.md` | every workspace on one machine; not committed | | Built-in | managed by Devin Desktop | templates such as `/plan` | | System (Enterprise) | for example `/etc/devin/workflows/`, legacy `/etc/windsurf/workflows/` | deployed by IT, read-only for users | A workflow created from the **Workflows** panel with **+ Workspace** is saved in `.devin/workflows/` of the current workspace, not necessarily the git root; if a workspace still has a `.windsurf/` directory and migration was declined, it goes to `.windsurf/workflows/` instead. Each workflow file is limited to **12,000 characters**. ## When two workflows share a name Precedence runs from the organisation down: 1. **System**, deployed by IT, highest priority. 2. **Workspace**, in `.devin/workflows/` or the legacy folder. 3. **Global**, in `~/.codeium/windsurf/global_workflows/`. 4. **Built-in**, shipped with Devin Desktop. So an organisation's `/deploy` overrides a project's `/deploy`. At system level, the `Devin` folder is loaded if it exists and the legacy `Windsurf` folder is used only when it does not; the two are **not merged**, so an admin creating the new folder must move the old workflows into it. ## Workflows and the newer agent Workflows belong to Cascade. The **Devin Local** agent, the default for new tabs, does not support them, and the docs direct teams to convert them into **skills** with the **Devin: Open Cascade Migration Wizard** command. The changelog shows the direction of travel: v3.6.22 (July 29, 2026) made workflow surfaces explain that workflows are being deprecated in favour of skills, v3.9.19 (September 8, 2026) says Cascade has been removed, and v3.10.23 (September 10, 2026) lists workflow commands among the legacy Cascade entry points it removed. Knowing workflows is still useful for reading a Windsurf-era repository full of `.windsurf/workflows/` files, and for knowing what a migration has to carry across. ## Workflows, rules and skills compared | | Workflows | Rules | Skills | | - | - | - | - | | Shape | a single `.md` file of steps | a single `.md` file with frontmatter | a folder with `SKILL.md` and supporting files | | Invocation | manual only, `/[workflow-name]` | `always_on`, `glob`, `model_decision`, `manual` | chosen by the model, or an @-mention | | In the system prompt | no, listed as commands | depends on the mode | only name and description until invoked | | Best for | one-shot runbooks you trigger yourself | conventions and constraints | procedures the agent should find by itself | The docs' rule of thumb: if you always want to trigger it yourself, use a workflow; if it is a short behavioural constraint, use a rule; if the agent should pick it up and it needs supporting files, use a skill. ## Mistakes to avoid - Expecting Cascade to run a matching workflow without the slash command. - Putting a team runbook only in the global folder, where nobody else can see it. - Assuming a workspace workflow can shadow an IT-deployed one of the same name.
- When would you choose a skill over a workflow for a deployment procedure in Devin Desktop?When the agent should pick the procedure up by itself, or needs supporting files. A workflow is manual-only and runs only from `/[workflow-name]`, while a skill is invoked by the model from its `description` or by an @-mention and can bundle scripts and templates beside `SKILL.md`. Skills, unlike workflows, also carry over to the Devin Local agent.
- An admin adds /Library/Application Support/Devin/workflows/ on macOS, and older system workflows disappear. Why?System-level workflows load from the `Devin` folder when it exists and fall back to the legacy `Windsurf` folder only when it does not; the two are not merged. Creating the new folder therefore hides the legacy one, so the old workflows must be moved into the `Devin` folder.
- Cascade starts a matching workflow by itself when the request fits.
- A workflow can be given trigger: always_on so it runs on every message.
- Global workflows in ~/.codeium/windsurf/global_workflows/ are committed with the repository.
- One workflow cannot call another workflow.
- The Devin Local agent runs .devin/workflows/ files as slash commands too.
- A workspace workflow overrides an IT-deployed system workflow of the same name.