Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mito AI: Restore chat on refresh #1488

Merged
merged 35 commits into from
Feb 10, 2025
Merged

Mito AI: Restore chat on refresh #1488

merged 35 commits into from
Feb 10, 2025

Conversation

ktaletsk
Copy link
Collaborator

@ktaletsk ktaletsk commented Jan 22, 2025

Description

  • Keep the full history (prompts, display messages, metadata) in the backend.
  • Move backend storage from memory to the disk (JSON or sqlite).
  • Create new websocket message types to receive the history.
  • Restore history when the extension loads.

Testing

  1. Start a new chat or explain code or debug error
  2. Refresh the browser page or close and reopen JupyterLab page

Documentation

N/A

@ktaletsk ktaletsk requested a review from aarondr77 January 22, 2025 03:35
Copy link

vercel bot commented Jan 22, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
monorepo ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 10, 2025 3:52pm

clear file when clearing history
mito-ai/mito_ai/handlers.py Outdated Show resolved Hide resolved
${input}`};
}

const removeInnerThoughtsFromMessage = (messageContent: string) => {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we're going to need this sort of post-processing code in the frontend for when we stream responses to the frontend.

rename variable from aiResponse to chatHistoryResponse
…hes specifically with that type of request and not all events that effect the history
@aarondr77 aarondr77 merged commit f529365 into dev Feb 10, 2025
57 of 59 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants