Notes from the work

One email when a tutorial or migration write-up goes live. Nothing else, and an unsubscribe link in every email.

LeanZero

Two people in Romania doing Atlassian migrations, Forge apps and practical AI work for teams that would rather talk to the person doing the job. Most of what we learn ends up on this site.

Services

  • Atlassian migrations
  • Atlassian FastShift
  • Atlassian maintenance
  • Forge app development
  • AI development consultation

Topics

  • Jira
  • Jira Service Management
  • Confluence
  • Bitbucket
  • Atlassian Forge
  • Cloud Migration
  • Local AI
  • AI Coding
  • Certifications
  • Atlassian Team
  • All topics

Company

  • Blog
  • Tutorials
  • Contact

Community

  • Join Discord
  • Support this site

© 2026 LeanZero. All rights reserved.

Privacy policyTerms of service24/7 SupportTrust centerSecurityDPALegal notice
  1. Home
  2. Portfolio
  3. Elzi
  4. Features
  5. Software Build Sessions
Elzi feature guide

Software build sessions

One brief becomes a planned, multi-agent build across your nodes.

A software build session turns one message into a whole build. Instead of one model answering turn by turn, Elzi plans the work, splits it into tasks, hands them to several nodes at once and writes the files into your project folder. The app calls these swarm builds. You start one by choosing "Elzi · Build" as the chat's model and describing what you want built.

Starting a build

  1. Open a chat in the project folder the build should write to.
  2. In the model picker choose "Elzi · Build" (plan and fan out a build across the pool).
  3. Describe what you want built. The build runs on your swarm pool, or on a strategy you marked "Use for swarm builds".

What happens during a build

  1. Open: the brief is sliced into parts.
  2. Ask: the swarm asks you once, up front, about decisions only you can make.
  3. Research: one read-only lane per part, in parallel across your nodes.
  4. Plan: tasks, the files each task owns and the order they depend on.
  5. Build: large tasks are split into smaller ones, and the nodes write the code.
  6. Integrate and repair: the app is started, probed, and what the checks find gets fixed.

A run panel shows each phase live. Every phase is also written to an event log in the project.

Roles and nodes

A strategy assigns nodes to roles: Planning (reading the request, asking questions, researching and writing the plan), Build (writing the code for each task), Backend, Frontend, Testing (running and checking the result, and fixing what the check finds) and Chat. Each node has a weight; a higher weight gets a bigger share of the tasks. LM Studio models loaded on your Macs can join a build too.

Limits

  • OpenAI-compatible endpoints you add yourself are chat only for now; swarm builds can't use them yet.
  • Each Mac's MLX engine serves one model at a time, so a build reaches a Mac's local model only through that Mac's single engine.

How it differs from agent sessions and benchmarks

Agent sessionSoftware buildBenchmark run
You start it withA chat in a project folderA chat on "Elzi · Build"The Benchmark view
Who drivesYou, turn by turn (or a schedule, for Agent Work)The swarm, from one briefA frozen task, the same for every model
ModelsOne model or node answersMany nodes share the workThe model or nodes you want to measure
What you getThe conversation and the files it changedA planned, multi-agent build written into the projectA score with its evidence, which you can compare
The three kinds of work in Elzi. Each has its own guide: agent sessions, software builds and benchmarks.

Related guides

Nodes and strategiesThe models Elzi hands work to, and the rules for which one does what.Agent sessionsChat with an agent inside a project folder, or set one up to work on a schedule.Benchmark runsGive models the same frozen task and compare their scores before you trust one.ProvidersWhere models come from: the MLX engine on your Macs, or a cloud provider with your key.

Facts on this page were checked against our own test records on 6 November 2026.

Using Elzi

  • What Elzi is
  • Agent sessions
  • Software build sessions
  • Benchmark runs
  • Nodes and strategies
  • Providers

The MLX engine

  • The LeanZero MLX engine
  • Serving a model on one Mac
  • Distributed serving across two Macs
  • N-gram tables and prompt lookup
  • Speed: measured numbers
  • Memory lock

Media and devices

  • Images
  • Voices
  • LeanZero Link

Elzi

  • All feature guides
  • Download and user manual