Skip to main content
Veryfront Agent can start a child fork when focused work needs its own context, tools, or runtime budget. A child fork is an isolated run created by the main Agent. It is not a separate product you manage. Most users do not need to request forks directly. Agent decides when a fork helps.

​
When Agent uses a fork

Task shapeWhy a fork helps
ResearchKeeps source gathering separate from the main answer.
PlanningLets a focused run draft a plan while the main Agent owns the conversation.
Large code changesGives implementation work a separate context and tool budget.
ReviewLets a review pass stay isolated from the builder’s working context.
Parallel workSplits independent subtasks without mixing files or findings.

​
Parent and child roles

RoleResponsibility
Main AgentOwns the user conversation, decides whether delegation helps, and gives the final answer.
Child forkHandles one scoped task with separate context, tools, and runtime budget.
The child returns a compact result. The main Agent remains responsible for the final response.

​
What a child receives

A child fork receives:
  • A scoped task from the main Agent.
  • Current project context when available.
  • Relevant skills.
  • A fresh tool set.
  • Its own model and step budget when the selected skill requires it.
It does not receive the full parent conversation history.

​
How to ask for delegated work

You can ask Agent to split work when the task has independent parts: 
Split this into a plan pass and a review pass before editing files.

Research the current implementation separately, then propose the smallest fix.
For short questions, small file reads, and short answers, stay in the main chat.

​
Limits

Child forks cannot start more child forks. Child forks do not replace review, tests, or deployment checks.

​
Next

GoalPage
Add reusable workflowsSkills
Set project rulesProject instructions