Planned
Model Preference & Fallback
A dedicated UI to choose model preferences on project level. There will be different categories of models ( Tabs ) for Text | Embedding| Chat | Image | Audio | Transcript For Each category customer can create 5 Settings and reorder them. In each settings can choose 4 tabs ( Basic | Fallback | Best | A/B Test ) When using model selection in a workflow node, choose a preferred setting options which will populate the UI with credentials and model selection. ( By Default the first preference will be chosen or create a new preferences
Aman Sharma 10 months ago
💡 Feature Requests
Planned
Model Preference & Fallback
A dedicated UI to choose model preferences on project level. There will be different categories of models ( Tabs ) for Text | Embedding| Chat | Image | Audio | Transcript For Each category customer can create 5 Settings and reorder them. In each settings can choose 4 tabs ( Basic | Fallback | Best | A/B Test ) When using model selection in a workflow node, choose a preferred setting options which will populate the UI with credentials and model selection. ( By Default the first preference will be chosen or create a new preferences
Aman Sharma 10 months ago
💡 Feature Requests
Planned
Test Case Expected Results
When creating Test Cases, capture expected results (in addition to capturing the name and test conditions as Lamatic does currently). Consider also, Using code checks and AI to find deviation and grade result quality. Use this quality score as an input for deciding whether to deploy an update. Assist in recommending the best option when A|B testing prompts, agents, workflows, models and other settings such as temperature. Using these results to create benchmarks. Measuring and alerting about “model drift” over time. Integrating “human-in-the-loop” strategies to expand Test Cases and quality checking. Added Later (based on feedback from another user): Make it easier to see the history of Test Case executions (without leaving Experiments). Marc Greenberg didn’t realize he could find the results in Logs, but also didn’t like having to dig through logs to find the execution details for a given test.
cwhiteman 11 months ago
💡 Feature Requests
Planned
Test Case Expected Results
When creating Test Cases, capture expected results (in addition to capturing the name and test conditions as Lamatic does currently). Consider also, Using code checks and AI to find deviation and grade result quality. Use this quality score as an input for deciding whether to deploy an update. Assist in recommending the best option when A|B testing prompts, agents, workflows, models and other settings such as temperature. Using these results to create benchmarks. Measuring and alerting about “model drift” over time. Integrating “human-in-the-loop” strategies to expand Test Cases and quality checking. Added Later (based on feedback from another user): Make it easier to see the history of Test Case executions (without leaving Experiments). Marc Greenberg didn’t realize he could find the results in Logs, but also didn’t like having to dig through logs to find the execution details for a given test.
cwhiteman 11 months ago
💡 Feature Requests
Group Results Feature for Search
Add additional option to group results with a particular key to a UI similar to below
Aman Sharma About 1 month ago
👏🏻 Feedback
Group Results Feature for Search
Add additional option to group results with a particular key to a UI similar to below
Aman Sharma About 1 month ago
👏🏻 Feedback
Planned
Add tries for nodes executions
Add a global level property that sets how many times a given node can retry. Use a default value set on project setting level then it could be over-ridden for every node seperately.
aruna 10 months ago
High Priority
💡 Feature Requests
Planned
Add tries for nodes executions
Add a global level property that sets how many times a given node can retry. Use a default value set on project setting level then it could be over-ridden for every node seperately.
aruna 10 months ago
High Priority
💡 Feature Requests
Support Subflows / Stages within a flow
Customer want to build multiple agentic flows with different payload and stages within the same flow There are various options we can provide this - Suspend - Resume logic Dedicated Followup Node which sends back the response and takes the input then resumes the flow where it left
Aman Sharma About 1 month ago
💡 Feature Requests
Support Subflows / Stages within a flow
Customer want to build multiple agentic flows with different payload and stages within the same flow There are various options we can provide this - Suspend - Resume logic Dedicated Followup Node which sends back the response and takes the input then resumes the flow where it left
Aman Sharma About 1 month ago
💡 Feature Requests
Add Evals Functionality
Types of Evals - On Test Debug On Deployments Compare On Set of Logs Realtime Sampling Options Build Inhouse with AI Integrations Connect with Langfuse and do it cross directional
Aman Sharma About 1 month ago
💡 Feature Requests
Add Evals Functionality
Types of Evals - On Test Debug On Deployments Compare On Set of Logs Realtime Sampling Options Build Inhouse with AI Integrations Connect with Langfuse and do it cross directional
Aman Sharma About 1 month ago
💡 Feature Requests
Version Control Capability
Add functionality to version control within an environment - Projects Flows Prompts Version control should be visible via - logs API requests Reports
Aman Sharma About 1 month ago
👏🏻 Feedback
Version Control Capability
Add functionality to version control within an environment - Projects Flows Prompts Version control should be visible via - logs API requests Reports
Aman Sharma About 1 month ago
👏🏻 Feedback
Add MCP Support
Support for MCP Integration similar to Zapier. Find details here - https://www.perplexity.ai/search/how-can-lamatic-ai-build-mcp-i-9.Gp.fxuQ_WWHzBBqlqFUA
Aman Sharma 3 months ago
High Priority
💡 Feature Requests
Add MCP Support
Support for MCP Integration similar to Zapier. Find details here - https://www.perplexity.ai/search/how-can-lamatic-ai-build-mcp-i-9.Gp.fxuQ_WWHzBBqlqFUA
Aman Sharma 3 months ago
High Priority
💡 Feature Requests
Ability to export the code and deploy on other platform ( BYOC )
Support for code export like other platform like webflow
Aman Sharma 3 months ago
💡 Feature Requests
Ability to export the code and deploy on other platform ( BYOC )
Support for code export like other platform like webflow
Aman Sharma 3 months ago
💡 Feature Requests
Markdown Support in Prompt Editor
Add Markdown support to the Prompt Editor. It would make it much easier to write and share detailed, well-formatted prompts. Example
Vrijraj Singh 9 days ago
👏🏻 Feedback
Markdown Support in Prompt Editor
Add Markdown support to the Prompt Editor. It would make it much easier to write and share detailed, well-formatted prompts. Example
Vrijraj Singh 9 days ago
👏🏻 Feedback
Add Type-ahead to the API response section
In Lamatic, the GraphQL API trigger node response section does not support type-ahead (though other sections within Lamatic do). Pat@fama.io was confused by this and concluded that you don’t select variables in that window (which isn’t true). He suggested mirroring the same type-ahead functionality found elsewhere in the GraphQL API trigger node response section (which allows you to select variables by typing).
cwhiteman 10 days ago
Low Priority
👏🏻 Feedback
Add Type-ahead to the API response section
In Lamatic, the GraphQL API trigger node response section does not support type-ahead (though other sections within Lamatic do). Pat@fama.io was confused by this and concluded that you don’t select variables in that window (which isn’t true). He suggested mirroring the same type-ahead functionality found elsewhere in the GraphQL API trigger node response section (which allows you to select variables by typing).
cwhiteman 10 days ago
Low Priority
👏🏻 Feedback