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 APISlack Discussion: https://chasm-talk.slack.com/archives/C05PHU191GX/p1715774841176749
Johnson Lai 2 days ago
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 APISlack Discussion: https://chasm-talk.slack.com/archives/C05PHU191GX/p1715774841176749
Johnson Lai 2 days ago
Weave Product Feedback:
Feedback type:Β Feature Request / Bug Report / User Experience / Performance Description#1: Describe the Feature Request / Bug Report / User Experience / Performance you would like to suggest /see / improved.Duplicate the template above to list down as many instances of feedback as possible. Answer the following questions: On first impression, what would you rate Weave, on a scale of 1 to 10?On first impression, how easy is it to use Weave?You may use the following template to assist you:Β Feature Request:Describe the feature you would like to see?Why do you think this feature is important to Weave?User Experience:Describe your overall experience using the product.What do you like about the product?What improvements would you suggest?Performance:How does the product perform in terms of speed and responsiveness?Are there any specific areas where performance could be improved?
Shuwei Li 22 days ago
Weave Product Feedback:
Feedback type:Β Feature Request / Bug Report / User Experience / Performance Description#1: Describe the Feature Request / Bug Report / User Experience / Performance you would like to suggest /see / improved.Duplicate the template above to list down as many instances of feedback as possible. Answer the following questions: On first impression, what would you rate Weave, on a scale of 1 to 10?On first impression, how easy is it to use Weave?You may use the following template to assist you:Β Feature Request:Describe the feature you would like to see?Why do you think this feature is important to Weave?User Experience:Describe your overall experience using the product.What do you like about the product?What improvements would you suggest?Performance:How does the product perform in terms of speed and responsiveness?Are there any specific areas where performance could be improved?
Shuwei Li 22 days ago
[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 About 1 month ago
[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 About 1 month ago
PRD in Progress
Filter function for core modules
As a user, I want to be able to filter prompts / workflow by status As a uesr, I want to be able to filter datasets by file type
Mei Wei Lim 2 months ago
PRD in Progress
Filter function for core modules
As a user, I want to be able to filter prompts / workflow by status As a uesr, I want to be able to filter datasets by file type
Mei Wei Lim 2 months ago
PRD in Progress
Sorting function for core modules
As a user, I want to be able to sort my prompts, workflow, datasets by: name (alphabetical order or reverse)created date (earliest to latest, or reverse)updated date (latest to earliest, or reverse)
Mei Wei Lim 2 months ago
PRD in Progress
Sorting function for core modules
As a user, I want to be able to sort my prompts, workflow, datasets by: name (alphabetical order or reverse)created date (earliest to latest, or reverse)updated date (latest to earliest, or reverse)
Mei Wei Lim 2 months ago
PRD in Progress
Develop Weave's Platform Tokenizers
Different LLM has different set of tokenizers. To streamline the token calculation method on our platform, it's best to develop our own set of tokenisers. Reference: https://github.com/huggingface/tokenizers
Shuwei Li 2 months ago
PRD in Progress
Develop Weave's Platform Tokenizers
Different LLM has different set of tokenizers. To streamline the token calculation method on our platform, it's best to develop our own set of tokenisers. Reference: https://github.com/huggingface/tokenizers
Shuwei Li 2 months ago
Lock Node that Prevent Draggable
Because nodes position is one of the experience component, sometime user would mis click and nodes and it was drag elsewhere. it quite frustrated for user need to drag it back. especially when all the nodes as planned nicely for different region, therefore the lock feature would helpful for user have OCD
Patrick Lee 2 months ago
Lock Node that Prevent Draggable
Because nodes position is one of the experience component, sometime user would mis click and nodes and it was drag elsewhere. it quite frustrated for user need to drag it back. especially when all the nodes as planned nicely for different region, therefore the lock feature would helpful for user have OCD
Patrick Lee 2 months ago
Select Multiple Nodes
It would be better if we having a drag box that select multiple nodes and that allow user to group it and drag togetherbenchmark: Figma
Patrick Lee 2 months ago
Select Multiple Nodes
It would be better if we having a drag box that select multiple nodes and that allow user to group it and drag togetherbenchmark: Figma
Patrick Lee 2 months ago
PRD in Progress
Option for users to view core modules in grid or list view
By default, users can view the core modules in grid view. Users can have the option to toggle between grid view or list view. Core modules include: Prompt, Workflow and Datast
Mei Wei Lim 2 months ago
PRD in Progress
Option for users to view core modules in grid or list view
By default, users can view the core modules in grid view. Users can have the option to toggle between grid view or list view. Core modules include: Prompt, Workflow and Datast
Mei Wei Lim 2 months ago
Dev In Progress
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 modelshortlist the LLM models according to their use case and preferencesearching for the model for the ease of finding their preferred modelThis model catalog is also considered as part of the expansion plan where Weave will be the aggregator of dAi models
product@chasm.net 2 months ago
Dev In Progress
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 modelshortlist the LLM models according to their use case and preferencesearching for the model for the ease of finding their preferred modelThis model catalog is also considered as part of the expansion plan where Weave will be the aggregator of dAi models
product@chasm.net 2 months ago
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 3 months ago
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 3 months ago
Multiple credit purchase per transcation/payment
Allow user to purchase credit package n times per payment or transaction For example getting $120 worth of credits by purchasing the $30 package in 4x quantity.
Yongsheng Lui 3 months ago
Multiple credit purchase per transcation/payment
Allow user to purchase credit package n times per payment or transaction For example getting $120 worth of credits by purchasing the $30 package in 4x quantity.
Yongsheng Lui 3 months ago
Domain name & IP whitelist
Need this whitelist feature for each endpoint due to security concerns. Suggest to have a global settings that apply to all endpoint but at the same time also allow override for each individual prompt/workflow
Yongsheng Lui 3 months ago
Domain name & IP whitelist
Need this whitelist feature for each endpoint due to security concerns. Suggest to have a global settings that apply to all endpoint but at the same time also allow override for each individual prompt/workflow
Yongsheng Lui 3 months ago
Confusing workflow node connection logic
Having hard time to understand how to properly achieve this using Weave.Suggest to make some changes to the connecting node
Yongsheng Lui 3 months ago
Confusing workflow node connection logic
Having hard time to understand how to properly achieve this using Weave.Suggest to make some changes to the connecting node
Yongsheng Lui 3 months ago