Sequential Execution
Stages execute in a defined order rather than running as disconnected tasks.
Agent Flows connect your recruited specialists into a reusable sequential workflow. Each stage contributes its own specialty before AgentForge creates one coordinated final result.
Agent Flows are designed for work that benefits from a specific order of specialist execution.
Instead of asking several agents to independently answer the same mission, each stage receives useful findings produced before it. This lets research, development, content, QA, prompt design, automation, visual creation, security review and mission coordination build on one another in a deliberate order.
Example: Lyra researches the problem, Nexus turns findings into a technical solution, Vex validates quality, and Rune converts the final requirements into a production-ready prompt. Any recruited AgentForge specialists can be arranged into a Flow.
Create a reusable AgentForge workflow and define the purpose of the process you want to repeat.
Assign recruited specialists to ordered stages and optionally add stage-specific instructions.
AgentForge evaluates each stage independently and determines whether it should run in Standard or Research mode.
Completed specialist output becomes context for the next stage so the workflow builds progressively.
After all specialist stages finish, AgentForge combines their work into one polished final deliverable.
Stages execute in a defined order rather than running as disconnected tasks.
Each stage receives its own execution mode and credit cost before the mission begins.
Completed stage outputs are stored so recoverable failures do not require every specialist to run again.
Started missions preserve the execution configuration they launched with so later edits do not silently change historical work.
AgentForge evaluates every workflow stage independently. Standard stages cost 10 credits while stages that require research cost 30 credits.
AgentForge stores the state of each workflow stage. If a later stage fails before billing completes, already-completed stages can be loaded from saved execution state instead of calling the AI again.
Once execution begins, AgentForge preserves the stage configuration used by that mission. Editing the original saved Flow later should affect future missions rather than silently changing the meaning or pricing of an execution already in progress.
The flow must belong to the authenticated user.
The saved flow must still be active before a new execution begins.
Every participating specialist must still be recruited and usable under the current plan.
AgentForge calculates the complete flow cost before claiming the mission.
Completed specialist stages can be reused during a safe retry.
Generated final results are preserved during recoverable billing failures.
Existing credit transactions prevent duplicate charging.
Learn how AgentForge tracks balances, mission charges, execution history and plan allowances.