A UI to see configured agents, available profiles and connections

[manojbajaj95]

Maybe we can add a UI that shows the different available profiles, available client ID secrets, and multiple connections that are available.

[manojbajaj95]

Brainstorming notes:

A UI makes sense, but it should stay aligned with authsome's core value prop: local, lightweight auth for agents. The first version should probably be a separate surface, not part of the default runtime path.

Suggested direction:

• Add an authsome ui experience as a local-only management console.
• Keep the default authsome install lightweight. The UI should be bundled as an extension/plugin or exposed through an optional dependency, e.g. authsome[ui].
• Do not require a frontend toolchain, web server framework, or heavier UI dependencies for users who only need CLI/library auth.
• Bind locally only, ideally 127.0.0.1, and treat the UI as an operator console rather than a hosted dashboard.
• Start read-mostly: profiles, providers, custom providers, connections, credential status, refresh errors, diagnostics.
• Allow safe actions later: login, logout, revoke current-profile credentials, set default profile, register/remove custom provider definitions.
• Keep all secrets redacted by default. The UI should show whether client IDs/secrets/API keys/tokens exist, not render their values.
• Be careful with the word "agents" until agents become first-class persisted objects. Today the real domain objects are profiles, providers, provider client config, and connections.

Recommended first cut:

• authsome remains CLI/library-first and lite by default.
• authsome-ui or authsome[ui] provides the local web console.
• The UI reads through existing authsome APIs rather than owning credential/storage logic.
• If/when the client-server architecture discussion moves forward, this UI can become the management surface for that architecture without forcing the base package to carry UI dependencies.

[ngaurav]

closing this as it is now implemented