Back to NautLoop

NautLoop / Guide 2 of 3 / 2 min read

How does NautLoop work?

Dispatch work to specialists and bring their results together.

The reason

An agent needs somewhere to work, and a way to return the result.

Parallel tasks should not all share the same files, credentials and dependencies. Each assignment needs an execution boundary and a clear owner.

NautLoop builds on temporary GitVM environments. Work runs in a sandbox with a defined lifetime, then code and artifacts come back before that environment expires.

48Nauts / Product guides · In development

A shared task lifecycle

A lead breaks down the task and dispatches work to specialist agents. Each specialist executes in its own environment and returns a contribution.

The coordination layer moves the task through execution, synthesis and delivery. A useful handback must retain the relationship between the assignment and the returned result.

  1. 01Dispatch
  2. 02Isolated execution
  3. 03Synthesis
  4. 04Delivery

Optional memory

Engram can retain relevant knowledge across runs. Decide which knowledge should persist and which material belongs only to the current task.

Persistent knowledge and sandbox isolation are separate choices. Evaluate both against the task’s information boundaries.