Most turns in a chat start with a message from you. Some start by themselves: a scheduled run, a background task, a plugin, a goal, a task or team message, a subtask, an outside event or a suggestion. When that happens, the turn opens with a notice that says what woke Oda. This page explains each notice and what you can do from it.
| Notice title | What it means |
|---|---|
| Scheduled task | One of your scheduled tasks ran and started this chat. See Schedule recurring tasks. |
| Background task updated | A background task moved on and brought its update into the chat. See Background jobs: limits and lifecycle. |
| Plugin status updated | A plugin Oda uses changed status. See Plugins and MCP connections. |
| Continuing goal | Oda woke the chat to keep working on its goal. See Chat with Oda. |
| Task message received | A message from a task reached the chat. |
| Team message received | A message from a teammate reached the chat. See The Team panel in Activity. |
| Subtask status updated | A subtask of the chat's work changed state, for example a delegated run settling. See Subagent settlement and results. |
| GitHub event received | A GitHub delivery started this chat. See Webhook sessions. |
| External event received | An outside event from a source other than GitHub started the turn. |
| Execution requested | A request to run reached the chat, and the recorded source does not name who asked. |
A turn started from a suggestion uses one of two phrasings instead: Started from a suggestion in plus the name of the chat it came from, or Started from a suggested task when that chat is not available.
Some turns start on their own rather than from your message: a scheduled run, a background task, a plugin, a goal, a task or team message, a subtask, an outside event or a suggestion. The reply opens with a notice whose title names the source; expand the notice to see what triggered the response.
It is the line inside an expanded trigger notice. It means the turn was started by the notification it sits in, not by a message you sent; the notice's title and details say which source woke Oda.
One of your scheduled tasks ran and opened this chat; the reply is that run's work. Find the task and its runs under Scheduled in the sidebar, and see Schedule recurring tasks.
The turn began from a suggested task, and the notice names the chat the suggestion came from. Choose the Open button, which carries that chat's title, to jump back to it. When the original chat is not available, the notice reads Started from a suggested task instead.
Oda offers the button only when it can reach the chat the suggestion came from. When it cannot, the notice keeps to its title, and you can still read the reply and the notice's details of what triggered it.
A request to run something reached the chat, and the recorded source does not name who asked. The notice stays generic on purpose: it does not guess a source it does not have.
A GitHub delivery that your webhook setup verified started this chat. See Webhook sessions for what a delivery creates, and GitHub webhooks for the endpoint itself.
An outside event from a source other than GitHub started the turn. When the event is a GitHub delivery, the notice reads GitHub event received instead; other outside sources stay under this title.
A subtask of the chat's work changed state, for example a delegated run settling. See Subagent settlement and results.
Oda woke the chat to keep working on its goal without you sending a message. Goals are set with /; Chat with Oda covers how they work.
A background task moved on while it runs and brought its update into the chat. See Background jobs: limits and lifecycle.
Both mean the chat received a message that did not come from your typing: from a task it is part of, or from a teammate. See The Team panel in Activity for team work.