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. Agent Sessions
Elzi feature guide

Agent sessions

Chat with an agent inside a project folder, or set one up to work on a schedule.

An agent session is a chat with Elzi inside a project folder. You say what you need, and the agent plans, works with the tools you've allowed and asks when it needs you. It only works inside that folder. One model, node or strategy answers the chat, and you can change it at any time. When you want an agent that keeps working without you starting each turn, Agent Work runs it on a schedule.

Chat sessions

  1. Under Projects, pick a folder and choose "New session here". Any folder becomes a project the moment a session runs there.
  2. Pick the model with "Run this chat on": a node, a strategy, or "Other models and providers…".
  3. Type what you need in plain words and press Enter.

Sessions are listed under the folder they ran in. The sidebar shows which ones are active now and which are waiting for your answer. You can fork a session to try another direction, or delete it. When an agent hands part of the job to delegates, they share the chat's nodes. Skills, MCPs and Memories extend what the agent knows and which tools it has.

Agent Work: agents on a schedule

Agent Work is for an agent that keeps a desk: it wakes on a schedule, checks what's new, investigates, keeps a ledger and a scratchpad, drafts, has its drafts reviewed and asks you only when a decision is yours. Each wake-up is a tick. An agent is a folder with an agent.yaml file.

Choose "New agent" and fill in its purpose and folder, a charter (who it speaks as, what it may touch, what it must ask about first), a schedule (how often it wakes, on which days and hours), its tools and access, a guard that runs first and can hold a tick, specialist workers and review lenses that each attack every draft. "Open desk" shows what needs you, the current tick's lanes, a ledger and the tick history. "Remove from roster" keeps the folder.

Good to know

Agent Work and the Benchmark view appear in the default local edition of the app.

How it differs from builds 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

Software build sessionsOne brief becomes a planned, multi-agent build across your nodes.Benchmark runsGive models the same frozen task and compare their scores before you trust one.Nodes and strategiesThe models Elzi hands work to, and the rules for which one does what.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