Crush AI coding agent setup for small business teams
Crush is an open source terminal AI coding agent from Charm. See what businesses use it for and how MILabs sets it up.
Updated 2026-04-14
What Crush is
Crush is an AI coding agent that runs in a terminal window. Charm publishes it as open source software, so the code is public and a team can read it before adopting it. A developer starts Crush inside a project folder and asks it to explain code, track down a fault or make a change. The agent works on the files in that folder, and the developer reviews what it produces before that work is used. Crush supports more than one model provider, so a team can choose the underlying model and change that choice through its configuration. For a business, the tool suits the people who already write and maintain its software, because much of that work stays inside the terminal and the repositories the team already uses. The developer and the team remain responsible for reviewing every change before it reaches customers. A team that already knows its codebase tends to get the most from it, since it can judge suggestions quickly.
Crush in plain language
Coding agents are AI programs that read a software project, reason about its files and propose or make changes on a person's instruction. Rather than answering questions in a chat window alone, they work alongside the code itself, opening files, following references between them and suggesting edits. Many tools in this group run from the command line, close to the version control, test commands and build scripts developers already use.
For a business, the useful question is where the agent's output ends up. A change proposed by an agent still has to be read, run and merged by someone who understands the system. Good results depend on clear instructions, a codebase with reasonable structure and tests that show when something has broken. Without those, the agent can produce plausible work that takes longer to check than it saved.
Model choice matters as well. A coding agent sends the material it reads to whichever model it is connected to, so the provider, its terms and the scope of the files shared all become part of the decision.
What businesses use it for
- Explaining code that a small team has inherited.
- Tracing the cause of a fault in an internal web application.
- Drafting tests and small changes for an existing project.
- Building scripts that move data between files in a project folder.
- Documenting project structure so new developers can get started quickly.
Who it suits
- Software teams whose developer already works comfortably in a terminal
- Companies that maintain their own internal tools or websites
- Owners who want code changed and reviewed under clear permissions
How MILabs sets it up
MILabs begins with the owner or lead developer. Together you choose which model provider the business will use and which plan or account sits behind it, so costs and data handling are agreed before anything is installed. We then install Crush on the machines that need it and point it at the repositories, folders and documentation the team already works from. Where the business uses Git hosting, issue tracking or a shared drive, we connect those so the agent can read the context it needs. We set permissions for each person, covering which folders the agent may read or change and which actions need a person's approval. Finally, we agree who looks after the setup, who approves model or configuration changes and who reviews the output.
Builds it fits
Industries it fits
Crush in practice
Inside a business, this kind of tool usually begins with a developer pointing the agent at one repository and a specific task. A typical session might involve reading an unfamiliar module, asking how a function is called across the project or drafting a unit test for a route that has none. The developer keeps the work scoped to the folder, so the agent only sees what the team has chosen to expose.
The work tends to arrive in small pieces. A bug report is narrowed to a file, the agent suggests a change, and the developer runs the existing test suite and reads the diff before committing. Changes to configuration, documentation or internal scripts follow the same rhythm. Because the agent works in the terminal, its edits sit in the same version history as everything else, so review becomes a normal part of the team's routine.
Over time, teams often build habits around it. These include a shared notes file describing project conventions, agreed prompts for common tasks and a standing rule that no agent output merges without a second reader. Those habits are what separate a useful setup from one that quietly accumulates code nobody fully understands.
Frequently asked questions
- What does a Crush setup need from me?
- A Crush setup needs a named owner or lead developer, a decision on which model provider and account will be used, and access to the repositories and folders the agent should work with. It also needs a short list of who may approve changes and who maintains the configuration over time. MILabs gathers these details at the start, and the business supplies the accounts and people while MILabs handles installation.
- What does Crush not do?
- Crush is a coding agent for work inside a project, so it does not manage office tasks such as invoicing, rostering or customer email. It does not decide what reaches production, because a developer reviews and accepts its output. It cannot guarantee correct code, and it works best alongside testing, code review and the judgement of the people who own the software.
- Is Crush suitable for a small business?
- Yes, when the business has at least one person who writes or maintains software and works comfortably in a terminal. Crush is less useful for a business without code of its own, because most of its value comes from working on a project's files. A small team can use it for everyday changes and reviews, provided someone is responsible for checking the output.
- Is Crush safe to use with customer data?
- Yes, with care, because safety depends on the model provider, the account terms and how the business configures access. Customer records should stay out of project folders the agent can read unless the business has approved that provider for that data. MILabs reviews the folders and permissions with the owner during setup, and recommends that personal and payment data stay out of the working directory.
- What are the limits of Crush?
- Crush works within the context it can read, so large or poorly documented codebases may produce answers that miss important detail. Its results depend on the model it is connected to, and those models can make mistakes. It works in the terminal, so teams that rely on visual design tools or office software will need other tools for that work. Its output is a draft from a capable assistant, reviewed before use.
