A single terminal that puts
dozens of agents
to work for you
It reads and edits your files, runs your commands and takes the task to the end — with the provider you already use, local models included. Your session, your data and your key stay on your machine.
curl -fsSL https://aluy.dev/install.sh | bash
Aluy renders best in WezTerm: the icons and borders come out visually more refined. It works the same in other terminals, just plainer.
A real cycle: from broken test to green.
What you'll put it to work on.
Tasks
Bulk renames, file wrangling, reports, data cleanup — describe it, it does it in your shell.
Processes · robotic automation
Wires steps and tools into one process. End to end, instead of brittle scripts that break.
Testing
Writes, runs and fixes until it passes. Reads the error, corrects it, runs again.
Development
Reads the project, proposes the change, edits files and runs the build. You review and approve.
Not a chat about your code. A team that acts.
Kick it off and go do something else
Works in cycles on its own until the task is done — with a handbrake. Hard caps on time and steps, plus automatic stops.
A fleet of specialists
Each subagent is a profile (.md) with a focus — one for tests, one for review, one for docs. Delegate and they work in parallel.
Watch the fleet collaborate live
Rooms put several agents talking to each other about the problem — debating, splitting the work. You follow in real time and jump in whenever.
Plug in what you already use
Through MCP — the open standard for connecting tools — the agent talks to databases, APIs and services. It can actually use them, not just talk about them.
Local where it matters, connected only where it has to be.
The session, history, project files, memory and your provider key. The agent runs locally, behind the permission gate.
The model call goes straight to the provider you configured, with your key. No middleman and no metering.
Three optional add-ons, running on your own machine.
Memory that outlives the session: the agent keeps facts and preferences and recalls them in the next conversation.
Condenses the conversation as it grows, so a long session keeps fitting in the model’s window.
Runs small models on your machine for Aluy’s own internal work — those calls never leave it.
All three are optional and come with turbo mode. Without them Aluy works the same: memory stays in the project’s ALUY.md, written by you or by /init.