@sentry/junior 0.27.1 → 0.27.2

package/dist/app.js

@@ -3409,6 +3409,10 @@ function buildSystemPrompt(params) {
         "- Use Slack-friendly markdown, not full CommonMark. Prefer bold section labels over markdown headings, and use bullets and short code blocks when helpful.",
         "- Keep normal responses brief and scannable.",
         "- If depth is needed, start with a concise summary and then provide fuller detail.",
+        "- Prefer a single compact thread reply when the full answer comfortably fits within this inline budget.",
+        "- When canvas creation is available and a research or document-style answer would likely need continuation, multiple sections, or future reference value, create a Slack canvas and keep the thread reply to a short summary plus the canvas link.",
+        "- Typical canvas-first cases include long-form research summaries, timelines, bios or profiles, structured notes, plans, comparisons, and other reusable reference documents.",
+        "- Do not create a canvas for short factual answers that fit cleanly in one normal thread reply.",
         "- For tool-heavy research, discovery, or source-checking requests, do not send an initial acknowledgment. Start the visible reply only once you can present the actual answer.",
         "- Do not narrate tool execution or repeated status updates in the visible reply.",
         "- Avoid tables and markdown links like `[label](url)` unless explicitly requested. Prefer plain URLs or Slack-native entities when exact rendering matters.",
@@ -5665,7 +5669,7 @@ function mergeRecentCanvases(existing, created) {
 }
 function createSlackCanvasCreateTool(context, state) {
   return tool({
-    description: "Create a Slack canvas for long-form output in the active assistant context channel. Use when content is too long for a thread reply or needs a persistent document. Do not use for short answers that fit in-thread.",
+    description: "Create a Slack canvas for long-form output in the active assistant context channel. Use when the answer is better as a reusable document than a thread reply: long-form research, timelines, bios/profiles, structured notes, plans, comparisons, or anything likely to exceed one compact Slack reply. After creating it, keep the thread reply brief and include the canvas link. Do not use for short answers that fit cleanly in one normal thread reply.",
     inputSchema: Type11.Object({
       title: Type11.String({
         minLength: 1,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sentry/junior",
-  "version": "0.27.1",
+  "version": "0.27.2",
   "private": false,
   "publishConfig": {
     "access": "public"