v0.11.1: Preserve hosted-client authorization through sign-in

Fixed

Hosted MCP clients can follow authorization redirects before opening the final URL in the owner's browser. The old redirect to a bare login URL could lose the session-bound consent request, so successful passkey login landed at grant management instead of returning to the client.

Angelos now renders sign-in at the validated authorization URL, allowing the actual browser to create its own session-bound request. Passkey verification, explicit consent, client/redirect validation, PKCE and CSRF protection remain required. No transfer token or arbitrary return URL was introduced.

Verification

Regression tests cover Claude and ChatGPT prefetch/browser handoff, enrollment and login through consent/PKCE callback, interrupted/expired sessions, retry/denial, cross-session rejection and open-redirect prevention. Full Go race/vet/build, Python and documentation checks passed. The production anonymous Claude authorization request returns sign-in directly at the authorization endpoint with no redirect and no-store caching. Actual owner consent remains an account-specific step.

Upgrade

No configuration or stored-state migration. Existing sessions, grants, keys and client settings remain intact. Close an old bare login/grants tab and restart Connect from your MCP client after deployment; a page that already lost its request cannot recover it.

Changelog: https://angelos.ashray.xyz/docs/changelog

v0.11.0: Client-neutral setup and security hardening

Highlights

• Full-capability agent-led setup with ChatGPT, Claude.ai, and other compatible MCP clients; each client has an independent owner-approved grant.
• Explicit gate-aware initial OAuth scopes; existing installations and grants are not silently elevated.
• Isolated OAuth quotas for proven sessions/grants, preserved credentials on rate denial, and immediate configured-client disabling. Fresh anonymous admission remains bounded; ingress abuse protection is still needed.
• Safe private signing-key generation, targeted source/deployment ignores, checksum-pinned full-history secret scanning, pinned Actions, and locked Vercel CLI tooling.
• Public upstream updates do not require a separate upstream PAT; existing updater compatibility and workflow-review safeguards remain.
• Dedicated release changelog, focused migration reference, and local native fonts without Google Fonts requests.
• Removed the optional personal email from LICENSE, preserving Apache-2.0 attribution.

Verification

Full Go race/coverage tests with disposable Redis, vet/build, 125 Python tests, 20-page documentation checks, locked Vercel CLI installation, and full source/history secret scans passed. Exact-commit CI and both production deployments were verified before publication.

Upgrade

Preserve your issuer, signing key, owner identity, Redis and existing environment. Existing grants keep their scopes. To configure new full-access connections explicitly, use the setup guide. Existing personal forks must review and manually sync workflow changes before their unattended updater continues.

Documentation

• Setup: https://angelos.ashray.xyz/docs/quickstart
• Changelog: https://angelos.ashray.xyz/docs/changelog
• Migration: https://angelos.ashray.xyz/docs/tool-migration

Validation limits

Live Claude owner consent and a separate teammate's automatic-update pilot are not established by protocol tests. The optional local virtual-passkey browser test could not launch because the execution environment denied browser Unix sockets. Provider/account policies still apply.

v0.10.0: Personal instances and agent-led provider setup

Highlights

• Personal-instance setup designed for coding agents, with a complete setup guide and repository-local setup skill.
• Opt-in daily fork updater for compatible tested releases: validation, safe fast-forward updates, staged Vercel deployment, and canonical health checks while retaining each instance's configuration, Redis and keys.
• iCloud and Yahoo secure IMAP/SMTP presets; existing Spacemail, Gmail/Workspace and custom TLS settings remain supported.
• Microsoft Outlook.com/Microsoft 365 Graph support for the primary mailbox, with delegated OAuth, account-bound references and encrypted persistent token renewal.
• Reviewed local Google and Microsoft consent helpers, private credential output, and intended-mailbox verification.

Verification

Full Go race/Redis tests, vet/build, 111 offline Python tests, documentation checks, independent security reviews, exact-commit CI, and both API/docs deployments passed. The existing Spacemail-to-AgentMail two-way loop passed, including attachment integrity and preservation of old drafts and send receipts.

Setup and updates

• Setup: https://angelos.ashray.xyz/docs/quickstart
• Automatic updates: https://angelos.ashray.xyz/docs/keep-updated
• Microsoft capabilities and restrictions: https://angelos.ashray.xyz/docs/microsoft

Existing instances need no mandatory configuration or stored-state migration. New provider connections require their documented credentials and approvals. The updater is opt-in and is not enabled merely by forking the repository; workflow changes, divergent forks and incompatible migrations stop for review.

Validation limits

New-provider authentication and enterprise eligibility remain account-specific; no live Microsoft, iCloud or Yahoo account or separate owner's hosted-updater pilot was exercised for this release. Tenant administrator policies still apply. Microsoft support is primary-mailbox-only, with unsupported advanced operations explicitly capability-gated.