Auth Methods (Tracking)

[benbrandt]

https://agentclientprotocol.com/rfds/auth-methods

#330
#588

[hancengiz]

I have a question about moving the whole auth methods to acp protocol. why?
If a acp client tool chooses to use ACP protocol only for chats, and have a settings page etc. to let users to activate that agent, we already have distribution methods, for example right after the user installs it, we can have an interactive activation as cmd convention (which could still be advertised by the agent inside the protocol via authMethods, but if there a convention like "acpagent --terminal-auth" I do not need to initialize an acp session just to learn how to activate the interactive terminal.

Why not just define that as a convention, and that can be advertised inside the protocol as well? Now I need to init an acp process and check if that particular ACP supports terminal authentication methods, even if they do. Also, I think all acp agents should support terminal interactive method as a MUST. The tool can choose to do OAuth, ask for manual key entry, or whatever they choose; at that point, the interface is with a human.

[benbrandt]

Not all agents use TUIs and also not all agents will be run locally in the future, so I think it is important to support more ways of authenticating and supporting a user experience around that