1.267

As a step toward integrating AI services into the  Model client, users can now provide their own opencode.json that is loaded in addition to the bundled default configuration of the desktop AI assistant. This allows for user-specific customization.

• Users can place their own opencode.json into the datadir, where it is read by the client.
• The file is loaded in addition to the bundled default configuration and deep-merged with it. User-specified fields override the defaults, while all other defaults remain unchanged.

The POST /api/v1/pool-entries/state/get endpoint (get_pool_entry_states / get_pool_entry_and_supplement_states) is a building block for client–server sync. The client submits a list of known UUIDs and receives back a SyncObjectStatus per entry (containing uuid, change_tag, type, change_utc_offset). The endpoint has been extended to allow clients to:

• Filter by epoch: Returns only entries whose epoch value is greater than or equal to a given threshold, enabling true incremental sync.
• Resolve children recursively: Given a set of root UUIDs, automatically includes the states of all transitive supplements and hierarchically owned child entries.

This fix relates to the process of creating collections, i.e. user-specific groups of run configurations. When a user adds run configurations to a new collection, the default name New collection appears. Previously, when a user then clicked on New collection, this text disappeared and the collection was displayed without a name. This behavior has been fixed. The default name no longer disappears and it can be edited as needed.

Previously, content was sometimes displayed in the wrong order in the Properties view. This occurred in sections that have sub-sections. For example, the Owner sub-section appeared at the wrong location within the Basic Information section. This behavior has been fixed.

Previously, changing an attribute value, e.g. setting an additional attribute, caused the Properties view to automatically scroll down. This behavior has been fixed. The scrolling position no longer changes unless users scroll down themselves.

Previously, the new component grid did not show the matching components correctly for auxiliary attributes. The Run matches column and the grid itself showed components as matching, even though they did not match. This behavior has been fixed.

Note: Assembly was not affected by this issue. The correct components were always exported during assembly.

This fix relates to the Groups and Runs areas. The ascending and descending sort icons were previously switched in these areas. The icons now correctly indicate:

•   Sorted in alphabetical order (A-Z).
•   Sorted in reverse alphabetical order (Z-A).

In some cases, background actions (such as synchronization or automatic updates) fail because the user’s login session has expired or cannot be renewed without user interaction. Previously, the application showed a generic error instead of clearly telling users that they needed to sign in again. This has been fixed. The correct authentication error is now preserved and surfaced to the user with a specific message, such as ‘Your session has expired, please sign in again.’