# First launch — your project is instantly understood

Project Scanner found:
✅ Tech stack: Next.js 15, TypeScript, Tailwind CSS
✅ Database: Prisma + PostgreSQL
✅ Testing: Vitest + Playwright
✅ Deployment: Docker + GitHub Actions
✅ API style: REST with Zod validation

Git seeding found:
✅ 23 architectural decisions from recent commits
✅ Draft decisions created — review and confirm

.continuity/
├── decisions.json          # All your decisions
├── SESSION_HANDOFF.md      # Generated handoff context
└── embeddings.json         # Semantic search (Pro)

Everything is local JSON. Commit to git, share with team.

Your project is instantly understood

On first launch, the Project Scanner analyzes your codebase and creates draft decisions for your tech stack, dependencies, database, testing, deployment, API style, and project structure. Git seeding pulls decisions from your recent commit history.

• •Project Scanner creates draft decisions automatically
• •Git seeding pre-populates from recent history — sidebar is never empty
• •Everything stored locally as plain JSON in .continuity/
• •Commit to git and share with your team

# Verify it works — ask your AI:

You: "Do you have access to Continuity? Which memory
      tools or MCP profile are available here?"

AI:  "Continuity is connected in this client.
      I can see tools like:

      • log_decision — save architectural choices
      • search_decisions — semantic + keyword search
      • get_quick_context — load project history
      • update_session_notes — keep session context current
      • read_session_notes — recover the active thread

      Tool availability depends on the client and the
      active MCP profile. If Continuity is not mounted
      here, I should say so and fall back to repo-local
      context instead of pretending the tools are loaded."

✅ Working. Your AI either reports connected tools or
   honestly tells you it's in degraded mode.

If AI says "I don't have those tools yet":
→ Reload VS Code (Cmd+Shift+P → Reload Window)
→ Check Output panel (View → Output → Continuity)
→ Confirm the client supports workspace MCP

Verify it in 30 seconds

Ask your AI: "Do you have access to Continuity?" A healthy client should report the tools or profile it can see. If the MCP connection is degraded, it should say that and fall back to repo-local context instead of bluffing.

• •AI confirms access to key memory tools and may report the active MCP profile
• •If the client is degraded, it should say so and use repo-local Continuity files instead
• •Decision lifecycle: active, draft, outdated, deprecated, or superseded
• •If it doesn't work, reload VS Code or check the Output panel