Logan Ramos

Refactor model picker architecture (#326052) * Refactor model picker * Some linters and formatters * Cleanup some old tests * Simplify model picker state and configuration * format stuff * Address model picker review feedback * Update blocks-ci screenshot hashes * Simplify model picker architecture terms

Chat usage tracking improvements (#328012) * Agent host usage tracking Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: e3463606-86bf-4c41-ab25-936dc1c9d952 * Cleanup some model picker stuff * Address comments --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: e3463606-86bf-4c41-ab25-936dc1c9d952

Coalesce content exclusion fetches to stop exhausting the GitHub API rate limit (#328268) * Coalesce content exclusion fetches to stop exhausting the GitHub API rate limit Every caller that discovered a new repository triggered a refresh of the content exclusion rules for *every* known repository, so request volume grew quadratically with repository count. In a workspace with many git repos (an AOSP checkout, in the reported case) this produced ~16k requests to api.github.com in 30 minutes, exhausting the account's 5k/hour REST budget and starving everything sharing it, including Copilot token refresh. The endpoint is https://api.github.com/copilot_internal/content_exclusion, so it draws on the user's ordinary REST quota rather than a CAPI budget. - Coalesce per repository using shared DeferredPromises, a short batching window and a bounded-concurrency Limiter, so each repo is fetched at most once per TTL and each caller only waits on the repos it asked for. A regression test measures 75 requests -> 3 for 26 repositories. - Only cache rules on a successful response. Empty placeholder rules were written on discovery and left in place on failure, making a failed fetch indistinguishable from "this repo has no exclusions" and preventing a retry for 30 minutes, so exclusions silently stopped applying while rate limited. - Only memoise a negative verdict once the relevant rules actually loaded, which otherwise left files checked during an outage permanently allowed. - Add a shared rateLimitBackoffMiddleware covering 429 and quota-exhausted 403 responses, honouring Retry-After and x-ratelimit-reset, and move both RemoteContentExclusion and CloudSessionApiClient onto it. This replaces a third hand-rolled copy of the same backoff logic. - Precompile glob patterns, track the regex rule count directly, and only invalidate memoised results when rules that could change an outcome arrive. Fixes #322275 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 32f94728-158b-4639-b789-a5dd483f043f * Address review feedback on cache invalidation and request lifecycle Five correctness issues raised in review, each with a test that fails against the previous implementation. - rateLimitBackoffMiddleware: a response that was already in flight could clear a block established by a concurrent rate-limited request, letting later calls reach the server during the window the server asked us to wait out. The backoff is now only reset once the active block has elapsed. - isIgnored returned a memoised verdict before reaching the staleness check, so a URI that had been evaluated once never triggered a refresh and could miss newly added exclusions indefinitely. Verdicts are now tagged with a rule generation and are only trusted while the rules behind them are unchanged and unexpired. - applyRules only invalidated verdicts when the incoming rules were non-empty, so a refresh that removed the last rule left files excluded permanently. Incoming rules are now compared against the previous set, which also avoids invalidating on an unchanged refresh. - drainPendingRepos cleared the pending map before its batches completed, so a lookup arriving while a request was slow queued a duplicate fetch every batching window. Entries now stay registered until their request settles, and are removed only if still owned by that attempt. - dispose only settled repos still queued. Limiter.dispose drops queued factories without running them, so with more than five batches the callers awaiting them never resolved. Pending entries are now settled before the limiter is disposed, and enqueues after disposal resolve immediately. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 32f94728-158b-4639-b789-a5dd483f043f --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 32f94728-158b-4639-b789-a5dd483f043f

Improve copying chat output to external apps (#328466) * Improve copying chat output to external apps * address comments

Add more model picker diagnostics and cleanup architecture (#326894) * Add more model picker diagnostics and cleanup architecture * Fix stale model selection call after merge * Preserve restored chat model selection * Address comments

Further Unify Model Picker Architecture (#326351) * Further unify model picker architectures * Address model selection review feedback * Unify model picker storage

Simplify model selection restoration (#326965) * Simplify model selection restoration * Restore chat widget main behavior * Simplify chat model selection reconciliation * Simplify model picker architecture

Adopt latest models in Auto (#329021) * Start auto v2 exploration * Auto V2 * Update based on comments

Improve chat input CTAs (#326003) * Cleanup notification code and make it model picker aware * Fix chat input notifications not being session type aware * Fix session awareness

Support Auto Tiers (#329463) * Support Auto tiers * Make auto tiers an exp driven thing * Resolve comments

Suppress keybindings and filtering during IME composition (#328269) * Agent Host changes for lramos15/agents/investigate-issue-318977-fix * Use KEY_IN_COMPOSITION as the single IME signal Drop the `isComposing` member from both `IKeyboardEvent` interfaces and rely on the normalized key code instead. `StandardKeyboardEvent` already reports `KEY_IN_COMPOSITION` for every composing keystroke, so a parallel `isComposing` flag was a second source of truth for the same fact. It also broke the standalone editor build: `@internal` members are stripped from `out-editor-src`, which left `base`'s interface without the property while `platform`'s still required it, so the two `IKeyboardEvent` types stopped being assignable (5 errors in editor-distro). Using the key code fixes that build, keeps `monaco.d.ts` unchanged, and reverts the `isComposing: false` churn from the keyboard mapper tests. Also cancel any in-flight dynamic filter when a composition starts: a request issued for the previous value could otherwise resolve mid-composition and splice and re-layout the list underneath the IME candidate window. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: c4ba1417-a152-448b-af4b-1a5017b949e8 --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: c4ba1417-a152-448b-af4b-1a5017b949e8

Improve the local to native and remote to local copy, paste, and DND experience (#320685) * Improve the local to native and remote to local copy, paste, and DND experience * Address comments

Drive session cost from SDK's API (#328232) * Drive session cost from SDK's API * Address PR feedback on SDK-driven session cost - Serialize `usage.getMetrics` reads behind a `Throttler`. Several handlers refresh the session total, so their RPCs could overlap and an older one resolving last would publish a session cost that visibly regresses. A high-water guard can't reject the stale value because the total is legitimately non-monotonic — `history.truncate` makes the SDK re-fold usage from the surviving events. Keeping one read in flight removes the interleaving and coalesces the redundant reads a burst of events would issue. - Emit the compaction's per-turn cost synchronously, before awaiting the metrics read, then re-emit to enrich it with the session total. The terminal `session.idle` can close the turn mid-read, after which the reducer drops its usage — so a compaction whose turn ends immediately was never persisted. - Teach `hasReportedUsage` about `sessionTotalNanoAiu`. A compaction billed while no turn was active advances only the session total, and such a report was being treated as empty and dropped by `usageInfoToChatUsage`. - Correct two comments that described the wrong billing source: per-turn cost accumulates synchronously from each event's `copilotUsage`; the SDK's usage metrics supply only the session-wide total. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: c33a0289-7f6d-40de-9f11-4b2e474a5e9c --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: c33a0289-7f6d-40de-9f11-4b2e474a5e9c

Make sub agents implemented as tools render as subagents (#326867)

Implement cache expiration notification for chat input (#327331) * Agent Host changes for lramos15/agents/sdk-cache-expiration-notification * Fix prompt cache notification lifecycle Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: a40a876c-ed33-4630-8676-f6fbded1eaa0 * Update prompt cache E2E snapshot Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: a40a876c-ed33-4630-8676-f6fbded1eaa0 * update cache wording * Fix prompt cache notification test expectation Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 7718528b-0a94-4298-baf4-2ae9428e21e9 --------- Copilot-Session: a40a876c-ed33-4630-8676-f6fbded1eaa0 Copilot-Session: 7718528b-0a94-4298-baf4-2ae9428e21e9

Support showing promo messages with no end date and no % discount (#329193) * Support showing promo messages with no end date and no % discount * Address PR feedback on promo message support - Tighten promo JSDoc on the metadata contract, notification contribution, and helpers to match repository JSDoc limits - Document the positive/zero/negative discount cases so message-only promos are not omitted by agent implementations - Cover open-ended, message-only promos through the untyped _meta read and the CAPI billing normalization Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: edb3b42a-1bec-45f8-9453-51ad10583f06 --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: edb3b42a-1bec-45f8-9453-51ad10583f06

Only refresh models under active turns (#328818) * Only refresh models under active turns * Address comment

Support model pinning (#316253) * Support model pinning * Cleanup some hardcoded auto logic

Add chat resumed status bar entry when quota resets (#322113) * Add chat resumed status bar entry when quota resets * Address comments * Address comments

Display session cost + persist context widget (#321803) * Display session cost + persist context widget * fix tests + comments