Dynamic Workflows help Happycapy handle complex Project work as a staged run instead of one long reply. Use them when a task needs planning, context gathering, subtasks, parallel subagents, review, and saved files.You still start from a normal Project message. Enable Dynamic Workflows in Settings first, then describe the outcome and the final files you want. Happycapy can plan the run, split work into subtasks, use subagents when helpful, review intermediate results, and save the final artifacts back to the Project.
Dynamic Workflows are an experimental capability. Open Settings, go to Experimental, and turn on Dynamic workflows before using them in a Project.
SettingsOpen Experimental and turn on Dynamic workflows.
Dynamic Workflows can use a lot of credits. They may run multiple stages, read more context, call more tools, create intermediate artifacts, and use subagents in parallel. Save them for complex, multi-step work where redoing the task would be expensive.
Do not assign each subagent yourself. Tell Happycapy what work you need done and which files you want at the end. Happycapy decides how to plan, split, review, and save the work.
Use Dynamic Workflows for this task.I am preparing to launch an AI video script tool for independent creators.Please research and plan the launch from these angles:- target users- competitors- pricing- content channels- first features- launch risksCreate the following files:- outputs/market-entry-brief.md- outputs/competitor-comparison.csv- outputs/two-week-launch-plan.xlsx- outputs/landing-page-outline.html- outputs/social-posts.json
Avoid Dynamic Workflows for simple questions, short copy edits, quick translations, and small one-file changes. A normal Project message is cheaper and faster for those.
During a run, Happycapy turns your request into a plan, splits work into subtasks, uses subagents when parallel work helps, checks intermediate results, and saves the final files back to the Project.That is what makes the process dynamic: the route can adjust while the task is running, instead of following a fixed template.
Start with a focused scope before handing over a very broad task. Name the final files, review the first run, then expand the workflow when the pattern is stable.If you repeat the same workflow often, ask Happycapy to turn the pattern into a reusable Project instruction or Skill. If it should run on a schedule, connect the stable prompt to an Automation.
