⚡ Bolt: Skip redundant state updates for terminal sessions - #87
⚡ Bolt: Skip redundant state updates for terminal sessions#87google-labs-jules[bot] wants to merge 1 commit into
Conversation
Skip unnecessary API polling and database writes when sessions reach terminal states (completed/failed). This reduces redundant network requests in the CLI and prevents unnecessary Supabase calls in the web API while preserving required summary polling.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
💡 What: Added conditionals to skip
buildAdapter(vendor).getStatus()andstore.upsert()for terminal states in the CLI (status.ts). In the Web API (sessions/route.tsandsessions/[id]/route.ts), we still poll forsummary, but we skippatchSession()database writes if the state and timestamp haven't changed.🎯 Why: PolyAgent frequently polls session statuses to update the UI/CLI. When a session reaches a terminal state (
completedorfailed), its status won't change. Polling external endpoints (for the CLI) and continuously rewriting the exact same state to the DB (for the web) burns unnecessary network I/O, database writes, and latency.📊 Impact: Completely eliminates external API network polling in the CLI for completed/failed sessions. Drastically reduces database write operations (
patchSession) in the Web API by only updating when the state actually mutates.🔬 Measurement: Watch the network and database calls in the Supabase logs or proxy layer when the dashboard is open with completed sessions. The number of active DB patches will drop to zero for those rows.
PR created automatically by Jules for task 12314708591583464460 started by @parvezk