ULUAI agents beehive

Describe your project. Get an AI team that builds it.

ULU is a beehive of AI agents: a desktop app for Claude Code. You explain what you want in plain words. Kukulu, the builder bee, turns it into a team of AI agents and shows you every step while they work.

ULU 0.3.4 is out for macOS. Your first project is free.

Install ULU Watch the video

Install ULU

For macOS 12 or later, on Apple Silicon and Intel. Signed and notarized by Apple.

With Homebrew recommended

One command installs ULU and everything its teams need: git, the GitHub CLI, Node.js, Claude Code and Ollama.

brew install --cask endorphin-ai/tap/ulu

No Homebrew yet? Get it at brew.sh first.

Download

Unzip it and move ULU to Applications. ULU's Tools then installs the rest with one button, Install everything.

Download ULU for Mac 22 MB

  1. Sign in to Claude Code. Open Terminal, run claude once and sign in.
  2. Start a project. Open ULU, press New project and describe what you want to build.
  3. Pick a team. Take one of the ten ready teams, or let Kukulu design one for you.
  4. Give it a task. Watch the hive build it, check the work, and ship it.

Your first project is free. Every project after that takes a paid place on your key, and keeps it for good. A paid key also turns on ULU Remote, the hive on your phone. Prices

You also need your own Claude plan or API key: the agents run in Claude Code, and ULU shows what they cost while they work.

News

ULU 0.3.4: nine dead ends are fixed

A walk through what a person does in ULU found nine places where the window left you stuck, and each is fixed and tested in a real browser. A failed check now keeps its Write a bug button. Coverage refreshes after you save a check, and an old manual pass no longer counts as current. Finished tasks open their report and test run, Ask opens the commit or run it mentions, and a finished build offers Give the team a task. A failed report, diff or team list now has a Retry button.

Release notes

ULU 0.3.3: a smoother, more accessible window

Moving around ULU now shows where you are: tabs slide sideways, a new area fades in, and a project slides in and back out (all off when your Mac asks for reduced motion). Tabs work from the keyboard with the arrow keys, buttons are larger on touch screens, focus is easier to see, there is a skip link for keyboard users, and high-contrast mode keeps its borders.

Release notes

ULU 0.3.2: seven more fixes

An audit found seven bugs, now fixed and covered by tests. The most important: building or applying a change can no longer delete files outside your project when a project's .squad folder is a link, a failed Apply puts your instructions and design back, and ULU no longer replaces a settings file it cannot read with empty settings, which could lose your keys and project list.

Release notes

ULU 0.3.1: 35 fixes

A round of fixes after a full bug hunt, each with a test. The most important: ULU Remote is safer (a recorded command can no longer be replayed, a Keychain hiccup no longer orphans your phones, and the relay re-checks that your key is still paid), the usage-limit resume gives up cleanly and follows its switch, notifications reach you for every project, and updates no longer lose a found update or get blocked by a leftover Homebrew folder.

Release notes

ULU 0.3.0: your Claude limit no longer stops the work

When your Claude plan's usage limit is reached, the task now pauses instead of failing. ULU shows when the limit resets, keeps your Mac awake, and continues the task by itself a minute after the reset, in the same session, so the team remembers what it was doing. You get a notification when it pauses and when the team is working again, on your Mac and on your phone.

Release notes

ULU 0.2.0: notifications and ULU Remote

Leave your desk while the hive works. ULU now tells you what happens, on your Mac and on your phone.

  • Mac notifications when a task is done (with its cost and time), when the team needs you, when a team is built and when Kukulu answers.
  • ULU Remote (paid): watch the hive from your phone, answer the team's questions, approve a design and stop a task, from anywhere. Nothing to install from a store: pair your phone with a QR code from the Remote button in ULU. On iPhone, add it to your Home Screen to get notifications.
  • Everything between your Mac and your phone is encrypted end to end.

Release notes

ULU 0.1.0: the first release

ULU is out for macOS. Describe your project and get an AI team that builds it, with every step, its time and its cost in view.

  • Ten ready teams, each with a product manager, designer, architect, two developers, QA, security, DevOps and an end-to-end test healer, working through one proven flow.
  • Phone preview for Expo apps: in a phone on screen, on your own phone with a QR code, or in the iPhone simulator.
  • Ask, Git, Test and Mockups: ask questions about your code, review changes and merge pull requests with one button, check the app by hand and see test coverage.
  • Ship to Render and connect a domain through Cloudflare. Your keys stay in the macOS Keychain.
  • Setup in one click: Install everything puts git, the GitHub CLI, Node.js, Claude Code and Ollama on your Mac. Update Claude Code runs claude update and shows any error.
  • Safe updates: every update is signed and checked, and ULU goes back to the version you had if a new one does not start.

Release notes

Ten ready teams, one proven flow

Every team plans, designs, builds, reviews, tests, secures and deploys the same way, and stops for your approval on the design and the release. Only the stack changes.

Meet ULU on video

Watch Kukulu take a project described in plain words and turn it into a team of AI agents, then follow the bees while they work.

Play the video: Meet ULU, a beehive of AI agents for Claude Code

Watch the hive work

A build is usually a wall of log lines. In ULU every agent is a bee in its own cell. When El Capitan hands out work, a gold pulse travels from cell to cell, and the bee that receives it starts buzzing.

  1. El Capitan reads the request and hands it out.
  2. PM writes down what to build.
  3. Tech Lead decides how to build it.
  4. Dev writes the code.
  5. QE checks that it works.

From an idea to a working team in four steps

  1. One bee

    Define your project

    Tell Kukulu what you want to build, in your own words. It writes a project brief, asks only about what is missing, and three reviewers add the questions you did not think of.

  2. A bee beside three coloured blocks

    Generate the agents

    ULU designs the team: who does what, with which skills, in which order. You see it as a honeycomb, change what you like, and approve it.

  3. Four bees flying together

    Build the team

    Click Build. Every step shows its time and cost while it runs. Stop at any point and continue later, even days later.

  4. Three bees in a glowing honeycomb

    Your AI team is ready

    The team lives in your project folder and works inside Claude Code. Ask for a health report, or describe a change, whenever you need one.

Every bee shows what its agent is doing

You do not read logs to know how things are going. You look at the bees.

You always know the time, the cost and the context

AI agents spend real money and real minutes. ULU measures every stage, every build step and every agent, and shows it while it happens.

Cost
In dollars, per step and in total.
Time
Running time now, total when finished.
Context
How full each agent's memory is, before it becomes a problem.
Work
Files written, tools used, agents started.
A build in progress. Example figures.
  1. Prepare the project4s$0.02
  2. Fill skills 6 agents, 7 files6m 12s$3.41
  3. Customize agents 6 agents, 6 files3m 40s$1.18
  4. Write the workflow0m 48s$0.21
  5. Write signal routing
  6. Verify no stubs remain
  7. Generate CLAUDE.md

So far10m 44s$4.82

Context of the main agent38%

Made for people who have the idea, not the terminal

If you know what you want to build but not how to set up AI agents, ULU asks you the right questions and does the setup. You approve a picture of the team, not a folder of configuration files.

If you already work with Claude Code, you get the same engine with a window on top: every step measured, a visual view of the team, and reports on its health.