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

​
Parent and child roles

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:
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