diff --git a/CHANGELOG.md b/CHANGELOG.md index 3800a35..5572b60 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -4,6 +4,10 @@ All notable changes to this project will be documented in this file. The format ## [Unreleased] +### Changed + +- [#202](https://github.com/mohanagy/miftah/issues/202) Made the Console task-first for returning users: validated MCP connections now lead the page and show their named account profiles, durable default, and whether live in-session switching through `miftah_use_profile` is available. The setup wizard remains directly reachable, while the authentication ownership matrix and trust-boundary reference are collapsed behind **How authentication works**. The Console still exposes only non-secret metadata, never inspects client settings or running MCP processes, and preserves the existing validation, redaction, audit, file-containment, and no-shell boundaries. External evaluator acceptance remains open and is not claimed by this change. + ## [0.5.4] - 2026-07-30 ### Changed diff --git a/src/console/console-assets.ts b/src/console/console-assets.ts index de59c8b..6f076db 100644 --- a/src/console/console-assets.ts +++ b/src/console/console-assets.ts @@ -40,42 +40,14 @@ const page = `
+

Only validated files in Miftah's standard configuration directory appear here. Client settings and running MCP processes are never inspected.

+
+ How authentication works +
+

Connection ownership

+

Know who owns authentication before you connect

+
+
+

Managed here

+

Remote native OAuth

+

Miftah discovers standards-based endpoints, opens consent, and stores tokens only in the OS vault.

+
+
+

Provider-owned login

+

Provider adapter

+

Miftah launches a pinned local adapter. The upstream owns browser login and its private token cache.

+
+
+

Manual setup

+

Upstream-owned auth

+

Use the provider's documented API key, credential file, or login flow. Miftah passes only configured references.

+
+
+

Not imported

+

Unsupported state

+

Passwords, browser cookies, and arbitrary third-party token caches are never accepted or scraped.

+
+
+

Trust boundary: Profiles and a generated client entry describe local configuration; they do not prove a credential works or belongs to the intended account. A reviewed safe check may establish readiness only where declared, and a configured identity probe is separate. Miftah policy and redacted audit protect the wrapper, not provider-side token scopes or retention.

+
+
+