vibn-frontend/TODO_CHATGPT_IMPORT.md

ChatGPT Import - Issues to Fix

🐛 Current Problem

ChatGPT conversation import is not working when trying to import conversations from GPT projects.

📋 Test Case

URL Format:

https://chatgpt.com/g/g-p-68f85b531c748191a9e23a50e5ae92c0-ai-first-emr/c/68fc09e6-372c-8326-8bd3-6cbf23df44aa

Expected:

• Extract conversation ID: 68fc09e6-372c-8326-8bd3-6cbf23df44aa
• Import conversation via OpenAI Conversations API

Actual:

• Import is failing (error unknown - needs debugging)

---

🔍 Things to Check Tomorrow

1. Test Regex Extraction

Add console logging to verify the conversation ID is being extracted correctly:

const { id: conversationId, isShareLink } = extractConversationId(conversationUrl);
console.log('🔍 Extracted ID:', conversationId);
console.log('🔍 Is Share Link:', isShareLink);

2. Test OpenAI API Call

Verify the /api/chatgpt/import endpoint is receiving the correct data:

• Is the conversation ID correct?
• Is the OpenAI API key valid?
• What error is OpenAI returning?

Check server logs for the actual error from OpenAI.

3. Verify OpenAI API Key Permissions

The stored OpenAI API key might not have access to the Conversations API:

• Check if the key has the right scopes
• Try with a fresh API key from https://platform.openai.com/api-keys

4. Test Different URL Formats

Try importing:

• Standard conversation: https://chatgpt.com/c/[id]
• GPT conversation: https://chatgpt.com/g/g-p-[gpt-id]/c/[conv-id] ← Your format
• Old format: https://chat.openai.com/c/[id]

5. Check Browser Console

Look for:

• Network errors in the import request
• Response body from the API
• Any JavaScript errors

6. Possible API Limitations

The OpenAI Conversations API might:

• Not support GPT project conversations (different API endpoint?)
• Require different authentication for project-scoped conversations
• Have been deprecated or changed

---

🛠️ Files to Debug

1. Frontend Component:

   • /Users/markhenderson/ai-proxy/vibn-frontend/components/chatgpt-import-card.tsx
   • Line 72-116: extractConversationId() function
   • Line 175-217: Conversation import logic

2. Backend API:

   • /Users/markhenderson/ai-proxy/vibn-frontend/app/api/chatgpt/import/route.ts
   • Check what error OpenAI is returning

3. Test the API Directly:

   curl https://api.openai.com/v1/conversations/68fc09e6-372c-8326-8bd3-6cbf23df44aa \
     -H "Authorization: Bearer sk-YOUR-KEY"
   

---

📚 What's Built So Far

✅ Working:

1. OpenAI Platform Projects API - /api/openai/projects
2. Standard ChatGPT Conversation Import (theoretically, needs testing)
3. Regex patterns for all URL formats (including GPT project conversations)
4. UI with tabs (Chat, GPT, Project)

❌ Not Working:

1. Actual conversation import from GPT projects ← Main issue
2. Custom GPT import (started but incomplete)

🤷 Unknown:

• Does OpenAI's Conversations API support GPT project conversations?
• Is there a different API endpoint for GPT-scoped conversations?

---

🎯 Quick Debug Commands for Tomorrow

In browser console:

// 1. Test conversation ID extraction
const testUrl = "https://chatgpt.com/g/g-p-68f85b531c748191a9e23a50e5ae92c0-ai-first-emr/c/68fc09e6-372c-8326-8bd3-6cbf23df44aa";
const match = testUrl.match(/chatgpt\.com\/g\/g-p-[a-zA-Z0-9-]+\/c\/([a-zA-Z0-9-]+)/);
console.log('Extracted ID:', match ? match[1] : 'NO MATCH');

// 2. Test API call directly
const token = await firebase.auth().currentUser.getIdToken();
const response = await fetch('/api/chatgpt/import', {
  method: 'POST',
  headers: {
    'Authorization': `Bearer ${token}`,
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    conversationId: '68fc09e6-372c-8326-8bd3-6cbf23df44aa',
    openaiApiKey: 'YOUR-KEY-HERE'
  })
});
const result = await response.json();
console.log('API Response:', result);

---

💡 Alternative Approach

If OpenAI Conversations API doesn't support GPT project conversations, consider:

1. Manual export: Ask user to export conversation as JSON from ChatGPT
2. Screen scraping: Use a browser extension to capture conversation data
3. OpenAI Plugin/Action: Build a custom GPT action to send data to Vibn

---

🚀 Next Steps Tomorrow

1. Add detailed logging to both frontend and backend
2. Test the import with a simple conversation first (not from a GPT project)
3. Check OpenAI API documentation for GPT conversation access
4. If API doesn't support it, pivot to alternative approach

---

Last Updated: $(date) Status: ❌ Blocked - Import not working Priority: High