| name | threadkeeper-setup |
| description | Configure Threadkeeper, including an explicit, changeable conversation backfill scope, serendipity setting, and sensitive-category privacy default. Use when the user asks to set up, enable, configure, or backfill Threadkeeper. |
| metadata | {"emoji":"🧵","vellum":{"category":"productivity","display-name":"Threadkeeper Setup","activation-hints":["User asks to set up or configure Threadkeeper","User asks Threadkeeper to backfill old conversations","User asks whether Threadkeeper should include sensitive topics"],"avoid-when":["User only wants to review existing loops or proposals","User asks a historical project question; use context-archaeologist"]}} |
Threadkeeper setup
Configure conservatively. Do not begin a historical backfill merely because the plugin is installed.
The scope is a runtime preference and can be changed later without reinstalling the plugin.
Backfill scope choices
Choose exactly one scope when starting or changing a backfill:
future_only (recommended safest default)last_30_dayslast_90_daysall (unsafe broad scan; requires explicit confirmAllHistory: true)- a custom positive integer day count, for example
{ "days": 45 }
- an explicit inclusive ISO date range, for example
{ "startDate": "2026-01-01", "endDate": "2026-03-31" }
Date ranges use conversation updatedAt, include both calendar endpoints, and require valid YYYY-MM-DD dates with the start on or before the end. Custom day counts are positive integers from 1 through 36,500.
