Full Refresh option in Force Sync

Users currently struggle and have to perform multiple steps when indexing a new schema in the vectorDB. Current Steps - Update the metadata schema Change the mode the full refresh deploy the flow Schedule Runs Data indexed Proposed Steps - Option in Jobs > Force Sync > Full Refresh Automatically updates flows, Deploys it, Trigger a Job Return back the flow to Incremental

Aman Sharma 6 months ago

12

💡 Feature Requests

Support for Local Development

An open-source SDK to address developer adoption barriers and vendor lock-in concerns that are currently limiting growth. Problem Developers resist Lamatic's no-code/low-code platform due to limited library support, lack of local development capabilities, missing CLI tools, and weak version control integration Enterprise and startup customers worry about vendor lock-in and business continuity if Lamatic changes pricing or discontinues service Competitors offering open-source alternatives have an advantage Proposed Solution Build a standalone, open-source SDK enabling developers to: Develop AI agents/systems locally in their preferred IDE Test and debug offline without cloud dependency Use Git for version control across all project components Create custom integrations and capabilities Deploy anywhere (on-premise, private/public cloud, or Lamatic-managed) Compile flows into executable code via CI/CD pipelines Core Architecture YAML-based configuration system with: Pre-built node libraries for AI components Containerized runtime (Pod + Core) executing configurations Compiler for optimizing YAML into executable workers Local web editor accessible via localhost CLI for all development operations Multiple invocation methods (API, webhooks, widgets)

Aman Sharma About 1 month ago

💡 Feature Requests

Integration to ZeroEntropy

Integrate with ZeroEntropy API for Vectorization, Ingestion and Query

Ghita About 1 year ago

Engineering

🔌 Integration

Dispay Test Run Stats in Debugger

Problem: Developers must manually compute speed and token metrics from logs. Use case: Quickly benchmark and optimize workflows against performance targets. Functionality: Real-time display of execution time, token usage, accuracy indicators, TTFT, throughput, and benchmark comparisons within the debugger.

Aman Sharma 4 months ago

1

💡 Feature Requests

Spaces for static file uploads and usage

Ability to upload files and use them in flows (to, among other things, eliminate the need to find a place to host files either for testing or production purposes). For example, PDF upload for training or CSV for instructions.

Aman Sharma 9 months ago

1

Engineering

💡 Feature Requests

Enhance Flow Comparison

Multi-tab Support and Flow Comparison Enable right-click to open flows in new tabs for easy comparison Support multiple tabs within the main window (similar to how Linear handles native apps) Display full flow names - currently get cut off/truncated in the UI, making it difficult to distinguish between flows Allow side-by-side visual comparison of different flow versions Consider implementing an Electron wrapper for native app experience with better tab support Cross-Environment Flow Navigation Ability to change environments within a single flow view - users want to see what the same flow looks like in staging while viewing production Maintain flow state when switching environments instead of returning to flow home screen Use flow slug associations to link flows across environments (dev/staging/production) Reduce manual effort required to promote workflows from dev → staging → production

Aman Sharma 8 days ago

💡 Feature Requests

Support For dynamic File References in Flow Config

The nodes are embedded inline with formatting artifacts (hello\\nhello), apparent test content, and no versioning metadata. Editing it requires understanding the entire config file, and changes produce noisy diffs that obscure actual prompt improvements. Before: prompts: - id: 187c2f4b-c23d-4545-abef-73dc897d6b7b role: assistant content: >- hello hello Important:please provide the response in wrap text format... After: prompts: - id: rag_system_prompt_v1 role: assistant # Edit prompts in /prompts/rag_system.md — supports preview & versioning contentRef: ./prompts/rag_system.md version: "1.2.0" lastUpdated: "2025-01-15" Developer Impact: Prompts become first-class artifacts — reviewable in PRs, A/B testable, and editable without touching pipeline config.

Aman Sharma About 1 month ago

💡 Feature Requests

Break Node and End Node

Problem: No clear way to terminate workflows early or break out of loops based on conditions, forcing users to create workarounds with maximum iteration counts. Use Case: When API calls fail or specific conditions are met, users want to cleanly exit workflows or break out of polling loops without continuing unnecessary iterations. Proposed Solution: Implement dedicated break and end nodes that allow conditional workflow termination and loop breaking.

Aman Sharma 3 months ago

💡 Feature Requests

Automated Response Evaluation System (Graders)

Problem: Manual grading of responses does not scale and is inconsistent. Use case: Systematically assess response quality across large test suites. Functionality: Grader agents with configurable rubrics, batch “grade all” execution, and integration with logs for historical evaluation.

Aman Sharma 4 months ago

💡 Feature Requests

First-Party Chat History Management

Problem: Developers must manually manage JSON and memory fields across nodes, with inconsistent support. Use case: Simplify building and testing conversational flows with a toggle-based experience. Functionality: Checkbox-style chat history enablement, consistent memory field support on all nodes, and automatic user-based history storage and retrieval.

Aman Sharma 4 months ago

💡 Feature Requests

Billing: implement a Billing Manager permissions option

Customer reports: “Only the person that opens the account right now can enter billing information. Even if you’re an admin, you cannot enter billing information for what I’ve seen. Is there a way to solve this in a future product feature?” While best practice is to restrict the ability to edit billing info in a multi-user SaaS product, the ability to assign this role is desireable and will support the use case where a user signs up with a free account, but needs someone else to input billing info to upgrade. Will also support the ability for users to transition off the team and to have multiple billing managers for backup.

cwhiteman 7 months ago

5

👏🏻 Feedback

Connect with External Vector DB

Support Vector DB Weaviate PG_Vector PineCone Additional MongoDB ChromaDB Qdrant

Aman Sharma About 1 year ago

🔌 Integration

Add support for S3 action Nodes

Currently we only support S3 as a trigger. Add support to use it as a action node as well.

Aman Sharma 3 days ago

🔌 Integration

Introduce Operator Mode

Global variables panel separate from flow editor for non-developer operators Locked flow state where operators can edit variables without accessing full flow editor Highlight node associations when editing variables to show which nodes they belong to Overview/home tab combining reports and high-level flow statistics Unlock button system for accessing advanced editing features

Aman Sharma 8 days ago

UI/UX

💡 Feature Requests

Show Logs even if the request gets disconnected or Failed.

Using Lamatic is impossible to debug a situation that you can't see. If you run it through the editor and it works and use the API, it doesn't work, you have absolutely no way of knowing other than looking at all third-party tools that you have, like LLMs and different platforms for their own logs. I don't find that very helpful and it was very frustrating, hence all my messages and no responses from anyone for support.

Mark Ridgeon 28 days ago

🐛 Report Bug

Vector Search as Tool

Support Inbuilt vector search of vectorDB as tool call for AI Node

Aman Sharma 4 months ago

💡 Feature Requests

A/B Testing Analytics and Reporting in Logs

Problem: A/B experiments lack clear labeling and result visualization. Use case: Make data-driven decisions about prompts, flows, and model choices. Functionality: Experiment labels on runs, statistical analysis with confidence intervals, dashboards for variant comparison, and filtering/grouping by experiment tags.

Aman Sharma 4 months ago

💡 Feature Requests

Persistent Test Run History and Analytics

Problem: Debug runs are not persisted, hindering regression and performance tracking. Use case: Enable long-term testing workflows with historical comparisons. Functionality: Store all runs with timestamps and versions, searchable and filterable history, and side-by-side comparison of different runs and versions.

Aman Sharma 4 months ago

💡 Feature Requests

11Labs

Problem: Basic TTS/STT is insufficient for production-quality voice applications. Use case: Deliver high-quality, natural-sounding voice interactions for customer-facing apps. Functionality: A dedicated 11Labs node with full API coverage, streaming voice generation, configurable voices, and secure credential management.

Aman Sharma 4 months ago

🔌 Integration

Integrated Voice Processing Capabilities

Problem: No native voice model support, requiring external services for voice features. Use case: Build voice companions, real-time call analysis, and other voice-first applications. Functionality: Dedicated STT and TTS nodes with model selection, streaming audio support, real-time transcription/synthesis, and voice-based triggers and responses.

Aman Sharma 4 months ago

💡 Feature Requests