skip registering secure_storage for remote daemon

[moirahuang]

Description

Here's the original issue report: #12449

The issue is because of our dependency on secure storage, which has platform specific implementations so on Linux it uses SecretService which results in the reported lock issue. We technically don't need it for the remote daemon case because we handle auth in thehandshake, we are just incidentally using it right now during daemon setup so I'm skipping it for the remote daemon case.

Linked Issue

#12449

• The linked issue is labeled ready-to-spec or ready-to-implement.
• Where appropriate, screenshots or a short video of the implementation are included below (especially for user-visible or UI changes).

Testing

• 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

[moirahuang]

• skip registering secure_storage for remote daemon #12479 👈 (View in Graphite)
• master

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

[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 skips platform secure-storage registration for RemoteServerDaemon launch mode and registers an intentionally unavailable provider that avoids persistent secret access while allowing daemon auth to arrive through the remote-server handshake.

Concerns

• No blocking correctness, security, or spec-alignment concerns found in the changed 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