Commit 3340e3d
committed
fix: prevent Paperclip heartbeat spam, stable thread per task
Root cause: deployed agents had no runtimeConfig, so Paperclip's
default heartbeat scheduler could fire repeatedly. Each heartbeat
created a new AF thread (using runId), causing thread spam.
Fixes:
- Deploy now sets runtimeConfig.heartbeat.intervalSec=0 (on-demand
only, no automatic timer). Configurable via --heartbeat-interval.
- Paperclip connector uses issueId as threadId (not runId), so
repeated triggers for the same task reuse the same AF conversation
thread, preserving context instead of creating duplicates.
- Added --heartbeat-interval flag to `af paperclip deploy`
Verified by sub-agent: 2 triggers for same issue → same thread_id,
2 comments (not 50), conversation continuity preserved.1 parent 79c488f commit 3340e3d
2 files changed
+12
-1
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
61 | 61 | | |
62 | 62 | | |
63 | 63 | | |
| 64 | + | |
| 65 | + | |
64 | 66 | | |
| 67 | + | |
65 | 68 | | |
66 | 69 | | |
67 | 70 | | |
68 | 71 | | |
69 | 72 | | |
70 | | - | |
| 73 | + | |
71 | 74 | | |
72 | 75 | | |
73 | 76 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
4336 | 4336 | | |
4337 | 4337 | | |
4338 | 4338 | | |
| 4339 | + | |
4339 | 4340 | | |
4340 | 4341 | | |
4341 | 4342 | | |
| |||
4416 | 4417 | | |
4417 | 4418 | | |
4418 | 4419 | | |
| 4420 | + | |
| 4421 | + | |
| 4422 | + | |
| 4423 | + | |
| 4424 | + | |
| 4425 | + | |
| 4426 | + | |
4419 | 4427 | | |
4420 | 4428 | | |
4421 | 4429 | | |
| |||
0 commit comments