Echelar is a team of AI agents anyone on your team can call from Slack, GitHub, Linear, or Echelar's own app — or put on schedules as Automations. Every job ends the same way: a result a person approves.
Work starts wherever the signal already lives. The loop that follows is the same.
| Surface | What happens |
|---|---|
| Slack | Mention Echelar in an enrolled channel. It investigates or builds, and the result returns to the thread. |
| GitHub | Install the GitHub App. Echelar reviews pull requests after CI passes and answers when you mention it in a pull request thread. |
| Linear | Assign an issue to Echelar. A Session works it, and the pull request attaches back to the issue. |
| The Echelar app | Chat with it, watch live activity, and manage Automations. |
| Schedules | Recurring Automations on your schedule. When the work changes code, a pull request comes back. Nothing merges. |
Every job — a Slack mention, an assigned issue, a scheduled Automation — moves through the same four steps.
From Slack, GitHub, Linear, the Echelar app, or a schedule — work starts where the signal already lives.
In an isolated sandbox, grounded in how your repository actually works: its architecture, decisions, and conventions.
With the evidence attached — activity, changed files, checks, and artifacts your team can inspect.
A person reviews the result, decides what ships, and performs the merge.
There is no merge button. We didn't build one.
An Automation is a versioned definition of when work starts, where it may run, and what must come back to a person.
Describe one in plain English and Echelar drafts it. Every draft lands disabled until a person enables it.
Before you enable an Automation, we can dry-run it with you against a real recorded event and show exactly why it would or wouldn't fire. Once it is enabled, every fire writes an audit record with the prompt it sent.
Describe the recurring job in a Session. Echelar drafts the schedule, scope, checks, and Reviewer handoff, and the draft stays disabled until an authorized person enables it. On Monday at 08:00 the Automation starts and comes back as pull request #88, waiting for review.
Echelar keeps organization-scoped memory that is demoted automatically when the code it describes changes.
Repeated review corrections can become versioned Skill drafts — disabled, with the evidence cited — that a person reads and enables.
Enabled changes affect future Sessions only.
repo@7f31c2PR #842repo@81a0bcPR #901repo@8a44e1PR #918skill / v3Require a rollback path and verify schema compatibility before a billing migration returns for review.
enabled revision onlyBook an intro and we'll walk this loop on your code — where work starts, what comes back, and who approves it.