# 2026.18 Infrastructure Changes

## Changes on Application environment

| **Change** | **Environment Variable Name** | **Application Default Value (if env variable unset)** | **Example** | **Required** | **Applications** | **Short Description** |
|------------|-------------------------------|-----------------------------------------------------|-------------|--------------|-------------------|-----------------------|
| Added      | `EXCLUSIVE_FILE_ACCESS_FOLDER_LABEL` | `[Restricted]`                                     | `[Restricted]` | false        | `backend-service-ingestion` | Sets the placeholder folder name shown when a user has access to a file, but not to the folder that contains it. When it is set to `''` this behavior is disabled |
| Added      | `FEATURE_FLAG_ENABLE_FOLDER_PATH_RESOLUTION_FOR_EXCLUSIVE_FILE_ACCESS` | `false`                                           | `false`     | false        | `backend-service-ingesiton` | When enabled, the system can include folders that the user does not directly have folder access to, but that contain files they are allowed to access. Those restricted folder names are shown using `EXCLUSIVE_FILE_ACCESS_FOLDER_LABEL`, defaulting to `[Restricted]`. |
| Added      | `FEATURE_FLAG_ENABLE_SELECTED_UPLOADED_FILES_UN_18215` | `false`                                           | `true`      | false        | `web-app-chat` | When enabled, the chat's Select Files panel gains an Uploaded files tab which lists files uploaded in the current chat. Users can select or deselect individual files (or all at once) to control which uploaded files are included as context for their next message. Requires `FEATURE_FLAG_ENABLE_NEW_ANSWERS_UI_UN_14411`. |
| Added      | `FEATURE_FLAG_DEPLOYMENT_VERSION_CHECK` | `false`                                           | `true`      | no           | `web-app-chat`, `backend-service-configuration` | When enabled, will start the version pooling behaviour on chat to detect version changes and show the modal if there is a mismatch. |
| Added      | `FEATURE_FLAG_FILE_PREVIEW_UN_19395` | `false`                                           | `true`      | no           | `backend-service-configuration` | When enabled, user would be able to preview files in sidebar |
| Added      | `FEATURE_FLAG_SIDE_MENU_NAVIGATION` | `true`                                            | `true`      | no           | `backend-service-configuration` | When enabled, users interact and see new sidebar navigation |
| Added      | `FEATURE_FLAG_AGENTIC_TABLE_ENABLE_NEW_SHARING_UI_UN_16758` | `true`                                           | `true`      | no           | `web-app-chat` | Enables the [new sharing functionality](https://docs.unique.ai/users/spaces/agentic-table) for Agentic Table |
| Changed    | `INTERNAL_MODULES_CONFIG` — `RfpAgent.apiURL` entry | _(set per environment overlay)_                    | `http://assistants-agentic-table.python.svc.cluster.local/agentic_table` | yes          | `backend-service-chat` | Routes **RfpAgent** (Agentic Table) to the dedicated **assistants-agentic-table** service at `/agentic_table` instead of **assistants-core**`/core/rfp_agent`. Update each cluster overlay when deploying **assistants-agentic-table** with this release. |
| Added      | `FEATURE_FLAG_ENABLE_NEW_SPACE_ACCESS_MODAL_UN_17544` | `true`                                           | `true`      | no           | `web-app-admin` | Enables the new sharing modal UI in Space Management |
| Added      | `LITELLM_ENABLED` | `false`                                           | `true`      | no           | `backend-service-chat` | Set to true or company IDs to enable LiteLLM usage for all or select companies. |

## New service: assistants-agentic-table

With release `2026.18` there is a new service introduced named **assistants-agentic-table**. It’s a Python AI service (dedicated Helm chart / ArgoCD app) and must be deployed wherever the Agentic Table feature is enabled. The service will handle and process the Agentic Table requests - the functionality has been extracted from the `ai-service-assistants-core` service into its own service in order to better distribute the load.

In order to switch traffic from `ai-service-assistants-core` to `ai-service-assistants-agentic-table`, align **backend-service-chat**`INTERNAL_MODULES_CONFIG` environment variable so the `RfpAgent` targets this service eg. `{"name": "RfpAgent", "apiURL": "http://assistants-core.<namespace>.svc.cluster.local:8081/core/rfp_agent"}`.

## New version Modal

With this release, the Chat web app can optionally detect when users are still on an older build after you’ve deployed a newer one. When that option is turned on, people who keep a tab open across a rollout get a short message asking them to reload, so they don’t hit odd errors from mixing old UI with new server behavior.

That option is controlled on the Chat deployment by the environment variable `FEATURE_FLAG_DEPLOYMENT_VERSION_CHECK` (set it to `