Cache Keepalive: stay dormant until the first message/generation of the tab session

4b6db4ab8cabb9ea2efba3790631e37f4f6a1c64

permissionBRICK <permissionBRICK@gmail.com>

public/scripts/extensions/keepalive/index.js+29 -10 Viewed

 let idleTimer = null;
 let keepaliveActive = false;
 +// Whether keepalive has been "armed" this browser-tab session. It stays dormant until the
 +// first real message/generation happens in the tab, because on a fresh load (even with chat
 +// history already present) we have no way to know whether anything is still cached
 +// server-side — so pinging before then would be pointless. Resets on page reload.
 +let armed = false;
 // Per-profile "time since last message", keyed by connection profile id (or NONE_KEY).
 // In-memory only: on reload every profile is treated as freshly active.
 const lastActivity = {};

 /**
  * (Re)schedules the keepalive for the ACTIVE profile based on how long it has been since
  * that profile's last message. Does nothing (and leaves the timer cleared) whenuntil keepalive is
  * disabledhas been armed for thethis activetab connection.session, Calledor onwhen activityit ANDis wheneverdisabled for the active profileconnection.
  * Called on activity AND whenever the active profile changes, so each profile keeps its own independent idle clock.
 + * independent idle clock.
  */
 function scheduleIdleTimer() {
     clearIdleTimer();
     if (!armed || !isKeepaliveEnabledForActive()) {
         return;
+    }
     const timeoutMs = Math.max(60, Number(extension_settings[MODULE].timeoutSeconds) || 295) * 1000;

+}
 /**
 + * Real message/generation activity: arms keepalive for this tab session (if it wasn't already)
 + * and records the activity. Loading a chat's history does NOT call this.
 + */
 +function onChatActivity() {
 +    armed = true;
 +    markActivity();
 +}
++
 +/**
  * Fires a background ("quiet") generation against the active model to keep the
  * server-side prompt cache warm. The full prompt prefix (current chat context +
  * the keepalive message) is sent — which is what refreshes the cache — while the

  * deactivateSendButtons() reflects the busy state — and release both in `finally`.
  */
 async function fireKeepalive() {
     if (!armed || !isKeepaliveEnabledForActive()) {
         return;
+    }

     loadSettings();
     setupListeners();
     // Any chatA orreal message/generation activityarms keepalive for this tab session and counts as "using" the active profile.
 -    const activityEvents = [
 +    // active profile. (Keepalive stays dormant until the first one — see `armed`.)
 +    const activationEvents = [
         event_types.MESSAGE_SENT,
         event_types.MESSAGE_RECEIVED,
         event_types.GENERATION_STARTED,
         event_types.GENERATION_ENDED,
 -        event_types.CHAT_CHANGED,
     ];
     for (const event of activityEventsactivationEvents) {
         eventSource.on(event, markActivityonChatActivity);
+    }
 +    // Switching chats re-targets the per-profile idle clock but does NOT arm keepalive on its
 +    // own — opening/loading a chat is not proof that anything is cached server-side.
 +    eventSource.on(event_types.CHAT_CHANGED, markActivity);
++
     // When the active profile changes, re-target the idle timer at the new profile using
     // ITS own last-activity time (do NOT mark activity — switching is not using it).
     eventSource.on(event_types.CONNECTION_PROFILE_LOADED, scheduleIdleTimer);

public/scripts/extensions/keepalive/settings.html+1 -1 Viewed

             <label for="keepalive_message" data-i18n="ext_keepalive_message">Keepalive message</label>
             <input id="keepalive_message" class="text_pole" type="text" />
             <small data-i18n="ext_keepalive_help">After this many seconds without activity on the active connection profile, the current chat plus this message (sent as a hidden user message) is submitted to that profile to keep its server-side prompt cache warm. The completion is capped to a single token and is never saved to the chat. Sending is briefly locked while it runs. Only the profile you're currently using is pinged; each profile has its own idle timer. Keepalive stays off until you've sent at least one message since opening the tab (a freshly loaded chat isn't proof anything is still cached).</small>
             <hr>