Child forks

A child fork is a focused run with its own context, tools and runtime budget. Veryfront Agent can create one when a subtask benefits from isolation. You can request delegation or let Agent decide when it 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 its result to the main Agent.

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

Ask Agent to split independent parts of a task:

text
Split this into a plan pass and a review pass before editing files.
text
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. Their results still need review, tests and any required deployment checks.

Next

GoalPage
Add reusable workflowsSkills
Set project rulesProject instructions