AI Passport — Roadmap

Standard first, then ecosystem. See MANIFESTO.md.

Phase 0 — Foundation ✓

• Mission, vision, manifesto, specification
• JSON schema
• Core: Passport, Vault, Identity, Permission, PassportManager

Phase 1 — Core ✓

• Passport creation, encryption, validation
• CLI (init, info, grant, revoke, export, show)
• Git plugin (plugin run git)
• MCP server (mcp serve)
• npm publish @ai-passport-core/cli
• GitHub repository

Phase 2 — Cursor integration ✓

First real user experience — the “wow” moment.

• MCP adapter + grant flow
• End-to-end Cursor test → CURSOR_SETUP.md
• Auto-discovery UX polish (get_passport_status, MCP startup hints)
• First-time onboarding flow (ai-passport onboard)

Scenario:

Cursor opened → Passport found → AI knows your stack → AI adapts

Phase 3 — SDK ✓

Nobody should rewrite AI Passport. Just:

import { Passport } from '@ai-passport-core/cli/sdk';

const passport = await Passport.load();
const context = await passport.export('cursor');

See SDK.md. Low-level API remains PassportManager for advanced use.

Future: optional separate @ai-passport-core/sdk npm package (same API, lighter deps).

• @ai-passport-core/sdk workspace package → packages/sdk/ (Phase 5)

Phase 4 — Open specification ✓

Documentation over code. Companies should say: “We support AI Passport.”

• Public spec index → SPECIFICATION.md
• Compatibility checklist → COMPATIBILITY.md
• RFC process → RFC.md
• Hosted spec site → index.md (GitHub Pages: /docs on main)

Phase 5 — Ecosystem (in progress)

• Ecosystem overview → ECOSYSTEM.md
• VS Code consumer guide → VSCODE_SETUP.md
• Sign in with AI Passport (draft) → SIGN_IN.md
• Sign in with AI Passport (implementation) → authorize, token exchange
• Cloud sync (optional, E2E encrypted) — file provider ✓ v0.1.5; HTTP provider TBD
• VS Code extension package → extensions/vscode/
• VS Code extension Marketplace publish → mendocan.ai-passport