Pre-submit Checks

• I have searched Warp bugs and there are no duplicates
• I have searched Warp known issues page and my issue is not there
• I have an issue with AI and have included the debugging ID (Optional, but helps expedite the AI quality fix). Debugging ID instructions
• I have technical issue and have included the logs (optional, but helps expedite the bug fix). Log instructions

Describe the bug

I am trying to use warp as port of our CI/CD, but I have to use my own keys (BYOK).
On a machine where I also have WARP client installed, it's fine, but on a headless machine, there is no way to set them.

Those keys are saved locally using the warp terminal only

To reproduce

try the oz-cli local agent with byok

Expected behavior

To use the agent profile and my BYOK when using oz-cli on a headless machine

Screenshots, videos, and logs

No response

Operating system (OS)

Linux

Operating system and version

Debian 11.2

Shell Version

No response

Current Warp version

No response

Regression

No, this bug or issue has existed throughout my experience using Warp

Recent working Warp date

No response

Additional context

No response

Does this block you from using Warp daily?

Yes, this issue prevents me from using Warp daily.

Is this an issue only in Warp?

Yes, I confirmed that this only happens in Warp, not other terminals.

Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e

None