Changelog

Have something to say?

Tell Chasm how they could make the product more useful to you.

Pinned

[Template] A brief title that clearly describe what the feature is about

Content: A detailed explanation on how you want the feature to work and what is the use case of the feature? If possible, include any image references, videos, screenshots, or sketches to help convey your ideas more effectively. Impact of Not Having This Feature: What are the consequences of not implementing this feature. Will it hinder your or other users' ability to use the product effectively? [Example] Title: Enable weave to be used as a plugin on social media manager tools Content: As a social media manager, I'm using Later to plan and manage the social media post. Currently, I'm using Later to pre-schedule the post and use some other content generator tools to generate the contents and have to manually upload the content to Later. I find that Weave is super helpful for content generation and wish that there could be a Weave plugin on Later to create seamless content management.

Shuwei Li Over 2 years ago

💡 Request a feature

Planned

Reorganizing AI Models in 'All' view

Description: Currently, the arrangement of AI models in the All models menu is scattered. Models from the same provider not grouped together. For example, Meta has models on the top on the list and also at the bottom of the list. This setup can lead to confusion and inefficiency when users are trying to locate specific models. Proposed Change: Reorganising the AI models by sequencing them according to their respective providers. This would entail placing all LLM models in a contiguous block. This will improve navigational efficiency and user experience by making it easier to find and compare models from the same provider.

Johnson Lai Over 1 year ago

💡 Request a feature

Suggest to add a loading state between the Run and Stop button

I'm testing long prompts around 3.2k tokens using GPT-4 and have wasted quite a few credits.Sometimes the Run button is not very responsive (especially when the prompt is saving or the token size is a bit large). There may be a half to one-second delay before it actually starts running. I accidentally double-click because I think I didn't press the Run button the first time. As a result, the second click actually hits the Stop button.There needs to be a longer delay when changing the Run button to the Stop button. Maybe add a loading state.

Engineers Over 1 year ago

💡 Request a feature

Completed

Qwen1.5

Name of AI model: Qwen1.5 Huggingface / API Documentation Links: https://huggingface.co/collections/Qwen/qwen15-65c0a2f577b1ecb76d786524 https://openrouter.ai/models?q=qwen https://www.reddit.com/r/LocalLLaMA/comments/19e9xfj/introducing_qwen/ Purpose of using this model: Good for Mandarin and Japanese language inferencing, apparently has beaten GPT4 turbo for understanding Mandarin. Could be useful for those foreign language LLM requirements as a viable alternative to GPT. Issues involving hyperalignment as it's trained by distilling GPT lol. Current use cases that is already using this model Coding (surprisingly), different chatbots for different languages etc etc. Multimodal it's possible to have other input/output forms like visual and audio too.

An Anonymous User Over 1 year ago

📩 Suggest a new model

Making Weave API OpenAI compatible

With weave api being open ai compatible, user can just change their API in just 2 lines, then we can onboard user that used OpenAI quickly. const openai = new OpenAI({ baseURL: "https://pms.chasm.net/api/prompts/execute/44", apiKey: OPENAI_API_KEY, });``` Also with this feature, we can integrate with Langchain easily as well, user can just change model through API Slack Discussion: https://chasm-talk.slack.com/archives/C05PHU191GX/p1715774841176749

Johnson Lai Over 1 year ago

💡 Request a feature

[feature] Conditional logic, if/else and for loops

https://chasm.featurebase.app/p/conditional-or-logic-block-to-enable-workflow-brances ^ in regards to this post above, we have revisited the need to have built in logic blocks for the workflow page. A proposed design is either having assembly style JUMP-IF/LAND logic, or a encompassing loop. Some samples on how they might look like. The If/Else can simply be a dual branch design, no need for a Case style switch design for now. A design decision we must make is deciding between using another prompt block with execution pathway selection, vs a simply boolean/operator mini-block. I'm leaning towards the former as it will be more flexible and in line with the LLM industry.

John Koh Almost 2 years ago

💡 Request a feature

Completed

Model Catalog

Before user selects a model to run their prompt, the model catalog can help the users by reading the description of the model to help them better understand of the available model shortlist the LLM models according to their use case and preference searching for the model for the ease of finding their preferred model This model catalog is also considered as part of the expansion plan where Weave will be the aggregator of dAi models

product@chasm.net Almost 2 years ago

💡 Request a feature

Add a blog section to the Weave Landing Page

Suggest to incorporate a blog section into the Weave Landing Page by utilizing a third-party tool to embed Medium articles into our own blog post section on the Weave website. Alternatively, we could consider developing our own blog section. The primary motivation behind this suggestion is to enhance Weave's SEO performance. Currently, when users search for articles on our Medium platform, it does not effectively drive traffic to our main website. For instance, a search for "Chain of Thoughts" yields results that prominently feature our competitor Vellum's website, effectively diverting user traffic to Vellum platform. By adding a blog section to the Weave Landing Page, we can improve our visibility in search results. Third party embedding tools: https://dropinblog.com/

Shuwei Li Almost 2 years ago

💡 Request a feature