[1/5] [Remote codebase indexing] pass embedding configs through

[moirahuang]

Description

Passing embedding configs through for remote codebase indexing

Also made a small update to the refresh icon for remote envs to distinguish when there's already an index vs. when we need to create an index

Testing

Added unit tests + locally tested

• I have manually tested my changes locally with ./script/run

Screenshots / Videos

Agent Mode

• Warp Agent Mode - This PR was created via Warp's AI Agent Mode

[oz-for-oss]

@moirahuang

I'm starting a first review of this pull request.

You can view the conversation on Warp.

I completed the review and no human review was requested for this pull request.

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

[oz-for-oss]

Overview

This PR threads the embedding configuration through remote codebase indexing status/proto conversions, uses it when constructing the remote search context, and separates request-vs-resync actions for remote index refreshes in settings.

Concerns

• No blocking correctness or security concerns found in the reviewed diff.

Verdict

Found: 0 critical, 0 important, 0 suggestions

Approve

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

[kevinyang372]

On a high-level, does this need to pass through proto? The client gets the embedding config through the server anyway. So the remote server binary should be able to do the same no?

[moirahuang]

• [5/5] Handle remote codebase auto-index follow-ups #11092
• [4/5] Add remote codebase incremental sync #11094
• [3/5] Reduce duplicate remote codebase index status pushes #11093
• [2/5] remote codebase indexing telemetry #10985
• [1/5] [Remote codebase indexing] pass embedding configs through #10981 👈 (View in Graphite)
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.