feat: browseros API

[DaniAkash]

Integrates browser os to API to sync conversation history

[greptile-apps]

Greptile Overview

Greptile Summary

This PR integrates BrowserOS API to enable conversation history sync and user authentication. The implementation adds magic link and Google OAuth login, bidirectional sync for conversations, LLM providers, and scheduled tasks.

Key Changes:

• Authentication system using better-auth with magic link and Google OAuth
• GraphQL client infrastructure with typed documents and React Query hooks
• Real-time conversation sync when logged in, local storage fallback when logged out
• Bidirectional sync for LLM providers and scheduled jobs with conflict resolution
• Chat history UI switches between remote and local data based on login status

Issues Found:

• Performance bottleneck: All sync operations use sequential GraphQL calls in loops instead of parallel execution
• useConversations hook triggers excessive uploads due to unstable conversations dependency
• Multiple watchers and sync operations could cause race conditions under rapid changes

The architectural approach is sound - proper separation between local/remote storage, graceful degradation for offline users, and good error handling with Sentry. However, the sequential network operations will cause poor UX for users with many conversations, providers, or scheduled jobs.

Confidence Score: 3/5

• Safe to merge but will have performance issues for users with large datasets
• Core functionality is correct and well-structured with proper error handling, but sequential GraphQL operations in loops will cause significant performance degradation for users with many conversations/providers/schedules. The excessive re-render triggering in conversationStorage could also cause unnecessary API load.
• apps/agent/lib/conversations/uploadConversationsToGraphql.ts, apps/agent/entrypoints/sidepanel/index/useRemoteConversationSave.ts, apps/agent/lib/schedules/syncSchedulesToBackend.ts, apps/agent/lib/llm-providers/uploadLlmProvidersToGraphql.ts - all need parallel execution patterns

Important Files Changed

Filename	Overview
apps/agent/lib/graphql/execute.ts	creates GraphQL client with error handling and credential inclusion
apps/agent/lib/conversations/uploadConversationsToGraphql.ts	uploads local conversations to backend with batching and deduplication
apps/agent/entrypoints/sidepanel/index/useRemoteConversationSave.ts	manages real-time conversation sync to backend with message deduplication
apps/agent/entrypoints/sidepanel/index/useChatSession.ts	integrates remote conversation saving and restoring for logged-in users
apps/agent/lib/llm-providers/uploadLlmProvidersToGraphql.ts	syncs LLM provider configs to backend excluding sensitive fields
apps/agent/lib/schedules/syncSchedulesToBackend.ts	bidirectional sync of scheduled jobs with conflict resolution
apps/agent/entrypoints/background/index.ts	adds sync setup on session changes for providers and schedules
apps/agent/lib/conversations/conversationStorage.ts	adds upload on login but triggers excessively due to unstable dependencies

Sequence Diagram

sequenceDiagram
    participant User
    participant Extension
    participant AuthClient
    participant BrowserOSAPI
    participant SessionStorage
    participant LocalStorage
    
    Note over User,LocalStorage: Authentication Flow
    User->>Extension: Open login page
    Extension->>AuthClient: signIn.magicLink(email)
    AuthClient->>BrowserOSAPI: POST /auth/magic-link
    BrowserOSAPI-->>User: Send magic link email
    User->>BrowserOSAPI: Click magic link
    BrowserOSAPI-->>AuthClient: Set session cookie
    AuthClient->>SessionStorage: Save session info
    Extension->>Extension: Navigate to /home
    
    Note over User,LocalStorage: Conversation Sync Flow
    User->>Extension: Send message
    Extension->>Extension: Generate conversation
    Extension->>SessionStorage: Check login status
    alt User logged in
        Extension->>BrowserOSAPI: POST /graphql (CreateConversation)
        BrowserOSAPI-->>Extension: Conversation created
        Extension->>BrowserOSAPI: POST /graphql (AppendMessage)
        BrowserOSAPI-->>Extension: Message saved
    else User not logged in
        Extension->>LocalStorage: Save conversation locally
    end
    
    Note over User,LocalStorage: Initial Sync on Login
    SessionStorage->>Extension: Watch session change
    Extension->>LocalStorage: Read local conversations
    Extension->>BrowserOSAPI: POST /graphql (GetProfileId)
    BrowserOSAPI-->>Extension: Profile ID
    loop For each conversation
        Extension->>BrowserOSAPI: POST /graphql (ConversationExists)
        BrowserOSAPI-->>Extension: Check result
        alt Conversation exists
            Extension->>BrowserOSAPI: POST /graphql (GetUploadedMessageCount)
            BrowserOSAPI-->>Extension: Message count
        else New conversation
            Extension->>BrowserOSAPI: POST /graphql (CreateConversation)
        end
        Extension->>BrowserOSAPI: POST /graphql (BulkCreateMessages)
        BrowserOSAPI-->>Extension: Messages uploaded
    end
    Extension->>LocalStorage: Remove uploaded conversations
    
    Note over User,LocalStorage: LLM Providers & Schedules Sync
    Extension->>LocalStorage: Watch providers/schedules
    Extension->>BrowserOSAPI: POST /graphql (SyncProviders)
    Extension->>BrowserOSAPI: POST /graphql (SyncSchedules)
    BrowserOSAPI-->>Extension: Sync complete
    
    Note over User,LocalStorage: History Retrieval
    User->>Extension: Open chat history
    Extension->>SessionStorage: Check login status
    alt User logged in
        Extension->>BrowserOSAPI: POST /graphql (GetConversations)
        BrowserOSAPI-->>Extension: Remote conversations
        Extension->>User: Display remote history
    else User not logged in
        Extension->>LocalStorage: Read conversations
        Extension->>User: Display local history
    end

Loading

[greptile-apps]

_{6 files reviewed, 2 comments}

_{Edit Code Review Agent Settings | Greptile}

[DaniAkash]

@greptileai

[greptile-apps]

_{8 files reviewed, 6 comments}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

sequential GraphQL mutations in loop - creates network waterfall

use Promise.allSettled() to execute all provider updates in parallel

Prompt To Fix With AI

This is a comment left during a code review.
Path: apps/agent/lib/llm-providers/uploadLlmProvidersToGraphql.ts
Line: 65:120

Comment:
sequential GraphQL mutations in loop - creates network waterfall

use `Promise.allSettled()` to execute all provider updates in parallel

How can I resolve this? If you propose a fix, please make it concise.

[claude]

Code Review

I found 3 issues that need attention:

1. Missing useEffect import in AuthProvider.tsx

Location: apps/agent/lib/auth/AuthProvider.tsx:1

useEffect is used on line 9 but not imported, which will cause a runtime error (ReferenceError: useEffect is not defined).

Current:

import type { FC, PropsWithChildren } from 'react'

Fix:

import { useEffect, type FC, type PropsWithChildren } from 'react'

---

2. Incorrect import path in CLAUDE.md example

Location: apps/agent/CLAUDE.md:76

The import path in the example code is incorrect and will cause a module not found error.

Current:

import { graphql } from '~/graphql/gql'

Should be:

import { graphql } from '@/generated/graphql/gql'

The correct import path is @/generated/graphql/gql as used throughout the codebase. See chatHistoryDocument.ts for reference.

---

3. Incorrect import path in CLAUDE.md example

Location: apps/agent/CLAUDE.md:80

The import path in the example code is incorrect and will cause a module not found error.

Current:

import { getQueryKeyFromDocument } from '@/modules/graphql/getQueryKeyFromDocument'

Should be:

import { getQueryKeyFromDocument } from '@/lib/graphql/getQueryKeyFromDocument'

The /modules/ directory does not exist in the codebase. The correct path is @/lib/graphql/getQueryKeyFromDocument. See ProfilePage.tsx for correct usage.