2358 results found

1. Add an option to open a project directly in code view

   There is no option in Firebase studio, to open a project directly in code view. If you wish to do so, first you have to click on a project, opens in prototyper mode, but then you have to quickly switch to code view.

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. beautiful landing pages

   should be able to make top tier beautiful landing pages... would truly disrupt an entire category of business and provide a huge convenience for entrepreneurs.

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Support Markdown format for release notes files

   When attaching release notes to a release using App Distribution, it would be great if Markdown files were supported and rendered (release emails, inside the Tester app, in the Console, etc).

   36 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  App Distribution  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Firebase is good for developers but it is very complicated for beginners.

   This platform is good for developers but it is very complicated for beginners because in this app can be developed in simple language but running the functions of the app, creating flows, integration, and many such tasks are very difficult to do and understanding the console becomes very difficult due to which one cannot develop apps as per his idea and in this I want that making both apps and websites should be very easy, everything should be done easily, just with simple instructions, in integration right now 'Rocket.new' and 'emergency' compete with Firebase to a great extent because their interface becomes simple and easy for anyone Also for beginners and I want that anyone can create and prepare their dream platform in simple prompts or text and this platform provides free programs so more people will like to use it and I want that the option of uploading on any store from here should be made more easy and its interface should be such that even a 10 year old child can create and prepare his platform and the fee that has to be paid for uploading it on any platform store should be commission based so that users will not have to pay in advance and more and more users will use it, this will increase the revenue a lot and earn many times more than the one time fee from a single user This can be done which will attract more users. Thank you, I just want to share this idea because whatever problems I had to face, I shared it with you in the form of an idea, it will be of great help to you.

   This platform is good for developers but it is very complicated for beginners because in this app can be developed in simple language but running the functions of the app, creating flows, integration, and many such tasks are very difficult to do and understanding the console becomes very difficult due to which one cannot develop apps as per his idea and in this I want that making both apps and websites should be very easy, everything should be done easily, just with simple instructions, in integration right now 'Rocket.new' and 'emergency' compete with Firebase to a great extent because their… more

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Support geographic area and proximity searches with PostGIS

   Add GeoPoint and GeoBox scalar types and enable rich geo searching queries including indexing, "search within area", "find closest to point within radius", etc.

   43 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   5 comments  ·  Data Connect  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. نجوى أمام
   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  App Check  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Firebase studio to support source code in google drive.

   That's when it would start feeling like VSCode. I would even go further and suggest, all the gcp artifacts could reside on my google drive folder hierarchy.

   1. source code files
   2. artifact registry
   3. infra automation code
   4. static hosting files.
   5. Resource usage and billing on google sheets.

   If that's a big ask, provide a way to map the above GCP resources as a google drive.

   It gives so much comfort that all is in my drive and I can search/copy/paste with file explorer !!

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Google remote desktop instead of vnc

   I think using google remote desktop instead of vnc will not only work better but also be less laggy, that is one of the biggest reazons i dont move for windows, google remote desktop is just better than other alternatives, and i dont understand why google, being the creator of that tecnology does not implement it.

   8 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. There is an error when creating multiple applications.

   Hi Firebase Studio team and community,

   I'm running into an error when trying to create multiple applications in the platform.
   It seems like there's a limit that's causing this issue, and I have to reach out manually to request more.
   This is a bit frustrating for power users could this be fixed by introducing a paid tier for additional apps or an auto-billing option to unlock more without the hassle?

   Thanks for considering this! Firebase Studio is still the best app builder I've used.

   Best,
   Thanks
   Ryan

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  App Hosting  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. ATS Greens

    Visit the official ATS Greens website to explore verified prices, floor plans, and offers. Buy your luxury apartment in Noida directly from the developer. More Info: https://www.atsgreens.com/

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Crashlytics  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Firebase Studio needs to have revertable checkpoints after every Gemini edit
    8 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Firebase storage rules: Support for multi-database lookup

    This is a documented limitation and as such not an idea, but putting it out here to see if it get vote-traction. See the warning at the bottom of the page here:

    https://firebase.google.com/docs/storage/security/rules-conditions

    As of Feb. 25. 2025 it says

    "Warning: Storage Rules can only access documents from the default Cloud Firestore database when multiple databases are active."

    We have a project where we're doing tenant partitioning in both Firestore and firebase storage. The primary reason for creating separate buckets and databases is to be able to have storage in different customer preferred regions, and to achieve other isolations which are beneficial (backup/restore recovery scenarios etc.).

    Most files in firebase storage are protected by security rules that look up a document from the firestore database and checks access using a fairly standard acl scheme.

    This does not work unfortunately in a multi-db setup, which prevent this type of acl based storage security rules.

    I've not found any workarounds except an approach there the storage object Ids are long unique Ids that can't be "guessed" or brute force generated to look up an object in storage, but this is not as clean as being able to explicitly check access rights (and other logic on top of that using the rules language).

    The fact that it works in single/default db makes it feel like a significant takeback that the security design has the by changed when introducing multiple databases to the project.

    I think this is a common case for solutions doing tenant separation where there is a need to have objects in storage protected by acls.

    This is a documented limitation and as such not an idea, but putting it out here to see if it get vote-traction. See the warning at the bottom of the page here:

    https://firebase.google.com/docs/storage/security/rules-conditions

    As of Feb. 25. 2025 it says

    "Warning: Storage Rules can only access documents from the default Cloud Firestore database when multiple databases are active."

    We have a project where we're doing tenant partitioning in both Firestore and firebase storage. The primary reason for creating separate buckets and databases is to be able to have storage in different customer preferred regions, and to achieve other isolations which… more

    10 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Cloud Storage for Firebase  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. attaching a google doc

    I wrote my entire req in a google doc and i can't attach it. It's easier to write in a google doc than in the prompt box.

    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Create a 'cookbook' tutorial about adding 'Firebase Authentication' to 'Google AI Studio' apps

    Problem/Goal

    Developers using Google AI Studio to build custom AI applications (especially those moving beyond prototyping) need a straightforward, secure way to manage user accounts and access control. Integrating a robust authentication system like Firebase Authentication is the standard solution, but connecting it specifically to an AI Studio-powered backend or frontend can involve several tricky, undocumented steps.

    Suggested Feature/Content

    Create a "Cookbook" Tutorial (a detailed, step-by-step guide) that specifically focuses on the end-to-end implementation of Firebase Authentication for AI Studio applications.

    Key 'Recipes' (Sections) to Include

    Recipe 1: Firebase Project Setup

    Initialize a new Firebase project and enable a common authentication method (e.g., Email/Password or Google Sign-In).

    Securely store API keys and configuration settings.

    Recipe 2: Frontend Integration (Web/React)

    Implementing sign-up/login/logout UI components using the Firebase SDK.

    Managing the user's authentication state.

    Recipe 3: Secure AI Backend Communication

    The crucial step: Using the frontend's Firebase ID Token to make a secure, authenticated request to the backend (e.g., a Google Cloud Function or Cloud Run service hosting the AI Studio code).

    Verifying the ID Token on the backend to confirm the user's identity and grant access to the AI model call.

    Recipe 4: Role-Based Access Control (Optional)

    Adding custom claims to a Firebase user token to implement simple tiers (e.g., 'Free Tier' vs. 'Premium Tier' access to different models or rate limits).

    Expected Benefits

    Accelerates Development: Provides a "copy-and-paste" blueprint, lowering the barrier to entry for building production-ready, multi-user AI applications.

    Improves Security: Encourages developers to use best practices for token-based authentication from the start.

    Showcases Integration Power: Highlights the seamless connectivity between Google's developer tools (Firebase, AI Studio, Google Cloud).

    Problem/Goal

    Developers using Google AI Studio to build custom AI applications (especially those moving beyond prototyping) need a straightforward, secure way to manage user accounts and access control. Integrating a robust authentication system like Firebase Authentication is the standard solution, but connecting it specifically to an AI Studio-powered backend or frontend can involve several tricky, undocumented steps.

    Suggested Feature/Content

    Create a "Cookbook" Tutorial (a detailed, step-by-step guide) that specifically focuses on the end-to-end implementation of Firebase Authentication for AI Studio applications.

    Key 'Recipes' (Sections) to Include

    Recipe 1: Firebase Project Setup

    Initialize a new Firebase project and enable a common… more

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Documentation  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Education

    Kakakheil-One

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Remote Config  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Condition groups for Remote Config

    Here is the problem: we have a lot of versions of our app where some configs or their structure where changed in a backwards-incompatible way, so we need to roll them out using conditions by version: old config is placed under some "Legacy before v1.1.1" condition, and the new one becomes the default.
    As you can imagine, after a while we have a lot of these legacy conditions and scrolling through all of them becomes tedious. So creating one single "legacy" group to store them all would be very useful.

    I expect that all conditions placed in a group should be evaluated one-by-one in the order that they are specified in said group:
    - Condition A
    - Legacy/Condition B
    - Legacy/Condition C
    - Condition D
    etc...

    Also it would be useful to target config roll-outs by the whole group. For example, I could create one single config that all users that have been resolved to any condition under "Legacy" group will receive

    It would be nice if could also collapse such groups on each config to reduce visual clutter

    Thank you!

    Here is the problem: we have a lot of versions of our app where some configs or their structure where changed in a backwards-incompatible way, so we need to roll them out using conditions by version: old config is placed under some "Legacy before v1.1.1" condition, and the new one becomes the default.
    As you can imagine, after a while we have a lot of these legacy conditions and scrolling through all of them becomes tedious. So creating one single "legacy" group to store them all would be very useful.

    I expect that all conditions placed in a group should… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Remote Config  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. allow the bot to have global admin console privledges.

    The bot often has problems performing cli functions. Please allow it to autonomously approve api's, run commands, etc...just provide ui prompts for the user to decline the action if they feel the need.

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Gemini in Firebase  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Enhance Go Development Support for Integrated GUI Applications in Remote/Cloud IDEs

    Enhance Go Development Support for Integrated GUI Applications in Remote/Cloud IDEs

    To the Google Firebase/Cloud Platform Team,

    I am writing to provide critical feedback on the current Go development experience within cloud-based IDE environments (such as Cloud Workstations or Cloud Shell Editor) and to propose a significant feature enhancement that aligns with modern full-stack development trends.

    1. Summary of the Strategic Goal: Go for End-to-End Applications

    Our objective is to leverage the performance and cross-compilation capabilities of Go (Golang) for developing integrated, full-stack applications—specifically, those combining high-performance Go backends with modern Go-based Graphical User Interfaces (GUIs).

    The ability to rapidly prototype, debug, and run Go-based frontends (e.g., using toolkits like Fyne, Wails, or Gioui) within the same remote environment used for backend and cloud service development is an essential step toward achieving a truly unified, holistic cloud development workflow for the Go ecosystem.

    1. The Technical Limitation: The Headless Barrier

    While the remote IDE is robust for compiling and executing server-side Go services, it fundamentally fails when attempting to execute applications that require access to a display server.

    The Issue Encountered (Proof of Concept Failure):

    When attempting to run a simple application built with fyne.io/fyne/v2, the process fails at two stages:

    Build Stage Failure: Compilation initially fails due to the absence of crucial underlying system dependencies (e.g., OpenGL, X11 header files, and required C/C++ tooling) that Go GUI toolkits rely on for linking.

    Runtime Stage Failure (Root Cause): Even after manually installing the necessary dependency libraries (e.g., libgl1-mesa-dev, xorg-dev), the application executable cannot launch because the Cloud IDE container is a "headless" environment that lacks an active X Display Server or Wayland compositor. The application terminates with errors indicating it cannot open a display connection (e.g., $DISPLAY not set).

    This structural limitation restricts Go's utility on the platform exclusively to CLI and API-only development.

    1. Impact and Value Proposition

    This limitation creates a significant friction point for Go developers:

    Fragmented Workflow: Developers are forced to compile their backend remotely but must switch to a local machine to compile, run, and debug the corresponding GUI or desktop-style frontend. This breaks the promise of a seamless, cloud-native development experience.

    Restricted Market Adoption: It limits the platform's appeal for developers who choose Go specifically for its strong cross-platform GUI options (desktop, mobile, WebAssembly).

    Loss of Debugging Efficiency: The powerful remote debugging tools available in the IDE cannot be effectively utilized for the user-facing portion of a Go application.

    The Opportunity: By solving the display server problem, Google Cloud can position Go as a premier language for truly integrated full-stack development, appealing to users who value the concurrency and single-binary deployment advantages Go offers.

    1. Proposed Solution: Integrated Virtual Display Streaming (The Key Feature)

    The most robust solution involves integrating a mechanism to provision and stream a virtual graphical environment directly into the user's browser.

    Primary Feature Ask: Virtual Display and Streaming

    We request the implementation of a service that automatically handles the graphical runtime environment:

    Virtual Display Service: Automatically initialize and manage a virtual display server (such as Xvfb or a similar in-memory display buffer) within the development container.

    Dependency Pre-configuration: Ensure that all standard Go development environments (or a dedicated "Go GUI" template) are pre-installed with the required X11, OpenGL, and C/C++ development libraries necessary for major Go GUI toolkits to compile successfully.

    Low-Latency Streaming: Implement a low-latency, WebSockets-based streaming solution (e.g., leveraging VNC/noVNC principles) that captures the output of the virtual display and renders it in a dedicated browser tab or pane within the Cloud IDE, allowing for full mouse and keyboard interaction.

    Execution Flow: A developer should be able to simply execute a Go GUI application (e.g., go run main.go), and the IDE automatically starts the necessary forwarding/streaming process, showing the interactive application window.

    Minimum Requirement: Clear Guidance and Pre-configuration

    At a minimum, if real-time streaming is not immediately feasible, we request:

    Pre-configured Base Images: Offer official container images that include the necessary system dependencies (libgl1-mesa-dev, xorg-dev, etc.) to guarantee that Go GUI applications can at least successfully compile and be packaged/built for local deployment, eliminating the "missing dependency" build errors.

    Clear Documentation: Provide prominent documentation explicitly detailing the headless limitation and directing users toward the supported cross-compilation workflow for Go GUI applications.

    By integrating the Virtual Display Streaming capability, you will transform the developer experience for a growing segment of the Go community and significantly expand the scope of application development supported by the Firebase and Google Cloud platforms.

    Thank you for your review and consideration of this strategic enhancement.

    Enhance Go Development Support for Integrated GUI Applications in Remote/Cloud IDEs

    To the Google Firebase/Cloud Platform Team,

    I am writing to provide critical feedback on the current Go development experience within cloud-based IDE environments (such as Cloud Workstations or Cloud Shell Editor) and to propose a significant feature enhancement that aligns with modern full-stack development trends.

    1. Summary of the Strategic Goal: Go for End-to-End Applications

    Our objective is to leverage the performance and cross-compilation capabilities of Go (Golang) for developing integrated, full-stack applications—specifically, those combining high-performance Go backends with modern Go-based Graphical User Interfaces (GUIs).

    The ability to rapidly prototype,… more

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firebase Studio  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Subject: UI-Based Context Management to Prevent Token Limit Errors - Suggestion for App Prototyper Enhancement

    Subject: UI-Based Context Management to Prevent Token Limit Errors - Suggestion for App Prototyper Enhancement

    I am writing to you as a community of active App Prototyper users who greatly appreciate its capabilities. Recently, I've encountered a challenge that we believe will become increasingly common for users: the "input token count exceeds" error ([GoogleGenerativeAI Error]: ... The input token count (...) exceeds the maximum number of tokens allowed (...)). This issue arises from the accumulation of conversation history within the capra-context-state.json file.

    A community member (as discussed in this forum post: https://community.firebasestudio.dev/t/temporary-workaround-for-error-due-to-exceeding-input-token-count-unofficial/12457) conducted a detailed investigation and proposed a manual workaround involving direct editing of the capra-context-state.json file to reduce the conversation history sent as context to the Gemini model. While effective, this manual solution carries risks and requires a level of technical expertise that may not be accessible to all users.

    The Identified Problem:

    After analysis, based on the current functionality and the content of capra-context-state.json (an example of its structure is provided below), confirms that the complete history of interactions, particularly within agentHistories["app-prototyping-agent: edit-app-agent"], is re-sent with each new prompt. With continued use, this history grows, inevitably leading to the model's token limit being exceeded.

    Example of the relevant capra-context-state.json structure (simplified):
    ```json
    {
    // ... other sections like currentProposalObject ...
    "agentHistories": {
    "app-prototyping-agent: edit-app-agent": [
    {
    "role": "user",
    "content": [{"text": "User message 1..."}]
    },
    {
    "role": "model",
    "content": [{"text": "Model response 1..."}]
    },
    {
    "role": "user",
    "content": [{"text": "User message 2 (reporting error)..."}]
    },
    {
    "role": "model",
    "content": [{"text": "Model response 2 (suggesting fix)..."}]
    }
    // ... more interactions ...
    ]
    },
    "currentState": "edit-app"
    }

    The Proposal: UI-Integrated Context Management

    To make context history management safer, more intuitive, and accessible to all users, we propose implementing features directly within the App Prototyper interface. I believe this would significantly enhance the user experience and the long-term usability of the tool.

    Suggest including buttons that could appear next to each message or interaction block (user prompt + model response) in the chat window, possibly on hover to keep the interface clean:

    'Delete' (or 'Remove from Context') Button:

    Functionality: Would allow the user to select a specific message or an interaction pair (user prompt + model response) and remove it from the corresponding array in agentHistories within capra-context-state.json.

    Impact: Directly reduces the token count.

    Considerations:

    A confirmation dialog would be essential.

    Ideally, the removal would also be reflected in capra-thread.json (history view), or at least the message would be visually marked as "not included in context."

    Removing a pair (user/model) seems to be the most natural approach, as observed by the community.

    'Edit' Button:

    Functionality: Would allow the user to modify the text of a previous user message within the context. This would be useful for shortening long prompts or correcting information without removing the entire interaction.

    Impact: Allows for finer control over token content.

    'Refresh Context' (or similar) Button:

    Functionality: After performing deletions or edits, this button would ensure that the App Prototyper uses the updated capra-context-state.json for the next submitted prompt, avoiding the behavior of the "Retry" button which, as understood, uses the pre-modification context. It could also clear the new prompt input field.

    Benefits of Implementation:

    Accessibility: Empowers all users, regardless of technical expertise, to manage context and avoid token errors.

    Safety: Reduces the risk of JSON file corruption from manual editing.

    Improved User Experience (UX): Offers an integrated and seamless solution to a recurring problem.

    Maintained Productivity: Allows users to continue using the Prototyper for longer periods without interruption.

    Next Steps and Collaboration:

    I understand that the project is open source. As users with technical capabilities, I am willing to explore the possibility of contributing to the implementation of these features if it aligns with the team's interests. I already have a good understanding of the data structures involved and a VM with code access for prototyping.

    I would appreciate hearing your thoughts on this proposal and whether there are any internal plans or considerations regarding this issue. I am available to discuss this further, provide more details about the analysis, or collaborate in a way that is most productive.

    Thank you for your time and for the excellent tool that the App Prototyper is.

    Sincerely,

    Subject: UI-Based Context Management to Prevent Token Limit Errors - Suggestion for App Prototyper Enhancement

    I am writing to you as a community of active App Prototyper users who greatly appreciate its capabilities. Recently, I've encountered a challenge that we believe will become increasingly common for users: the "input token count exceeds" error ([GoogleGenerativeAI Error]: ... The input token count (...) exceeds the maximum number of tokens allowed (...)). This issue arises from the accumulation of conversation history within the capra-context-state.json file.

    A community member (as discussed in this forum post: https://community.firebasestudio.dev/t/temporary-workaround-for-error-due-to-exceeding-input-token-count-unofficial/12457) conducted a detailed investigation and proposed a… more

    6 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Clear parts of context

    If I rollback a change to the project, but the previous change is still in context then future changes are poisoned. I need a way to clear part of the context. Or even just resetting the context would help.

    5 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Firebase Studio  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating