# Release notes

Freelucy versions are listed below in reverse chronological order. Each release builds on the previous — to use the newest features and stay supported on current ServiceNow releases, run version 3.1 or later.

***

## Version 3.1 — Improved

Minor release. Adds the capability to globally define tables that Freelucy filters out in the UI, rolls up essential library updates, and fixes outstanding bugs.

## Version 3.0.1 — Fixed

Bug fixes addressing loading issues on the ServiceNow Rome release.

## Version 3.0 — Major

Major interface overhaul. Introduces:

* The floating action bar.
* The redesigned side panel.
* Read-only mode for users with the Reader role.
* General improvements to relationship management and UI.

## Version 2.3

Adds relationship tooltips on hover and pre-commit removal of staged changes. Visual updates to popups and tooltip elements.

## Version 2.2

Adds the **Jump to** feature for switching the primary element from any connected element. Improvements to search.

## Version 2.1

UI color theme update, ACL adjustments, and bug fixes for browser-related issues.

## Version 2.0

Transition to the Freelucy brand and updates to the SweetAlert library.

## Version 1.1

Browser hierarchy view and multi-selection with drag-and-drop. Fixes for form and search-related issues.

## Version 1.0

Initial release with core relationship-editing functionality.

***

## What's next

* Review the [Roadmap](broken://pages/nWrXLJKkMqDlySZyHZWr) to plan upgrades.
* See [Update Freelucy](/freelucy/get-the-app/update.md) for how to move to a newer version.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ins-pi.com/freelucy/get-the-app/release-notes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.