When authenticating with a remote MCP server, exxperts currently registers itself as "Pi Coding Agent". This name can appear on the provider's authorization screen.
The value comes from the default OAuth client metadata in pi-mcp-adapter. exxperts already rebrands the adapter's callback pages and UI text in scripts/patch-mcp-adapter.mjs, but the external metadata still uses Pi's name and repository URL.
Could exxperts send its own identity by default?
client_name: exxpertsclient_uri: https://github.com/EXXETA/exxperts
Pi attribution belongs in the documentation and NOTICE file. The OAuth client connecting to an external service is exxperts.
When authenticating with a remote MCP server, exxperts currently registers itself as "Pi Coding Agent". This name can appear on the provider's authorization screen.
The value comes from the default OAuth client metadata in
pi-mcp-adapter. exxperts already rebrands the adapter's callback pages and UI text inscripts/patch-mcp-adapter.mjs, but the external metadata still uses Pi's name and repository URL.Could exxperts send its own identity by default?
client_name:exxpertsclient_uri:https://github.com/EXXETA/exxpertsPi attribution belongs in the documentation and NOTICE file. The OAuth client connecting to an external service is exxperts.