Skip to content

ELITEA Release Notes

Introduction

Discover ELITEA — your all-in-one platform for working with Generative AI and managing data-driven projects. ELITEA goes far beyond a simple repository: it’s a flexible workspace where you can create, organize, and collaborate on prompts, datasources, agents, pipelines, and collections with ease. From building complex workflows to managing AI assistants or connecting external tools, ELITEA gives you everything you need to bring your ideas to life.

Information

Important

  • Availability: Version 1.7.0 is available in the Next environment only. Nexus will remain on its current version for now. The Next environment contains a full copy of your projects, agents, pipelines, toolkits, and chats migrated from Nexus, plus all 1.7.0 features and updates. Use this safe transition window to review changes, configure new Indexes, set up Credentials, and verify your workflows before Nexus is upgraded.
  • Prompts deprecated: The Prompts entity is deprecated. All existing prompts were converted to Agents. You can create Agents without attaching a Toolkit (a lightweight replacement for Prompts) and use variables with these agents.
  • Datasources deprecated: The Datasources entity is deprecated. Your existing datasources remain available in this release so you can re-index and reconfigure them using the new Index data tool available in most Toolkits (e.g., GitHub, Confluence, Bitbucket, ADO Repos, Jira, etc.), as even though they remain connected to agents, they cannot be used (as the datasets themselves are not migrated). Note: Creating new datasources or datasets is no longer supported.
  • Integrations replaced by Credentials: Integrations are deprecated and replaced by Credentials as a standalone entity. Existing Integrations are not auto-migrated; recreate them as Credentials manually. See: How to Use Credentials.
  • Toolkits separated: Toolkits are now a standalone entity under the Toolkits menu. Agents and Pipelines that previously had connected toolkits still keep those links; you can also reuse Toolkits across multiple entities. See: How to create a toolkit.
  • Temporary limitations (Next environment): Exporting agents/pipelines from Nexus and importing them into Next is not supported due to compatibility differences. Forking functionality may not work fully in Next. Both will be redesigned and enhanced in the upcoming release.
  • Shared LLM models (Next environment): The LLM models provided in Next are shared and intended for evaluation only and have daily limits. For any production workload, request your own EPAM AI DIAL keys and configure them in Settings → AI Configuration. For a quick walkthrough, see the: How to configure and use Epam AI Dial keys.

Reference

For a short walkthrough of working in the Next environment, see the Next - Quick Start Guide.

New Features

Chat Redesign and Enhancements

  • Complete redesign of the Chat menu for a more intuitive and modern experience
  • Quickly select frequently used entities (agents, pipelines) at the start of a conversation or during an active chat
  • Instantly search and select any entity (agents, pipelines) by typing # followed by the first letters of the entity name
  • Drag & drop support for moving conversations between the ungrouped list and folders, and vice versa
  • Automatic grouping and sorting of conversations into date-based groups (Today, Yesterday, This Week, Older)
  • Redesigned workflow for adding users to a conversation from the Participants sidebar
  • Redesigned Conversations sidebar for improved navigation
  • Redesigned Participants sidebar for better user management

Canvas: Agent and Pipeline Editing Support

  • Modify the selected agent or pipeline directly from a conversation via Canvas without leaving Chat.
  • Edit any selected version of an agent or pipeline.
  • From Canvas, add toolkits, agents, or pipelines to the selected agent/pipeline.

For usage details, see Canvas in Conversation.

Complete Redesign and Enhancement for Thinking Steps

  • Redesigned and enhanced Thinking Steps for agents, pipelines, and LLM model execution—both in Conversations and within Entities
  • More informative step-by-step details, including which tools and LLMs participated, with their input and output data, for improved troubleshooting and debugging
  • Thinking Steps are now preserved in Conversations for agents and pipelines, allowing later analysis and investigation
  • Added support to display the duration of each agent and pipeline execution, giving users deeper insight into performance

LiteLLM Proxy Support (Next environment)

ELITEA now supports using a LiteLLM-compatible proxy as the LLM endpoint in the Next environment.

  • Unified API across providers: route to models from multiple vendors via one proxy.
  • Fast access to additional and reasoning-capable models as your proxy exposes them.
  • Improved observability and cost tracking when enabled on your LiteLLM instance.
  • Works with streaming and function/tool calling workflows.

New Entity Type: Toolkits

Toolkits have been completely redesigned and are now a dedicated entity type in ELITEA, bringing major improvements to how you organize and reuse toolkits with Agents and Pipelines:

  • A new Toolkits menu lets you view and manage all your created toolkits in one place.
  • Creating a toolkit is now a streamlined process: simply choose the toolkit type, then configure it with an improved, user-friendly interface.
  • You can now reuse the same toolkit across multiple agents and pipelines, eliminating the need to configure the same integration or logic repeatedly. This leads to better organization, consistency, and efficiency in your projects.
  • When building or editing an agent or pipeline, you can either create a new toolkit (which will take you to the New Toolkit page) or select from your existing toolkit library.
  • Note: When you add other agents or pipelines as components within an agent or pipeline, they are now also tracked and managed as toolkits, providing unified visibility and control.

Agents Enhancements

  • Agent types have been deprecated.
  • Toolkits section enhancements for Agents/Pipelines:
  • +Toolkit button: Click to select from all available Toolkits or create a new toolkit.
  • +Agent button: Click to select from all available Agents to add as a “toolkit”.
  • +Pipeline button: Click to select from all available Pipelines to add as a “toolkit”. Note: you cannot add a Pipeline as a “toolkit” to an Agent if that pipeline contains interruptions or subgraphs.

Pipelines: New Router and State Modifier Nodes

Two powerful new nodes have been added to Pipelines, expanding your pipelines capabilities:

  • Router node: A simple, rule-based decision node. The Router node evaluates a condition using your current state or data, then selects one of several possible routes (branches) for the pipeline to follow. This enables dynamic, conditional logic within your automation flows.
  • State Modifier node: A utility node that updates, transforms, or cleans up parts of the workflow’s state. Think of it as a “state editor”—you can use it to modify one or multiple variables, generate new content using templates, or reset portions of the state as needed.

Postman Toolkit Integration

A new Postman toolkit is now available, enabling seamless integration between ELITEA and the Postman. With this toolkit, you can:

  • Automate API Testing: Run and manage your Postman collections directly from ELITEA agents and pipelines.
  • Retrieve and Update Collections: Access, duplicate, or update your Postman collections and requests as part of your automated workflows.
  • Leverage Postman Environments: Use environment variables and configurations to make your API tests more dynamic and flexible.

For setup and usage details, see the Postman Toolkit Guide.

Zephyr Squad Toolkit Integration

A new Zephyr Squad toolkit is now available, allowing you to connect ELITEA with Zephyr Squad for advanced test management. With this toolkit, you can:

  • Manage Test Cases: Create, update, and organize test cases within Zephyr Squad directly from ELITEA.
  • Automate Test Execution: Trigger and track test executions as part of your automated workflows.
  • Synchronize Results: Seamlessly sync test results and statuses between ELITEA and Zephyr Squad.

This integration helps unify your test management and automation processes, making it easier to maintain quality and traceability across your projects.

Changed Features

Credentials: Formerly Integrations

  • The feature previously known as "Integrations" has been renamed to Credentials and is now a dedicated entity in ELITEA.
  • Credentials allow you to configure authentication for different services at both the private (user) and project levels, supporting secure and flexible access management.
  • All functionality previously available under Integrations remains, but is now managed from the new Settings → Credentials page for easier access and organization.
  • Credentials can be reused in the toolkits, just as before.
  • Added support for new services, including ServiceNow, Postman, ADO Plans, ADO Repos, and Bitbucket, expanding the range of integrations you can securely manage.
  • This change improves clarity, centralizes credential management, and makes it easier to maintain secure connections to all your external tools.

Indexing Tools: Replacement for Datasets

ELITEA now provides six standardized indexing tools across supported toolkits, replacing legacy datasets:

  • Index Data: Create an index of data for search and retrieval.
  • Search Index: Perform search operations against indexed data.
  • Stepback Search Index: Advanced search with stepback context for improved relevance.
  • Stepback Summary Index: Stepback search with on-the-fly summary generation.
  • Remove Index: Remove an existing data index.
  • List Collections: Display available collections in the indexing system.

Currently supported toolkits include:

ADO Repos, ADO Wiki, ADO Plans, ADO Boards, Bitbucket, GitHub, GitLab, Confluence, Jira, SharePoint, Artifact, Figma, TestRail, Xray, Zephyr Enterprise, Zephyr Essential, Zephyr Scale.

Tip

You can also trigger indexing from an Agent or from Chat by selecting an Agent/Toolkit that has the Index Data tool, then instructing it to index the target (provide repo/site/project and scope). For an example, see Index GitHub data.

Coming soon: A dedicated menu to view created indexes across toolkits within a project, plus a per-toolkit tab showing useful index details.

Artifacts: Complete Redesign and Enhancements

  • The Artifacts menu has been completely redesigned for a more intuitive and efficient experience.
  • The Buckets table has been enhanced for better organization and usability.
  • New Preview File support allows you to view and review files and images directly within ELITEA, without needing to download them first.
  • A new Buckets sidebar provides quick navigation between different storage buckets.
  • You can now manually upload files from your PC directly into ELITEA.
  • Added the ability to select and download multiple files at once for greater convenience.

Settings: Complete Redesign and Enhancements

  • AI Configuration: The former Configuration tab is now the dedicated AI Configuration subsection under Settings. From here you can configure LLM models and Embedding models, manage AI services credentials (e.g., EPAM AI Dial), review available configuration details, and download an example configuration if you want to connect and use ELITEA LLM models via API.
  • Personal Access Tokens: Now a separate subsection under Settings for easier management. See Personal Tokens.
  • Secrets and Projects: Both subsections have been enhanced and improved for clarity and usability. See Secrets and Projects.

Fixed Issues

  • SQL Toolkit in Pipelines: Fixed an issue where the SQL toolkit could not be used in pipelines. Previously, when using tools like list_tables_and_columns or execute_sql in a pipeline, the answer would appear in the steps but no LLM response was provided. Now, the LLM response containing the answer is correctly returned.
  • Pressing Enter to Save a Secret Also Inserts a Newline in the Value: Fixed an issue where pressing the "Enter" key to save a secret would also insert a newline character into the value. Now, pressing Enter saves the secret without adding a newline.
  • Message Regenerate Function Fails After Agent or Pipeline Configuration Change: Fixed a bug where the message regenerate function would fail with a 400 bad request error after making changes to an agent or pipeline configuration. Now, regenerating a message works as expected and reflects the updated configuration.
  • Monitoring Export Fails When No Token Usage: Fixed an issue where exporting monitoring data would fail with a 400 error if there was no token usage for the selected project or timeframe. Now, an empty file is downloaded as expected.
  • Copy Secret Functionality Not Working on Safari Browser: Fixed an issue where the "Copy Secret" feature in the Secrets table did not work on Safari browsers due to Clipboard API limitations. Now, copying secrets works in following way, Show value of the secret then click the Copy to clipboard icon.
  • Existing GitHub Toolkits Not Functioning: After a recent update, existing GitHub toolkits may not function properly when editing or executing agents. Workaround: Delete the toolkit, add it again, configure it with the same settings, and save the agent.
  • General Usability Improvements: Various general fixes and enhancements have been implemented across the platform to improve overall usability, responsiveness, and user experience.

Known Issues

  • GIT Source Authentication: SSH authentication for GIT sources fails. Workaround: Use HTTPS with Username and Password.
  • Collections Import: After importing Collections, new collections are not being created under the Collections section.
  • Test Connection: The test connection functionality for the toolkit is currently experiencing issues and may not operate correctly. Confluence Dataset Label Filtering: When using multiple labels (two or more) as a filter while creating a dataset of Confluence type, an error occurs. The system raises an ApiValueError, indicating that the CQL (Confluence Query Language) is invalid or missing. Workaround: Use a single label as a filter to avoid this issue.