[sentry-junior]

A conversation that starts with "Fix this " gets a vague title like "Verify Issue 1583 and Submit PR if Valid". The title model only sees the URL, so it can't tell what the issue is about.

This adds a provider-neutral conversationTitleContext plugin hook. Before core generates a title from the first human message, it asks plugins for short facts about objects linked in that message. The title model sees those facts under "Linked objects", and the prompt tells it to name the object by number and title (for example, Fix #1583: Login fails on Safari).

The GitHub plugin implements the hook. It finds up to 3 distinct issue, pull request, and commit references (URLs, GitHub autolinks such as owner/repo#123, and prose such as "issue 1583 on getsentry/junior") and reads each title.

The hook reads through host-owned credentialed egress (ctx.egress), not a token it mints itself. Title work runs outside the Turn, so core gives it a conversation-title system actor. Egress policy, grant selection, and audit telemetry apply. The system actor gets only installation grants, never user tokens, and title work never starts authorization. Reads reuse the shared installation lease, so no extra token is minted per object.

The hook is optional and fails open. Core stops waiting after 5 seconds, ignores hooks that throw, and caps how many lines plugins can return and how long each line can be. If nothing comes back, titles are generated the same way as before. Dispatched runs, which have no human message, don't call the hook.

Note: titles from private repositories in the installation can now show up in conversation titles. Junior can already read and quote that content in replies in the same conversation, with the same installation-read grant.

The new lifecycle eval (when the first message links a tracked issue…) needs a Roach recording. I couldn't record it locally without the write token, so it will record on its first CI run.

via BYK.

--

View Junior Session in Sentry

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
junior-docs	Ready	Preview	Oct 27, 2026 5:36pm UTC

[sentry-evals]

Sentry Evals

junior-integration

Run	Status	Passed	Failed	Errored	Cost	Tokens	Duration
Head	Passed	102	0	0	$0.98	0	351.48s

Base commit 11d1221 has no eval run to compare against.

[BYK]

Ideally it would detect anything listed here, assuming github: https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls

Also alternatives like:

• Let's fix issue 1583 on getsentry/junior
• Let's get PR 1234 fixed up

etc.

[sentry-junior]

@dcramer, about the question of this PR minting its own tokens: it did at first, but head 4498965 changes that. The title context hook now goes through the proxy.

• The GitHub conversationTitleContext hook reads issues, PRs and commits through ctx.egress.fetch (operations github.issue.get, github.pull.get and github.commit.get). It no longer calls issueInstallationToken or githubRequest.
• Core builds that egress in packages/junior/src/chat/plugins/conversation-title-context.ts with createPluginEgress. It runs as a conversation-title system actor. That actor gets only installation grants, never user tokens, and it never starts authorization.
• The host credential proxy picks the grant and adds the token. It reuses the shared installation lease, and egress policy and audit apply.
• Against main, this PR's diff has no issueInstallationToken or githubRequest calls.

The webhook route on main still mints installation tokens directly. It does this to read PR commit pages for commit classification and to add the "reviewing" reaction on feedback comments. That code is older than this PR. It has no Turn or credential context, so it never used egress. #2222 moves those calls into webhooks/installation-requests.ts. Its oxlint rules ban direct GitHub calls everywhere in the plugin except credential-support.ts and webhooks/. A possible follow-up is to route the webhook calls through egress as a system actor, the same way title context does.