MILabs
Tools

Zed code editor for business scripts and templates

Zed code editor set up for small and mid-sized businesses by MILabs, with AI help for changes to scripts and templates.

Updated 2026-07-17

What Zed is

Zed is a code editor made by Zed Industries, built for fast editing of source files. It supports shared editing, so two people can work in the same project at the same time, and it includes an AI assistant panel that can read the code in a project and suggest changes. A business does not need to be a software company to find it useful. Owners and team leads often have a small amount of code behind their tools: a script that moves data between a spreadsheet and a booking system, a template that formats invoices, or a configuration file for an automation. Zed gives the person who maintains that code a fast and familiar place to read and change it. Because the editor runs on the developer's own machine, the business keeps its code under its own control while using AI help to draft and review changes. Zed is one choice among several editors, and it suits work that already lives in code, whereas spreadsheets, forms and no-code tools tend to call for a different kind of tool.

Zed Industries: official site

Zed in plain language

A code editor is the application a person uses to open, read and change the text that makes software work. Unlike a word processor, it is built around files made of instructions, so it highlights syntax, follows references between files and keeps indentation and structure consistent. Many editors also run checks in the background, flagging likely mistakes as someone types.

Code lives in plain text files, usually grouped into a folder or a repository, which is a shared store that records every change made to the project over time. An editor opens that folder and lets the person working on it move between files quickly. Several people can work in the same project, and the repository shows who changed what and when, so each person's edits stay traceable to them.

AI assistants have become a common addition to editors. In these tools, a model reads the files open in a project and proposes a change, which the person then accepts, edits or discards. The answer depends on the context the model receives and on the provider behind the feature, so an owner should know which files leave the machine and which stay local. A person reviews each suggestion before it is accepted.

What businesses use it for

  • Maintaining small scripts that move data between the systems the business already uses
  • Reviewing and changing configuration files for workflow tools
  • Editing templates for quotes, invoices and reports
  • Working alongside an outside developer on a shared project
  • Drafting and checking code that an AI assistant has suggested before it goes live
  • Reading an existing codebase when a business takes over a product

Who it suits

  • Owners whose business runs on a few custom scripts or templates
  • Small teams that already keep their code in a shared repository
  • Businesses with an outside developer who needs a fast editor on site

How MILabs sets it up

MILabs sets up Zed with the business owner or team lead first. The opening conversation covers which projects the editor will open, who will use it, which plan or account type suits the team, and whether AI features should be switched on. MILabs then installs Zed on the machines that need it and connects it to the code repositories and project folders the business already keeps. Permissions come next, so each person sees only what their role needs in shared projects and in any AI provider account. Last, the owner and MILabs agree who looks after the setup, who updates the editor and who answers when something breaks. The business keeps ownership of its code throughout.

Builds it fits

Industries it fits

Zed in practice

In a typical business using this kind of editor, the work starts as a request from someone who runs the operation rather than from a developer. A bookkeeper might need a field renamed in an export, or a service manager might want a line added to a quote template. The request is written down, then the maintainer opens the relevant file, makes the change on a separate branch of the repository, and asks an AI assistant to explain what the existing code does before editing it.

Review is where the arrangement pays off. The change is compared against the previous version, usually line by line, and the reviewer reads the difference rather than trusting the summary the assistant produced. Where a script touches live data, the change first runs against a copy, such as a test folder or a sample export, so that a mistake appears before any customer or staff member sees it.

Over time the business builds a small habit around its code. Each change gets a short note saying what it does and why, and the owner knows which pieces depend on which software. An outside developer then inherits a repository that already explains itself, so the first conversation is about priorities.

good questions, straight answers

Frequently asked questions

What is Zed?
Zed is a code editor from Zed Industries, used to read, write and review source code. It supports editing by more than one person in the same project, and includes an AI assistant panel that can suggest changes to the code it can see. For a business, it is where the person maintaining scripts, templates or integrations does the work. It is a developer tool rather than a general office application.
How does MILabs set up Zed?
MILabs starts with a conversation with the owner or team lead about which projects Zed will open and who will use it. It then installs the editor, connects it to the repositories and folders the business already has, and sets who can see shared projects and AI settings. The owner and MILabs also agree who keeps the setup up to date and who answers questions. The business keeps ownership of its code throughout.
Where does Zed store data?
The editor works with project files where they already live, on the machine or in the repository the team chooses. Data sent to an AI provider depends on which AI features are switched on and which provider the account uses, so those settings are agreed with the owner during setup. MILabs does not promise one storage location for every feature, so the settings chosen for each feature are the ones that count.
When is Zed the wrong choice?
Zed is the wrong choice when the work lives mostly in spreadsheets, shared inboxes or no-code tools, because there is no code to change. It is a poor fit for a team with no one who reads or maintains code. In those cases a workflow tool or a template inside existing software is simpler. MILabs will say so in the first conversation rather than set up an editor nobody will use.
Can my team use Zed without training?
Team members who already use a code editor will find the basics familiar. Anyone without coding experience is best placed reading the code rather than editing it. In practice the owner keeps a named developer for changes, and the handover note explains which files are safe for the rest of the team to read and which should be left alone.
let's make something happen

Workflow automation: how we can help

Choose how you want to work on this with MILabs. Both options start with an enquiry.

Discovery is free, no obligation from the first chat.

Let us build it for you

We build it and look after it.

Build it yourself, we'll help

You build it with our direction, teaching and a weekly check-in.