-
Notifications
You must be signed in to change notification settings - Fork 277
feat(agent): gather thread_ts or message ts of events outside of assistant context #1444
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: zimeg-feat-agent-set-suggested-prompts
Are you sure you want to change the base?
Changes from all commits
1e1c167
2cbb1af
38d0c42
f2f084e
2c664c1
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -218,6 +218,9 @@ def extract_thread_ts(payload: Dict[str, Any]) -> Optional[str]: | |
| # This utility initially supports only the use cases for AI assistants, but it may be fine to add more patterns. | ||
| # That said, note that thread_ts is always required for assistant threads, but it's not for channels. | ||
| # Thus, blindly setting this thread_ts to say utility can break existing apps' behaviors. | ||
|
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 👁️🗨️ thought: I'm surprised that I agree that a "fix" for this, to respond in thread if a |
||
| # | ||
| # The BoltAgent class handles non-assistant thread_ts separately by reading from the event directly, | ||
| # allowing it to work correctly without affecting say() behavior. | ||
| if is_assistant_event(payload): | ||
| event = payload["event"] | ||
| if ( | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
📝 note: We avoided adding a new
tsvalue to the listenercontextin this PR and instead use the event information. This was to keep scope changes minimal and parity with the Bolt JS implementation IIRC.