Greptile Overview

Greptile Summary

This PR enhances the internal authentication system and fixes knowledge base document uploads by propagating user context through the entire processing pipeline.

Key Changes

• Internal Auth Enhancement: Modified generateInternalToken() and verifyInternalToken() to support optional userId in JWT payload, changing verification from returning a boolean to returning an object with {valid, userId?}
• KB Upload Fix: Added userId and workspaceId parameters throughout the document processing pipeline (processDocument, parseDocument, handleFileForOCR, etc.) to ensure proper metadata tracking when uploading files to storage
• Mistral Parser Fix: Fixed URL validation bug by converting relative paths to absolute URLs before validation, and included userId when generating internal tokens for API calls
• Updated Timestamp: Knowledge base updatedAt field now increments when documents are added via the knowledge block

Impact

All workflow routes now properly handle the new verification response structure, and knowledge base uploads will correctly track user and workspace ownership for files uploaded to cloud storage.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The changes are well-structured and consistent throughout the codebase. The auth signature change is backwards-compatible (boolean to object with .valid property), all call sites have been updated, and the parameter threading through document processing maintains proper typing
• No files require special attention

Important Files Changed

File Analysis

Sequence Diagram

sequenceDiagram
    participant Client
    participant API as API Route
    participant Auth as Internal Auth
    participant DocProcessor as Document Processor
    participant Mistral as Mistral Parser
    participant Storage as Storage Service
    
    Note over Client,Storage: Enhanced Internal Auth Flow
    
    Client->>API: Request with Bearer token
    API->>Auth: Verify internal token
    Auth-->>API: Return validation result
    Note over API: Extract user from token payload
    
    Note over Client,Storage: Knowledge Base Upload Flow
    
    Client->>API: Upload document to KB
    API->>DocProcessor: Process with context parameters
    DocProcessor->>Storage: Upload file with metadata
    Note over Storage: Store metadata with context
    Storage-->>DocProcessor: Upload successful
    
    DocProcessor->>Mistral: Parse PDF if needed
    Note over Mistral: Detect internal route
    Mistral->>Auth: Request new token
    Auth-->>Mistral: Provide token
    Mistral->>Mistral: Call internal API
    Note over Mistral: Context preserved in chain
    Mistral-->>DocProcessor: Return parsed content
    
    DocProcessor-->>API: Processing complete
    API-->>Client: Success

_{7 files reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}