adam/open-swe
1
0
Fork 0
mirror of https://github.com/Sea-Haven-Industries/open-swe.git synced 2026-09-30 08:03:15 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

fix: skip notification step when no source channel context is present (#1119)

Browse source 
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 <agent@anthropic.com>
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
langsmith-forge-dev[bot] 2026-05-01 11:41:18 -07:00 • committed by GitHub
parent 3683614601
commit 28027d5295
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 2 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
agent/prompt.py
View file

@ -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:
```