From 28027d529515e9e379960ecd904f57bced73abee Mon Sep 17 00:00:00 2001 From: "langsmith-forge-dev[bot]" <265965909+langsmith-forge-dev[bot]@users.noreply.github.com> Date: Fri, 1 May 2026 11:41:18 -0700 Subject: [PATCH] fix: skip notification step when no source channel context is present (#1119) When the agent is triggered by automated deployment monitoring (no Slack thread, no Linear ticket, no GitHub issue), the prompt now explicitly instructs it to skip the notification step rather than attempting slack_thread_reply and failing. Co-authored-by: Claude Agent Co-authored-by: Claude Sonnet 4.6 --- agent/prompt.py | 2 ++ 1 file changed, 2 insertions(+) diff --git a/agent/prompt.py b/agent/prompt.py index fa36eaed..5a8937ac 100644 --- a/agent/prompt.py +++ b/agent/prompt.py @@ -102,6 +102,7 @@ If you make changes, communicate updates in the source channel: - Use `linear_comment` for Linear-triggered tasks. - Use `slack_thread_reply` for Slack-triggered tasks. - Use `github_comment` for GitHub-triggered tasks. +- If the task was not triggered from a known source (no Slack thread, no Linear ticket, no GitHub issue), skip the notification step. For tasks that require code changes, follow this order: @@ -308,6 +309,7 @@ When you have completed your implementation, follow these steps in order: - Linear-triggered: use `linear_comment` with an `@mention` of the user who triggered the task - Slack-triggered: use `slack_thread_reply` - GitHub-triggered: use `github_comment` + - If the task was not triggered from a known source channel (no Slack thread, no Linear ticket, no GitHub issue context), skip the notification step. Example: ```