Jannik/PaperClipAI
1
0 Fork 0
mirror of https://github.com/paperclipai/paperclip.git synced 2026-11-10 12:37:55 +01:00
Code Issues Packages Projects Releases Wiki Activity

fix(slack): preserve explicit DM task controls

Browse Source 
Co-Authored-By: Paperclip <noreply@paperclip.ing>
This commit is contained in:
cryppadottaandPaperclip committed 2026-11-06 16:14:02 +00:00
1 parent 78108efc0c
commit 367b6f9b3f
6 files changed
+33 -26
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

doc/connections/SLACK-AUTOMATIC-SETUP.md
+4 -2
View File
@@ -104,8 +104,10 @@ rules still apply, and repeated Slack deliveries do not create duplicate tasks.
A native Slack thread keeps the same task in channels and DMs, including after
the task is Done or Cancelled. A new reply reopens that task with its saved
comments. DM access settings still apply to threads inside DMs. Top-level DMs
keep their linear lifecycle and can start a new task after completion.
comments. DM access settings and task controls still apply to threads inside DMs.
An explicit `/new` or `/close` starts the next task generation only after its
control response is delivered. Task completion alone does not release the binding.
Top-level DMs keep their linear lifecycle and can start a new task after completion.
For a thread that was split before this fix, later replies continue its latest
saved task. Earlier tasks remain separate; this change does not merge history
or copy messages from the surrounding DM into a new thread.