Changelog

Have something to say?

Tell us how we could make the product more useful to you.

Please add markdown rendering in chat

Please add markdown rendering. It displays as asterisks [e.g. asterisks (**) around ‘hello’ instead of displaying hello / hello in bold or italics]. Same with bullets. Dashes show as dashes instead of rendering as bullets. The AI often provides full markdown responses, but the chat can’t render them. MAJOR shortcoming, and super-basic. Please add it.

P. M. 9 days ago

💡 Feature Request

App-Initiated Learning Loop

This is a process that the app runs periodically to help analyze its own performance, identify patterns, and surface areas for improvement in the base prompt and training materials, to make the app more self-learning. It would work in four key steps: Define the trigger, have the LLM analyze gaps in responses to user queries, have the LLM identify areas for improvement, and then revise the base prompt and training materials. I’ve set this up with my app directly (and to only run when I’m the logged-in user), but what would be most useful would be if my app could directly access its own analytics, so I don’t have to download and upload these manually.

Russ Gaskin 3 months ago

💡 Feature Request

Fix link format on shared chats

Two issues here: When we share a chat from our Calstudio app, the link to the app at the bottom of the shared chat uses the app’s AI Name instead of its Display Name. In our case, it should be “Shared by Collaboration Advisor” instead of “Shared by CollaborationAdvisor”. The hyperlink on that text goes to for our app is https://advisor.wearecocreative.com/advisor.wearecocreative.com. That link works for some reason (maybe any value would work after the domain), so I’m just flagging this in case it’s an issue for others, especially those without custom domains.

Russ Gaskin 3 months ago

🐛 Bugs

Additional Styling Options

More control over styling look and feel! Incorporating an AI product into your website needs to have consistent branding options to feel part of you offering and not obviously another platform that feels like more of a bolt-on. Please consider giving more styling options for backgrounds, fonts, button styling and also consider providing some additional fun defaults like gradient, brutalist, moden themes. I would use Relume’s outstaning style generator as an excellent reference point: https://www.relume.io/style-guide

Christopher McCorry 4 months ago

💡 Feature Request

Support direct WhatsApp integration (without Twilio)

I’ve previously discussed this privately, but now at least one competitor already supports it (see this doc), so perhaps is it time? Their version: Chooses the phone number on their own (although they promise to support custom numbers in the future), so basically the app owner just enables a “WhatApp integration” checkbox and that’s all! Requires an extra request for each message (similar to what CalStudio already does with images, etc.) Solves WhatsApp File/Image Sharing Integration (they state “If your agent can do it inside your app, it can do it in WhatsApp too”) Doesn’t reveal if and how they support a login system (which in CalStudio is required in order to solve Allow to monetize WhatsApp/Email/SMS Integration) The competitor’s announcement:

lwc 5 months ago

3

💡 Feature Request

Allow to monetize WhatsApp/Email/SMS Integration

Basically everything that isn’t Web can’t be monetized which is unfortunate that some people might prefer those methods (especially WhatsApp) much better. For Email it should be relatively easy since you already have the users’ email addresses. Sure, it can forged but you can check if at least one of SPF/DKIM/DMARC passed. As for WhatsApp and SMS, you can ask users to fill in their phone number and then you should be all set.

lwc 6 months ago

💡 Feature Request

Persistent Single Chat Session per User

Users often want to interact with the app in a continuous, ongoing way—like talking to the same assistant over time. Having multiple or fragmented sessions disrupts this expectation. The inability to maintain one consistent thread of conversation makes it harder to ask follow-up questions or build on past interactions. For a better experience, users should feel like they’re always returning to the same conversation, with history and context intact, rather than starting fresh every time.

Aditya Karki 6 months ago

💡 Feature Request

Support multiple file uploads in chatbot

Currently, our chat bot built using calstudio.com only allows for single file uploads: if a user uploads a new file, it replaces the previous one. We need a feature that enables users to upload multiple files successively, so that all uploaded files remain visible and accessible. Example use-case: User uploads ‘file1.pdf’, then uploads ‘file2.docx’ — both files should be visible in the chat, not just the last one.

Aditya Karki 6 months ago

💡 Feature Request

Request to Grant "Credit" Access to Other Admins in Project

We would like to request that the "Grant Credit" feature be made accessible to other admin-level users within our project. Currently, only the primary admin has this access, but for operational flexibility and smoother workflow, it’s important that designated team admins can also allocate credits to users as needed. Please enable this permission for all admin roles or provide a way to assign this specific capability.

Amit Sethi 7 months ago

💡 Feature Request