You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(dashboard-agent): move the agent to Claude Sonnet 5, with per-role model overrides and a managed summary prompt
feat(dashboard-agent): move the agent to Claude Sonnet 5, with per-role
model overrides and a managed summary prompt
The in-dashboard agent now answers with Claude Sonnet 5 for its main
turns, the code and watch prompts, the warm first-turn step, compaction
summaries, attention wakes and the turn eval judge. Claude Haiku 4.5
stays on chat titles.
- Adds the Bedrock inference profile mapping for Sonnet 5 and keeps the
Sonnet 4.6 entry so stored prompt versions that still name it resolve.
- Switches thinking off for the bounded calls (summaries, attention
wakes) so their output caps are all answer.
- Main turns and the warm first-turn step pass each model's documented
output ceiling explicitly, so an unknown-to-the-provider id no longer
falls back to a 4096-token cap.
- The compaction summariser is a managed prompt
(`dashboard-agent-summary`), so its text and model can be versioned and
overridden from the dashboard like the system prompt.
- Each role's model can be overridden per environment with
`DASHBOARD_AGENT_MODEL`, `DASHBOARD_AGENT_SUMMARY_MODEL`,
`DASHBOARD_AGENT_JUDGE_MODEL` and `DASHBOARD_AGENT_TITLE_MODEL`, with
the above as defaults.
- No dependency changes; the installed providers accept the new id.
Mono-RevId: c01a1daba486863c535fede891d96259fa6b7386
* A hard ceiling on the summary, because "under 400 words" is an instruction and not a
62
61
* budget. 400 words is ~530 tokens, so this is roughly double what the summary needs.
62
+
* Thinking is switched off for the call, so none of it goes on hidden reasoning.
63
63
*/
64
64
constSUMMARY_MAX_OUTPUT_TOKENS=1_000;
65
65
66
-
exportconstSUMMARY_INSTRUCTION=`You are compacting a support conversation between a user and an agent that reads a Trigger.dev dashboard, so the agent can keep going with a shorter history.
67
-
68
-
Write a summary in under 400 words, as notes rather than prose. Keep, in this order:
69
-
1. What the user is trying to do, in their own terms, and anything they asked to be remembered.
70
-
2. Facts already established, with the run ids, queue names, task identifiers, error fingerprints and numbers they rest on. Never restate a number you cannot see.
71
-
3. Any investigation that is open: its investigationId, its title and its current outcome.
72
-
4. Any watch the transcript records — what it was set up to watch, and what it said if it reported. Write it as what the transcript recorded, never as what is true now: a watch can expire or be cancelled without saying so here, so never present one as current.
73
-
5. What was asked most recently and what is still unanswered.
74
-
75
-
Drop tool mechanics, retries, and anything already superseded. Do not add advice, and do not invent anything that is not in the transcript. Everything you write is a record of what the transcript said, not a claim about the present.`;
76
-
77
66
/** A summary that reads as a summary, and never as the user's next question. */
0 commit comments