Support for device code auth#248
Conversation
| mode: "url", | ||
| // This should be the authenticate requestId, but this is not exposed by the ACP SDK. | ||
| // The elicitation still works, but won't be tied to the authenticate request. | ||
| requestId: null, |
There was a problem hiding this comment.
I don't think we can fill in the requestId here without support to expose it from the ACP SDK.
I think this is fine for now, but could we consider adding requestId to the AgentHandlerContext?
There was a problem hiding this comment.
Good catch, I think I missed that. Will see if I can add quickly
There was a problem hiding this comment.
There was a problem hiding this comment.
Thanks for that, I've bumped to the latest SDK and wired up requestId.
It touched a lot of things, since several operations attempt to auto-authenticate, so they all needed the requestId to be passed through..
85af2be to
bb3048b
Compare
bb3048b to
3d0cb83
Compare
|
@benbrandt Is there anything more you'd like to see before reviewing this? I've just rebased it onto the recent elicitation work, and I think it fits in pretty well. It's now also using your new Happy to make any tweaks, it would be great to get this device code auth support merged. |
This PR adds device code auth support for ChatGPT login when no browser is available. It is a re-implementation of zed-industries/codex-acp#291 for agentclientprotocol/codex-acp.
An
elicitation/completeisn't required, due to theAuthenticateResponsesent when authentication is complete (or an error if it failed).