Efficient recurring tasks, clearer failures, and worker renames
This week made recurring tasks more efficient, made problems easier to see from your side, and made new workers steadier at getting started.
More efficient recurring tasks
Each run of a scheduled task now starts its own conversation instead of carrying every earlier run’s history. A task that has been running for months gives each run focused attention, and the 200th run is as efficient as the first, which means savings for you on long-running tasks.A clear notice when a connection stops working
When a connected app’s sign-in or key is no longer valid, the person talking to the worker is told plainly what failed and who can fix it. The connection’s owner is told what to do next.No more silence after a failed turn
When a worker can’t be reached or a turn fails, the person who wrote to it now hears that something went wrong. Before, they could get silence or a misleading “complete”.Renames reach Slack
Renaming a worker now updates the name of its installed Slack app within a couple of minutes, with no re-install. The worker introduces itself by its new name on its next turn.Fixes
- New workers more reliably go to work. Setup is steadier, so a newly created worker is more likely to come up and start working the first time.
Tasks launch, and webhooks that start work
Tasks are now the way work moves between workers and people, with a board in the web app to see where everything stands. Outside events can also start a worker’s work through a webhook.
Tasks you can hand off
A task records who asked, who holds it now, when it starts, when it’s due and a running log of what happened. Tasks move between workers and people, and each new entry wakes the other side. Your existing scheduled tasks now live on the same model.The tasks board
One place in the web app shows every task across your workers: scheduled, in progress and closed, what’s late, each task’s log, and actions on the tasks assigned to you or that you asked for.Tasks in the API and in workers’ skills
The same task operations are available through your own API key at /api/v1/tasks. Workers create, hand off, comment on, close and list tasks through built-in skills, with guidance on how to work a task.Webhooks that start a worker’s work
An outside event, such as a listing going down or a form being sent, can now start a worker’s work for one of your clients, with the result posted in that client’s channel. Set one up by asking your worker in Slack or from the Tasks page. The secret is sent to you privately, once. Several events can run side by side, and a reply that @mentions the worker in the thread within 7 days continues the run.Improvements
- Custom tool servers pick up new tools. Tools you add to your own MCP server after connecting can now be listed and called without reconnecting.
Fixes
- Scheduled tasks run once. Overlapping schedule checks could start the same task a second time a couple of minutes later. Each occurrence now runs once.
- Workers stay quiet when not addressed. In shared channels, a worker no longer posts “not able to pick this up” or “not set up for this channel” on messages that never mentioned it.
- A clear message for an expired Slack token. If the stored Slack token no longer works, creating a worker now tells you to paste a fresh token in Settings, instead of leaving a failed worker behind.
- Memory keeps saving after a wake. A timing problem could stop a worker’s memory changes from being saved after it woke up. That is fixed.
Hand work between workers, and safer key connections
Work can now be handed between workers and people as a task, and connecting or replacing an API key gives clearer, more accurate results.
Tasks as the unit of work
A task is a record of work that one worker or person hands to another, with a log of what was asked, done and decided. It survives restarts and shows who holds it now. Slack is one place a worker can report, not the only place the work lives. Tasks with no activity are archived after 30 days by default.Improvements
- Clearer feedback when a key is refused. The connection check now tells a key the vendor refused apart from an answer it couldn’t interpret, and the connection card keeps the result.
- Reconnecting a key app tests the new key. Reconnecting an expired key connection now checks the pasted key straight away, so a bad key is refused on the spot instead of showing Active and failing on the worker’s first call.
- An accurate message when you replace a key. After a successful swap, the sheet says “N agent(s) now use the new key” instead of “Nothing changed”.
- Only valid places to put a connection. A connection can no longer be placed on a worker-and-client pairing that has no running agent to use it. Those options are greyed out, with the reason.
Fixes
- Scheduled from a DM, answered in the DM. A job you schedule in a DM with a worker now sends each result back to you by DM. Before, the worker promised a DM and nothing arrived.
- Working keys are no longer refused over a “not allowed” answer. If an app’s test address says “not allowed here”, the key is saved as unconfirmed with the vendor’s message shown, instead of being refused. A working connection is never expired because one call was denied. A key the vendor actually rejects is still refused.
Workers that see whole messages, know your org, and adopt your skills
This week made workers more aware of the people and teams around them, and closed several gaps where a message could go unanswered.
Workers see the whole Slack message
Text, Block Kit blocks, attachments and files now reach the worker in full, no matter who posted them. A table someone pastes in is no longer dropped.Workers know your org chart
A worker knows who it reports to, who the other workers are and what each is responsible for. It can point people to the right colleague instead of taking on someone else’s job.Workers can adopt a skill you hand them
Give a worker a skill from another platform, such as a Claude skill, and it turns it into one of its own. It agrees naming and placement with its manager, sets up the connections it needs with a person, and offers to test it.The Ergoly expert can set up an org from your skills
Hand it your skills and it proposes a set of workers. It creates them once you approve, and gives each its skills. It also suggests the right channel for the work, and opens a new private one when none fits.Guides on how AI and human teams work
Every worker, and anyone configuring one, can open Ergoly’s principles on when to bring in a teammate, when a worker should become a team, and who approves what.Workers can turn themselves back up
A worker you asked to go quiet in a room can now be asked to start answering again, and does so itself, without anyone going to the control panel.Improvements
- A cleaner Worker page. The worker’s profile now sits in the page header, and the overview is four editable, properly rendered sections. Use the pencil to edit one in place.
- New workers start on the latest model. Newly created workers default to Claude Sonnet 5.5.
Fixes
- No more lost messages while a worker wakes. A message could be dropped if the worker was put to sleep at the exact moment it arrived. The turn now runs.
- No more unanswered messages when a conversation couldn’t be created. If a brief rate limit or timeout stopped a new thread’s conversation from being created, the message went unanswered. The platform now waits and tries again, so people still get a reply.
- Slack reads work again. Requests to read a thread, channel history or look up a person were failing quietly, and the worker carried on without that context.
- Clearer “unverified” key connections. Creating a key connection now says why it came back unverified, so it is no longer mistaken for a rejected key.
- Friendlier missing pages. A web address with no page now sends visitors to the home page instead of a generic error.
Vendors on your org chart, and task runs that settle cleanly
A smaller week: external companies can now appear on your org chart, and a task that fails at startup no longer gets stuck.
Vendors on the org chart
External companies can now be added to the Company org chart alongside your workers and people. Each vendor carries a logo, a website, a short description, a lead and a list of members, and can be shown or hidden per operator.Improvements
- Ongoing security hardening. We shipped a round of security fixes and hardening measures.
Fixes
- Stuck task runs. A task that failed before it could start used to sit in a pending state indefinitely. It now settles as failed, posts a notice in the run’s thread and clears.
Artifacts, approvals, and workers that manage their own tools
Four new capabilities change how workers interact with people, what they’re permitted to do, and how they connect to outside tools — plus a new way to publish rich, shareable pages straight from a conversation.
Artifacts
Workers can now publish self-contained pages that live in the control panel at a stable URL. Each page is private to your organization by default, or shareable by public link. Ask your worker for a report, a dashboard, a chart — anything you’d want to pass around as a link — and it handles the rest.Approval flows
Ask your worker to “get approval before” doing something and it posts Approve and Reject buttons in the conversation. Whoever presses one starts a new turn that records who decided and when, and the buttons retire the moment they’re used.Workers manage their own tools
Ask your worker in Slack to connect an app, take an API key, or reconnect a service. For sign-in apps it posts a link anyone in the conversation can approve; for key-based apps, paste the key and it’s stored securely. Each worker stays in its own lane — organization-wide connections are still made on the Connections page.Responsibilities and behaviors
Every worker now has two short, editable lists on its page in the control panel: what it’s responsible for, and how it goes about its work. Both start empty and change nothing until you fill them in. Edit them yourself, or ask your worker to propose an update when you hand it something new to own.Slack’s new agent experience
New workers install as Slack’s current agent experience. When you DM a worker you’ll see just the conversation — no more separate Messages and History tabs.Improvements
- Rename connections. Connections can now be renamed from the Connections page.
- Smarter channel onboarding. Invite a worker to a channel and it privately suggests to you what the room might be for, based on its name and members. Workers leave immediately if added by a Slack Connect guest.
- Progress updates in place. Each turn’s status is posted once and updated as the turn runs, instead of occasionally splitting into several messages.
- Long turns no longer look frozen. A turn running past five minutes now shows a clear error state rather than appearing stuck.
- Two accounts of the same app. You can now connect a second account of an app you already use — two Attio workspaces on different workers, for example.
Fixes
- API key field names. Connecting an app by API key now sends the key under the field name that app expects. Apps that named the field differently were being refused.
- Apps that need extra fields. Apps that need more than a key, like a region or subdomain, now get correct defaults when a worker connects them, and a failed check no longer leaves a stray account behind.
Workers can see images, and connections that stay connected
Workers can look at what you send them for the first time, and third-party connections are both faster to set up and much harder to knock over.
Workers can see images
A photo, screenshot or diagram attached to a Slack message — or stored in a worker’s memory — now reaches the worker as an image it can actually look at, rather than unreadable data. Ask about a chart, a mockup or a whiteboard photo and get a real answer.A faster Connect sheet
The app catalog on the Connections page now opens instantly and caches what it loads, removing the four-to-six-second wait every time you opened it.Improvements
- Clearer direct API connections. For services connected by base URL rather than from the catalog, workers now see the full registered address and know it’s a direct API, so they build correct requests without guessing.
Fixes
- Permission errors no longer disconnect. When a service refused one specific call, the whole connection was being marked expired. Now only a genuinely invalid or revoked credential disconnects; a missing permission shows up as a clear “not permitted for this call” and the connection stays live.
- Reconnect links complete. Reconnecting a key-based app through its link no longer lands on a mismatch error when the reconnect actually worked.
- Real @mentions. Workers occasionally posted mention markup as plain text, so the person was never notified. Mentions now render as real Slack @mentions.
- Moving older API keys across. Keys for services outside the app catalog now carry over correctly when an organization moves to the new connection system.
- Credentials kept out of logs. A failed command in a worker’s sandbox could write an internal access token into the sandbox log. It no longer can.
Connections: hundreds of apps, one page
This release is about how workers reach the rest of your stack. A new connections system gives every worker access to hundreds of ready-made apps — Google Sheets, HubSpot, Linear and many more — along with custom MCP servers and any service with an API key, all managed from one Connections page.
A single Connections page
Each connection now shows what it is, which account is signed in, where it’s used and whether it’s healthy. Click one to finish setting it up or change it. Older connections move to a Legacy tab and keep working exactly as before.The full app catalog
Adding a connection opens a picker organized by category, with popular apps up front and the entire catalog one click away. Custom MCP servers, your own OAuth app and raw API keys are always options.Any API, by key
A service that isn’t in the catalog can be connected with its API key from the same page. The key is stored securely and the worker can use that service’s full API through it.One way to use every tool
Workers list, search and run whatever their connections provide through a single built-in skill, with no per-service setup. Every turn, a worker knows exactly what it has access to.Progress you can read
Progress updates now read as narrated reasoning: each step in plain English, a header that describes the work, and a clean close when the turn ends. No more internal step names.Improvements
- DM anyone. A worker asked to message a colleague can now DM anyone the bot can see, not only people tied to a client. If a delivery fails, the notice names the person rather than showing a Slack ID.
- Set the escalation contact. Choose who a worker escalates to directly in its settings.
- Inbound webhooks. Workers can create their own inbound webhook endpoints, so events from outside services can kick off work.
Fixes
- Authenticated calls. Some outbound requests — web searches among them — were going out without their credentials and failing. Every credentialed call is now authenticated correctly.
- API key page redirect. Admins who hadn’t finished setup were bounced to the setup flow when creating an API key. The settings page now stays put.
Workers get their own email
Email sending is live, and workers are substantially more reliable at reading the conversation they’re in, finding their own skills and knowing who’s in the room.
Worker email
Every worker now has its own address and can send email directly. The control panel shows your organization’s sending domain, its DNS records, each worker’s address and an on/off switch, and every message sent is logged.Workers know what they know
Each turn, a worker sees an index of everything in its memory, with a description for every file. It can check what it knows before saying it doesn’t — fewer invented or inconsistent answers.Better at Slack
Workers look up who’s in a channel, who a person is and what was said earlier directly, without a detour. They also report progress mid-turn without sending a reply, and escalations reliably reach a person.Scheduled tasks can do what a live turn can
A scheduled run can now post into a thread, a DM or a new message — anything a worker can do when you’re talking to it.Fixes
- Thread context. Workers couldn’t always read the thread they were replying in. They now have the full thread on every turn.
- Knowing itself. Workers sometimes read their own @mention as someone else’s and mixed up people in the room. They now know their own identity.
- Channel setup menu. The menu shown when a worker first joins a channel wasn’t appearing. It’s back.
- Connections and new-worker setup. Both pages could fail to load with an error. Fixed.
- Switching organizations. Switching organization from the sidebar led to a missing page. It now lands where it should.
- Company page scrolling. A wide org chart scrolled the whole page sideways. The chart now pans and zooms inside its own frame.
- Silent Slack failures. When Slack rejected a reply, nobody found out. The worker now posts a notice that something went wrong.
The platform API, a simpler worker, and better scheduled tasks
Three large changes this week — a public API, a simpler worker underneath every teammate, and scheduled tasks rebuilt — plus a sweep of reliability fixes.
The platform API
Everything in your Ergoly environment — workers, clients, channel mappings, tasks, spend and connections — can now be read and changed through an organization-scoped REST API. Create and set up workers, map channels, schedule tasks and write memory with an API key. The API reference is linked from the control panel.A simpler, more consistent worker
Every worker now runs on the same small set of core tools, with everything else expressed as skills it reads and follows. Workers behave the same way across your organization and are easier to extend.Scheduled tasks, rebuilt
Each run gets its own Slack thread and can be interrupted with a reply. Tasks run as a named person, can target several clients from one definition, and can be seen and managed in the control panel.The Company page
A new page in the control panel shows your workers, people and teams as an org chart. Create teams and open roles, add people from Slack, and drag to reorganize.Workers can read app messages
When an app posts a rich message in Slack — a Linear card, a form submission, an alert — the worker now receives the whole thing, not just the one-line preview.Improvements
- Choose your avatar style. Pick your organization’s avatar style in settings; it applies to every worker straight away.
- App icons set automatically. Installing a worker into Slack now sets its icon for you, with a button to re-push it if it changes.
Fixes
- Long turns complete. A model step longer than a minute could derail a turn. Long turns now finish correctly.
- Separate conversations for parallel runs. Runs of a scheduled task that fired at the same time could share one conversation. Each run now gets its own.
- Usage metering. Per-customer usage was being under-recorded. It’s now accurate.
- No more stuck approvals. A stuck approval state could hold a worker indefinitely. The cause is fixed.
- Client channels recognized. Workers sometimes treated a client channel as a private DM and declined to use that client’s connections. Fixed.
- Timeouts named correctly. A scheduled task that ran out of time now reports a timeout, not a generic failure.
- Control panel stability. Crashes on the organization dashboard and the worker page are resolved.
Streamed replies, richer output, and a reliability sprint
The biggest change yet to how your worker speaks in Slack, plus a round of fixes aimed at the failures we heard about most.
Live streamed replies
Instead of sending several messages while it works, your worker now posts one message that updates in place. Named progress steps appear as they happen, then the answer streams in underneath. The channel stays readable and you always know where things stand.Tables and files
Workers can send properly formatted tables and upload files directly into Slack. A comparison, a list of records or a report arrives as a real table instead of a wall of text.One place for memory
The Knowledge tab in the control panel now shows a worker’s memory as a single file tree with named folders, instead of four separate views.Improvements
- Faster long tasks. Workers run longer scripts more efficiently, so big tasks finish sooner.
Fixes
- No more phantom deliveries. After a failed turn, a worker could claim work was waiting in a thread where nothing had been posted. It now knows whether its last reply landed.
- Quotes no longer cut replies short. A reply containing a quotation mark was being truncated at the quote.
- Scheduled tasks get the full time. Task runs were stopped after a minute. They now get the same 30 minutes as a live turn.
- Listen-only means listen-only. Workers set to listen without speaking could still post in some cases. No longer.
- Accurate explanations. Workers sometimes told people a message had been suppressed when it had been delivered. They now describe their own behavior correctly.
- Recovering from stuck states. Many stuck-worker reports traced to one family of bugs, now reworked. Workers recover from these on their own instead of waiting for a reset.
- Messages during start-up. Two messages arriving while a worker was waking could cause the second to fail. Both are now answered.