# Prototyper Chat starts new App Blueprint instead of continuing my existing app
**URL:** https://community.firebasestudio.dev/t/prototyper-chat-starts-new-app-blueprint-instead-of-continuing-my-existing-app/12400
**Category:** General
**Created:** [May 16, 2025, 2:52pm UTC](https://community.firebasestudio.dev/t/prototyper-chat-starts-new-app-blueprint-instead-of-continuing-my-existing-app/12400 "2025-05-16T14:52:13Z")
**Posts on this page:** 3
**Page:** 2
### Author:  [@Christopher\_Estep](https://community.firebasestudio.dev/u/Christopher_Estep)
#### Post date: [June 2, 2025, 9:57pm UTC](https://community.firebasestudio.dev/t/prototyper-chat-starts-new-app-blueprint-instead-of-continuing-my-existing-app/12400/22 "2025-06-02T21:57:31Z")
Where might I find a restore point? (sorry, newbie here)
---
### Author:  [@DaC](https://community.firebasestudio.dev/u/DaC)
#### Post date: [June 2, 2025, 10:13pm UTC](https://community.firebasestudio.dev/t/prototyper-chat-starts-new-app-blueprint-instead-of-continuing-my-existing-app/12400/23 "2025-06-02T22:13:13Z")
@Christopher_Estep take a look on these topics:
> [@Prototyper history gone, now what?](https://community.firebasestudio.dev/t/prototyper-history-gone-now-what/12354/16):
>
> access to the code backend Source Control tab … where you click to access Commit / Changes options this is also where your files waiting to commit/stage/changed will display The flow works like this: A file is edited = Changes (this gonna show on that section) Staged = when you mark a file that you believe is ready to commit Commit = Staged files will be grouped on a saved “Source Control Graph” which is your Commi…
> [@How-to Enabling Prototyper on Existing Project + Prototyper Full Context Clear](https://community.firebasestudio.dev/t/how-to-enabling-prototyper-on-existing-project-prototyper-full-context-clear/13781):
>
> Background: People trying to bring their existing project (local machine, github, other cloud, etc) realize they can’t use the prototyper interface, only the code view, which uses a different model. With time the prototyper context memory gets huge and this ends up causing some troubles: Slow Speeds Frequent VM locks (Infinite Loading - reset needed) Uncomplete interactions Reduced Context Precision Old code being randomly and frequently reintroduced Additional errors like exceeding input tok…
both have very detailed information on how to work with the backend from firebase studio where you’ll find things like the project’s backups (Source Control), terminal, etc.
---
### Author:  [@alfredo\_zarate](https://community.firebasestudio.dev/u/alfredo_zarate)
#### Post date: [June 3, 2025, 2:32am UTC](https://community.firebasestudio.dev/t/prototyper-chat-starts-new-app-blueprint-instead-of-continuing-my-existing-app/12400/24 "2025-06-03T02:32:58Z")
Tenía el mismo problema y me arriesgué y acepté el nuevo Prototyper y sólo cambióe el layout de mi aplicación y pude seguir dando instrucciones. Ahora el problemas es que la ventana de instrucciones se actualiza cuando la IA esta trabajando y se pierde todo. Vuelves a lanzar la instrucción y sigue actualizando la pantalla. No funciona los reinicios.
[Previous page](https://community.firebasestudio.dev/t/prototyper-chat-starts-new-app-blueprint-instead-of-continuing-my-existing-app/12400.md?page=1)