Skip to content

Multi-Agent

A bigger task needs more than a longer prompt.

Give a connected goal to a coordinated workflow. Specialised roles investigate the project, prepare the approach, implement subtasks and check the result – without making you manage every handoff.

Multi-agent orchestration requires Ultra and available credit. Tool approvals and project quality checks still apply.

One goal. Separate responsibilities.

  1. Plan

    Turn project context into concrete subtasks.

  2. Implement

    Work through the agreed changes with the project tools.

  3. Verify

    Review the result and run relevant checks.

Capture of a real run showing its goal, subtasks, specialised roles and verification status.
A coordinated multi-agent run

How orchestration works

Specialist agents work on one shared task.

  1. 01

    Break the goal into subtasks

    The Planner investigates the goal and project context, identifies affected areas and creates concrete subtasks.

  2. 02

    Implement the changes

    The Implementer works through subtasks with the project tools. Results are collected within the same run.

  3. 03

    Review independently

    The Reviewer checks changes and relevant verification results. Open points return to implementation as follow-up tasks.

  4. 04

    Bring the result together

    Receive the changes, verification results and open points for the shared task. You decide what to accept.

Autonomy with boundaries

Keep the scope visible. Keep a cost limit.

  • Set the budget.

    The default run budget is €20. Use --max-cost to set a different total limit before starting.

  • Choose the mode explicitly.

    --mode plan prepares an artifact; --mode agent implements. --mode auto follows the current CLI mode.

  • Check the outcome.

    A completed run is not a correctness guarantee. Keep tests, human review and your release controls in place.

Start with a bounded task.

Run these slash commands inside a Lurus Code chat in your project. Choose a clear goal and review the plan before handing over a larger change.

Read the documentation
  1. Prepare a plan without source edits
    /orchestrate --mode plan "Add a settings page"
  2. Implement with a €20 run budget
    /orchestrate --mode agent --max-cost 20 "Add a settings page"

Your code stays yours.

Source code and request context are processed with Zero Data Retention. No use for model training. Providers and processing regions are disclosed transparently.

See privacy and processing details

A few things to know before you start.

Which plan includes the orchestrator?
Multi-agent orchestration requires Ultra and available credit. The run also has its own configurable cost limit.
Does Plan mode implement changes?
No. It investigates and creates a plan artifact. Starting implementation is a separate action; review the approach first.
Is a completed run ready to merge automatically?
No. Agents and checks can miss issues. Inspect the diff, verification results and remaining gaps before approving a change.

Multi-Agent

Give the next larger task a connected workflow.

Choose Ultra for multi-agent orchestration. Start with a well-defined task rather than handing over the entire project.

Multi-agent orchestration requires Ultra and available credit. Tool approvals and project quality checks still apply.

Want to start with your team? Talk to us.

A deliberate choice

Before your first prompt.

Interactive demo
Lurus Codeprivacy-demo · illustrative workspace

Demo session ready. Your model choice and data route are separate decisions.

Illustrative scenario. No real sign-in, security test or code transmission takes place.

Image preview