Get help about CodeArchitect MCP features. Use when user says "use codearchitect" without specifying a feature, or asks "what can codearchitect do?". Returns available features with examples and next steps.

[CodeArchitect] Save important conversations for future reference.

=== WHEN TO USE ===

• User says: "use codearchitect store_session", "save this conversation", "store this", "remember this"

• User wants to keep/remember an important discussion

• After solving complex problems or making architecture decisions

=== STORAGE BEHAVIOR ===

1. ALWAYS saves to main folder: ~/.codearchitect/sessions/ (user's home directory)

2. OPTIONALLY saves to project folder if user specifies projectDir parameter

3. NEVER auto-detects project - only use projectDir if user explicitly provides it

=== CONVERSATION SOURCE (CHOOSE ONE) ===

OPTION 1: Export File (RECOMMENDED - Most Reliable)

• User exports conversation from Cursor/VS Code to .codearchitect/exports/ folder

• Tool automatically detects and processes the export file

• No need to manually extract conversation

WORKFLOW:

1. User exports chat: In Cursor/VS Code → three dots (⋯) → "Export Chat"

2. User saves to: ~/.codearchitect/exports/ folder (main location - always the same)

3. User says: "use codearchitect store_session"

4. Tool automatically finds newest export file and stores it

If multiple exports exist:

• Tool processes newest file (modified in last 10 minutes)

• If user wants specific file: use exportFilename parameter (e.g., "resolve_mcp")

OPTION 2: Direct Conversation Parameter (Fallback)

• Only use if export file method doesn't work

• Extract FULL conversation from your context window

• Format as plain text with USER/ASSISTANT markers OR JSON array

=== PARAMETERS ===

• conversation (optional): Direct conversation text/JSON - only use if export file unavailable

• exportFilename (optional): Pattern to match specific export file (e.g., "resolve_mcp" matches "cursor_resolve_mcp_configuration_issues.md")

• topic (optional): Session topic - auto-extracted if not provided

• projectDir (optional): Project directory path - if provided, saves to both main and project folders

• format (optional): "plain" or "messages" - default "plain"

=== WORKFLOW (EXPORT METHOD) === Step 1: User exports conversation to ~/.codearchitect/exports/ folder (main location) Step 2: User says "use codearchitect store_session" Step 3: Tool detects export file automatically from main exports folder Step 4: Tool parses and stores conversation Step 5: Tool saves to main sessions folder (always) + optionally project folder if projectDir specified

=== ERROR HANDLING === If no export file found:

• Return clear instructions with OS/IDE-specific export folder path

• Tell user exactly where to save the export file

• Provide step-by-step instructions

=== RESPONSE === After saving, return concise message:

• "Detected export file '[filename]', saved to main: [topic-name]. Next: use codearchitect get_session [topic-name]"

• Or if projectDir provided: "Detected export file '[filename]', saved to main: [topic-name] and project: [topic-name]. Next: use codearchitect get_session [topic-name]"

[CodeArchitect] Retrieve previous conversations to avoid re-explaining.

=== WHEN TO USE ===

• User says: "use codearchitect get_session", "get that previous conversation", "retrieve session"

• User mentions something they discussed before

• User wants to continue work on a previous topic

=== STORAGE BEHAVIOR ===

• Always retrieves from main folder: ~/.codearchitect/sessions/ (user's home directory)

• No project detection - all sessions are in main folder

=== USAGE ===

• No parameters: Lists all sessions

• filename: Get specific session by topic folder name

• date: List sessions from specific date (YYYY-MM-DD format)

• limit: Limit number of results when listing

[CodeArchitect] Search across all stored sessions to find relevant conversations.

=== WHEN TO USE ===

• User says: "use codearchitect search_session [query]", "search for [topic]", "find sessions about [topic]"

• User wants to find sessions by keyword or topic

• User remembers discussing something but not the exact session name

=== STORAGE BEHAVIOR ===

• Always searches in main folder: ~/.codearchitect/sessions/ (user's home directory)

• Searches through all date folders unless filtered

=== SEARCH BEHAVIOR ===

• Full-text search across topic, content, and messages

• Case-insensitive matching

• Returns relevance scores and context snippets

• Results sorted by relevance (highest first), then by date (newest first)

=== PARAMETERS ===

• query (required): Search query string

• date (optional): Filter by specific date (YYYY-MM-DD format)

• dateFrom (optional): Filter from date (YYYY-MM-DD format)

• dateTo (optional): Filter to date (YYYY-MM-DD format)

• limit (optional): Limit number of results returned

=== RESPONSE === Returns matching sessions with:

• Relevance score (0-1)

• Matched snippets showing context

• Match count

• Session metadata (topic, date, filename)