> ## Documentation Index
> Fetch the complete documentation index at: https://docs.revoengine.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 1.5.9 — Portable component revisions, clearer AI usage and unified data workflows

> 23 September 2026

RevoEngine 1.5.9 makes Component revisions portable between instances, brings Databases and Database Views into one read and export workflow, and expands the information available to builders and administrators. Assistant model choices, dashboard widgets and operational views have also been updated. This release includes the fixes completed after the 1.5.8 source release.

## Highlights

* Pin Endpoints, Job Templates and Agent Plugin tools to a Component content digest that identifies the same revision across instances, even when local version numbers differ.
* Read and join Databases, live Views and Materialized Views through the same low-code methods, and export any of them through one workflow.
* Choose GPT-6 Sol or Luna for new Assistant and Agent work, with Fast Mode available on both; existing active GPT-5.6 choices migrate to their supported equivalents.
* Compare Assistant usage with the preceding period and inspect activity for tools, skills and plugins in the administrator Usage view.
* Add and arrange richer dashboard widgets, including operational performance and AI usage views, from the widget palette.
* Find Component source and historical revisions with smaller, targeted reads while keeping multi-element edits and approvals governed.

## In detail

<AccordionGroup>
  <Accordion title="Pin the same Component revision across environments" defaultOpen={true}>
    Components and their elements now carry content digests based on the executable revision. An Endpoint, Job Template or Agent Plugin tool can retain an exact revision by digest when it moves between instances whose local version counters differ. New bindings continue to follow the latest revision when no digest is selected. The builder can inspect revision history, search matching digests and select a verified revision before saving a binding.

    Element metadata is editable in the Component authoring flows, while reserved revision data stays managed by RevoEngine. Existing revisions and bindings are migrated to the new representation. Review a pinned integration after migration if its historical source differs between environments; a matching local number alone is no longer proof of matching content.
  </Accordion>

  <Accordion title="Use one readable relation workflow">
    The standard database read methods now accept Databases, live Views and Materialized Views as root relations or structured joins. Access checks apply to each relation, and an ambiguous logical name fails closed. New and renamed relations cannot take a name already used by another relation type. The same `api.exportDatabase()` workflow exports all three types, including joined results.

    ```js theme={null}
    const page = await api.getDatabaseData('recent_orders_view', { fields: ['orderId'], take: 25 });
    return page.data;
    ```

    ```js theme={null}
    const total = await api.countDatabase('orders');
    return total;
    ```

    ```js theme={null}
    const exportResult = await api.exportDatabase('recent_orders_view', { format: 'csv', fileName: 'recent-orders.csv' });
    return exportResult.storageEntryId;
    ```

    For new low-code code, use `api.getDatabaseData()`, `api.getDatabaseDataRow()`, `api.countDatabase()` and `api.walkDatabaseData()` for readable relations. The former View-only read helper remains as a deprecated compatibility alias. `api.exportDatabaseView()` and the separate REST View export operations have been removed; callers should use the unified Database export operation.
  </Accordion>

  <Accordion title="Make Assistant usage and activity easier to inspect">
    The administrator Usage view now shows a comparison with the previous period of the same duration and separates current, review and historical model usage. Tool, skill and plugin activity is loaded when its tab is opened. Plugin activity keeps a useful name and icon even after a plugin is permanently removed, while hidden system activity remains outside the user-facing conversation.

    New and resumed Assistant or Agent work selects GPT-6 Sol or Luna under the current configuration. Existing GPT-5.6 Sol choices map to GPT-6 Sol; Terra and Luna choices map to GPT-6 Luna. Historical messages and usage records retain the model that actually produced them.
  </Accordion>

  <Accordion title="Build dashboards and investigate with focused evidence">
    The dashboard widget palette supports adding a widget at a selected position and moving surrounding widgets into a valid layout before saving. New dashboard views bring Agent, AI usage, Database audit, Job performance and Endpoint performance information into the same workspace. The existing dashboard permission and save flow still controls persistence.

    Component discovery now returns a compact revision and element map before source is requested. Builders and the Assistant can read selected current or historical elements, including several historical elements in one request, and apply source-only edits without replacing the entire element set. Operational investigation and conversation search use narrower evidence and indexed identifiers, reducing unnecessary broad reads.
  </Accordion>
</AccordionGroup>

## Also in this release

* Default Agent Plugin configuration accepts plugin IDs only. Legacy free-form default-plugin instructions are removed during migration and rejected in new configuration requests.
* Agent Plugin skills and packages now enforce configurable prompt token budgets, with a 10,000-token default, before their guidance enters the Assistant context.
* Component element payloads no longer expose the obsolete `libs` field; dependency analysis remains available through supported authoring and validation flows.
* The post-1.5.8 fixes improve database index and View handling, Jobs and Trace details, group membership actions, Storage forms and Assistant activity projection.
* Node.js SDK 1.5.9, generated low-code declarations and the Platform API schema are aligned with the supported product contract.

## Related guides

* [Component authoring](/build/components)
* [Database Views](/operate/database-views)
* [Low-code API reference](/low-code/reference/api)
* [Dashboards](/operate/dashboards)
* [Assistant](/ai/assistant)
* [Node.js SDK](/developers/sdk-overview)

## Continue through the releases

[All releases](/releases/changelog) · [Earlier: 1.5.8](/changelog/1.5.8)