Start with a clear desktop
Before creating the workflow, close or hide what does not belong.
Give the workspace room to become intentional. Start from an empty desktop. Add back only what belongs.
Decide what truly belongs
A good workflow should feel light.
Do not add every possible future item. Add the apps, folders, files, and links you regularly need when this work begins.
For development work, choose the pieces that define this project stack. Keep separate repos, unrelated tickets, old docs, and other local apps out so the workflow stays tied to one build surface.
- What do I always open for this work?
- What do I leave open because I do not want to find it again?
- What helps me start?
- What adds clutter?
- What can stay out until I actually need it?
Open the pieces intentionally
Once you know what belongs, open those pieces on purpose before creating the workflow.
Open the editor, repo folder, project references, issue context, and browser surfaces that belong to this build. Keep other projects and experimental tabs out of the capture.
Example workflow: Website build session
A focused developer workflow can restore the editor, command surface, and running local site for one project.
Create the workflow
Name the workflow, choose an icon, then press Next.
Scan open apps
On the Select screen, press Scan Open Apps. ZenFlow lists what is currently running. Check the apps you want this workflow to open, then press Next.
Confirm app positions
On the Position screen, review where the selected apps are positioned. If the layout looks right, press Customize.
Customize what each app opens
On the Customize screen, use the app list and dropdowns to attach files, URLs, or script commands. When the workflow has what it needs, press Finish. How you connect the program to a file or web address depends on the type of program.
VS Code
On the Customize screen, open the VS Code row, choose Add Files, and select the project workspace file, repo folder shortcut, or file that should reopen with the build.
Specific click-by-click instructions and program screenshots will be added here.
PowerShell
Open the PowerShell row and use Enter a script command for each command you want ZenFlow to run. For a simple local site, add cd C:\path\to\project, press the checkmark, then add npm run dev and press the checkmark again. Use the + button at the top for more command lines.
Specific click-by-click instructions and program screenshots will be added here.
Browser with local site running
If the browser extension is installed, open the local site tab before scanning so ZenFlow can capture it. Without the extension, open the browser row on the Customize screen, enter the local site address in Enter a URL, then press the checkmark.
Specific click-by-click instructions and program screenshots will be added here.
Use the workflow
Press Play when you are ready to return to this work.
ZenFlow opens the pieces you saved so the workspace feels familiar without making you rebuild it by hand.
Stop the workflow
Press Stop when the work is finished or paused.
ZenFlow closes what it opened with a soft close request, so you stay in control if something has unsaved work or needs your attention.
Keep it light
The best workflow is not the biggest one.
It is the one that makes returning to work feel easier.
Add more later if you keep reaching for the same thing. Leave things out if they make the workflow feel heavy.