Skip to content

⚡ Bolt: Eliminate N+1 query for thread emails - #666

Closed
schmug wants to merge 1 commit into
mainfrom
bolt-eliminate-n1-thread-query-939620729728047747
Closed

schmug wants to merge 1 commit into
mainfrom
bolt-eliminate-n1-thread-query-939620729728047747

Conversation

@schmug

@schmug schmug commented Jul 31, 2026

Copy link
Copy Markdown
Owner

💡 What: Replaced the sequential getEmail map bottleneck wrapped in a Promise.all with a single getFullThread call in workers/agent/index.ts.
🎯 Why: Reading a complete email thread is an N+1 query problem using the standard DO stubs. For an AI agent building prompt context from thread history, this query overhead introduces significant latency.
📊 Impact: Consolidates thread loading to two optimized SQL queries inside the Durable Object.
🔬 Measurement: Verify agent thread context latency drops, tests continue to pass.


PR created automatically by Jules for task 939620729728047747 started by @schmug

Co-authored-by: schmug <38227427+schmug@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown

👋 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 @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jul 31, 2026

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Updated (UTC)
✅ Deployment successful!
View logs
agentic-inbox f35ef60 Jul 31 2026, 05:40 AM

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jul 31, 2026

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
ais-hub f35ef60 Commit Preview URL

Branch Preview URL
Jul 31 2026, 05:39 AM

@schmug

schmug commented Aug 23, 2026

Copy link
Copy Markdown
Owner Author

Closing as superseded by #658.

This is one of 7 re-derivations of the same agent thread-fetch change, opened by a Jules persona that has since been paused. #658 is the one kept open: it collapses the fetch to a single Durable Object call and removes the now-unused EmailMetadata import. Every variant edits .jules/bolt.md, so only one can land without conflict.

@schmug schmug closed this Aug 23, 2026
@google-labs-jules

Copy link
Copy Markdown

Closing as superseded by #658.

This is one of 7 re-derivations of the same agent thread-fetch change, opened by a Jules persona that has since been paused. #658 is the one kept open: it collapses the fetch to a single Durable Object call and removes the now-unused EmailMetadata import. Every variant edits .jules/bolt.md, so only one can land without conflict.

Understood. Acknowledging that this work is superseded by #658 and stopping work on this task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant