Skip to content

Add CIMD auth & discovery plan#6

Open
Mark-Life wants to merge 4 commits intomainfrom
docs-cimd-auth-plan
Open

Add CIMD auth & discovery plan#6
Mark-Life wants to merge 4 commits intomainfrom
docs-cimd-auth-plan

Conversation

@Mark-Life
Copy link
Copy Markdown
Owner

Summary

  • Research doc on CIMD (Client ID Metadata Documents) for zero-registration OAuth2
  • Covers: current state, target flow, CIMD spec details, what needs to change across all packages/apps
  • Includes implementation order, security considerations, and 7 open questions

Context

Moving from API key auth to OAuth2 + CIMD so users can connect apps by just pasting a URL — no API keys, no pre-registration.

No code changes

Doc only (docs/cimd-auth-plan.md). Review for correctness and answer open questions before implementation.

🤖 Generated with Claude Code

Research doc covering OAuth2 + CIMD flow for zero-registration auth between chat and tasks apps.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@vercel
Copy link
Copy Markdown

vercel bot commented Mar 6, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
open-tools-web Ready Ready Preview, Comment Mar 7, 2026 10:46am

- Decision: use WorkOS AuthKit instead of custom OAuth2 AS
- Add WorkOS integration details (JWKS verification, metadata endpoints)
- Resolve open questions (auth format, scopes, backward compat, HTTPS)
- Update implementation order to reflect WorkOS approach
- Add new open questions (pricing, deployment model, standalone connect)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- WorkOS free tier: 1M MAU, sufficient
- WorkOS-hosted login (simplest path)
- Chat app on Vercel, OAuth state in encrypted cookies
- LLM API keys in localStorage with warning + clear button

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Chat app: no user accounts, no server-side state
- All per-user data in localStorage (LLM key, connections, OAuth tokens)
- Server is stateless proxy: receives tokens per-request, fetches tools, calls LLM
- Document why server-side fetch needed (CORS), OAuth callback flow, multi-user isolation

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant