You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my daily office work, I often need to repeatedly handle the same type of task. These tasks share a common characteristic:
The processing flow for the entire task is fixed, and usually requires 4 rounds of dialogue (or even more) to complete;
Each round of dialogue requires inputting a fixed user prompt, a specified model, and specific skills (skill / tool);
Every time I handle a new task, I have to repeatedly configure these 4 rounds of dialogue from beginning to end, entering the same prompts again and again, switching to the same models, and attaching the same skills.
This repetitive configuration is extremely cumbersome, highly inefficient, and prone to errors (for example, forgetting to switch models or missing a skill in one of the rounds).
My Needs
I hope the project can support building a complete set of reusable workflows, with the following specific requirements:
1. Multi-node workflow orchestration
A complete task consists of N nodes, each corresponding to one round of dialogue;
For example, a task requiring 4 rounds of dialogue would have 4 nodes configured;
Nodes execute in order, forming a reusable pipeline.
2. Each node can be configured independently
Each node should be able to independently set the following:
Configuration Item
Description
User Prompt
The content to be sent to the model in that round of dialogue
Model
Which model is used in that round (different rounds may use different models)
Skill / Tool
Which skills or tools need to be attached in that round
3. Each node supports multiple user prompts
This point is crucial to me: sometimes within the same node (the same round), I need to send multiple user prompts in sequence, for example:
First ask the model to make a plan;
Then ask the model to re-examine this plan;
Finally, set goals / add constraints for it.
In other words, within a node there should be an ordered sequence of multiple prompts, rather than only being able to enter one.
4. Shared context across the entire workflow
All nodes in the entire workflow share the same context;
The output of the previous node can serve as the input basis for the next node;
I do not need to manually copy and paste intermediate results between nodes.
5. Shared workspace across the entire workflow
All nodes share the same workspace / file system / project directory;
Files, code, and artifacts produced by previous nodes can be directly accessed and modified by subsequent nodes;
Similar to "a pipeline continuously working on the same project directory."
Expected Effect
After configuring a workflow once, each time I handle the same type of task in the future, I only need to:
Select a saved workflow;
Provide the initial input for this task (or let the first node receive it);
Run it with one click, and it will automatically execute in node order, sharing context and workspace throughout the entire process.
This can completely eliminate the cumbersome operation of repeatedly configuring prompts, models, and skills in each round.
Why I Hope the Project Adopts This
This kind of need — "fixed process + multiple rounds of dialogue + fixed configuration" — is very common in scenarios such as office automation, batch content processing, and code/document pipelines;
Currently, most tools only support "single-round dialogue" or "manual step-by-step operation," lacking the ability to turn multiple rounds of dialogue into reusable workflows;
If this project can support this feature, it will greatly improve the efficiency of handling high-frequency repetitive tasks and can also attract more users with similar needs.
Thank you to the maintainers for your efforts, and I look forward to your reply!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
背景与场景
在日常办公中,我经常需要重复处理同一类工作任务。这类任务有一个共同特征:
这种重复性配置极其繁琐,效率很低,也容易出错(比如某一轮忘记切换模型或漏挂技能)。
我的需求
我希望该项目能够支持搭建一整套可复用的工作流(Workflow),具体诉求如下:
1. 多节点工作流编排
2. 每个节点可独立配置
每个节点应当可以独立设置以下内容:
3. 每个节点支持多条用户提示
这一点对我来说很关键:有时候在同一个节点(同一轮)内,我需要按顺序发送多条用户提示,例如:
也就是说,一个节点内部应该是有序的多条 prompt 序列,而不是只能填一条。
4. 全流程共享上下文
5. 全流程共享工作区
期望的效果
配置一次工作流后,之后每次处理同类任务时,只需:
这样可以彻底免去每轮重复配置提示词、模型、技能的繁琐操作。
为什么希望项目采纳
感谢维护者的付出,期待回复!
Background and Scenario
In my daily office work, I often need to repeatedly handle the same type of task. These tasks share a common characteristic:
This repetitive configuration is extremely cumbersome, highly inefficient, and prone to errors (for example, forgetting to switch models or missing a skill in one of the rounds).
My Needs
I hope the project can support building a complete set of reusable workflows, with the following specific requirements:
1. Multi-node workflow orchestration
2. Each node can be configured independently
Each node should be able to independently set the following:
3. Each node supports multiple user prompts
This point is crucial to me: sometimes within the same node (the same round), I need to send multiple user prompts in sequence, for example:
In other words, within a node there should be an ordered sequence of multiple prompts, rather than only being able to enter one.
4. Shared context across the entire workflow
5. Shared workspace across the entire workflow
Expected Effect
After configuring a workflow once, each time I handle the same type of task in the future, I only need to:
This can completely eliminate the cumbersome operation of repeatedly configuring prompts, models, and skills in each round.
Why I Hope the Project Adopts This
Thank you to the maintainers for your efforts, and I look forward to your reply!
All reactions