An AI assistant for engineering managers
An engineering manager’s work is in Slack threads, reviews, incidents and plans. Tecla keeps those tasks in one list. You click Run, and Tecla does the work.
By @miguelaeh_ ·
A coding agent helps the engineer who writes the code. An engineering manager spends most of the day on other work: answers to other teams, reviews, incidents and plans. That work arrives in Slack, in GitHub notifications, in alerts and in meetings, and no tool collects it in one place.
For example, imagine that Lena from sales asks in Slack on Wednesday when the export fix will ship, because a customer is waiting for it. You know that the answer is in a pull request and in an issue. You are in a planning meeting, so you plan to look later. On Thursday Lena asks again, and now the customer is angry with her.
Lena’s question was not hard. It was lost because it arrived between twenty other messages. This post explains what Tecla does about that.
The short answer
Tecla is a proactive AI assistant for work. It finds and tracks your tasks in Slack, your email, your meetings, GitHub, your issue tracker, etc. When you open Tecla, the list of your tasks is already there, with all the context. You click Run on the ones you want. With other agents, you face an empty prompt. For an engineering manager, the tasks are the work around the code: the answers, the updates, the plans and the first look at a problem.
A manager’s tasks arrive in four places
The first place is a thread, like Lena’s question in Slack. The second is a notification: somebody asks you for a review, or a check fails on the main branch. The third is an alert, for example when a new error starts after a deploy and somebody has to find which change caused it.
The fourth place is a meeting, and it is the easiest one to miss, because a meeting creates work that nobody writes down. If the team agrees on Tuesday to move the launch to the 24th, then six issues and one plan still have the old date, and somebody has to change them.
Tecla makes a task from each one, and does the work when you run it
When Lena writes her question, Tecla adds the task “Tell Lena when the export fix ships” to your list. When you run it, Tecla reads the pull request and the issue, and it drafts the answer in the thread: the fix is in review and will ship on Friday. You read the draft and approve it. The table shows that task and four others.
| Where it came from | The task | What Tecla does |
|---|---|---|
| A question in Slack | Tell Lena when the export fix ships | Reads the pull request and the issue, and drafts the answer in the thread |
| A decision in a meeting | Move the launch to the 24th | Moves the due dates in Linear, updates the plan in Notion, and drafts the note to the team |
| An alert in Sentry | Find what broke checkout after the deploy | Finds the change behind the error and opens an issue with the cause |
| A notification from GitHub | Review the pull request from the new engineer | Reads the change and the issue behind it, and prepares its notes for your review |
| Every Monday | Write the engineering update | Lists what shipped and what is blocked, and drafts the message to the company |
You can see two of these step by step: a Slack conversation to done and the weekly report.
Tecla works in your tools, and sees what your account sees
You connect GitHub or GitLab, Linear or Jira, Sentry and Slack with your own accounts. Tecla can then see what each of your accounts can see, and no more. It does the work on a cloud computer and browser of its own, so nothing runs on your laptop.
A person still reviews the code and approves each message
Each task shows its plan before it starts, so you know what Tecla will change in Linear or in GitHub before it does it. When a task needs code, Tecla opens a pull request, and a person on your team reviews and merges it. Tecla doesn’t merge. A message or a review comment in your name waits for your approval, and you can change the text first.
Questions
- How is Tecla different from a coding agent?
- A coding agent does a coding task that you describe. Tecla finds the tasks, and most of a manager’s tasks are not code: answers, updates, plans, the first look at an incident. When a task does need code, Tecla can open a pull request.
- Does Tecla merge pull requests?
- No. It opens them. Your team reviews and merges them as it does with any other.
- Does Tecla post in Slack or comment on a review without asking me?
- No. A message or an email in your name waits for your approval before it goes out. You can edit it first.
- Does Tecla need access to our code?
- Only if you connect GitHub or GitLab. It then sees what your own account can see.
- What does Tecla cost?
- It is free to start, with no card needed. Then it costs $47 a month, or you buy credit packs from $8. See the pricing.
