Move single-tool rules from the system prompt into tool descriptions

Aperta
  • Qualcosa non va?
#2,411 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Refactoring
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
ai-infra-agents

Direzione di ricerca

Start with packages/junior/src/chat/system-prompt-rules.ts, then read the referenced system prompt policy and tool descriptions in agent-steering.md and tool-design.md. Check each listed rule to determine whether it applies to one tool or several, and inspect the behavioral and integration evals before making changes. Done means single-tool rules live only in that tool’s description or promptGuidelines, cross-tool rules remain in the system prompt, and evals show no new failures against main.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Follow-up to #2364 and #2371.

policies/system-prompt.md says block 5 (<tool-policy>, <skill-policy>, <planning>) holds only rules that apply to more than one tool. A rule about one tool goes in that tool's description (agent-steering.md, tool-design.md). #2371 wrote this rule down, but it did not move the existing single-tool rules.

Candidates in packages/junior/src/chat/system-prompt-rules.ts (check each one; some may apply to more than one tool):

  • The subscription and watchEvents rule (subscription, suggestedEvents, temporary watch expiry).
  • The loadSkill rules in <skill-policy>.
  • The updatePlan rule in <planning>.
  • The Slack send-tool limit in <slack-actions> (no new top-level channel posts).
  • The tool card rule ("Cards returned by tools attach to your next visible reply").
  • The handoff / spawnAgent decision line.

Done when:

  • Each rule that is about one tool lives in that tool's description or promptGuidelines, and only there.
  • The system prompt keeps only rules that apply across tools.
  • The behavioral and integration evals show no new failures, compared against a run of main.

Note: moving text out of the static system prompt changes the cached prefix. Tool descriptions must stay the same from turn to turn, as the caching rules in the policy require.

via David Cramer.

--

View Session [Sentry]

Lingua principale
TypeScript
Stelle
385
Fork
42
Merge medio
10h 4m
PR unite (30g)
361

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di getsentry/junior

Tutte le issue di getsentry/junior

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.