August 6, 2026
Model deployment visibility control
← All updates
Model deployment visibility control
5 improved 6 fixed
Model visibility is now an explicit hidden attribute set by operators
Improvements
- Model deployment visibility control. Model visibility is now an explicit
hiddenattribute set by operators, replacing the previous name-prefix convention — hidden models are excluded from pickers, member grants, and SDK keys. - Agent output stat cards as filter toggles. The “Needs review” and “Critical + High” stat cards on the Agent Outputs page are now clickable filter toggles, and the items grid has a new sortable “Updated” column.
- Self-hosting configuration docs overhauled. Self-hosting docs now provide consistent, copyable configuration guidance across the Helm, Admin Console, and KOTS ConfigValues install paths.
- Media gallery color coding. Media preview and the session media gallery now use color coding by media kind and an improved layout.
- Agents Charts subtab removed. The Agents Charts subtab has been retired; existing links redirect to the Sessions list, which already surfaces the same information accurately.
Fixes
- E2B detached commands now run to completion. E2B sandboxed runtimes no longer terminate mid-generation after ~40–45 seconds; detached commands run to completion.
- DataGrid no longer overwrites results with stale responses. Rapid filter, sort, or pagination changes no longer cause the table to flash back to outdated data — only the latest server response is applied.
- Session Media tab no longer shows “No media” when media exists. A bad ClickHouse filter on an always-empty column was silently dropping all media results; the Media tab now returns correct results.
- ”+ New Workspace” stays pinned at the bottom of the workspace switcher. The entry no longer floats upward regardless of how many orgs or workspaces you belong to.
- Webhook connection creation no longer returns a 422 error. Creating a webhook connection in Org Settings → Integrations now completes successfully.
- Actionable hashcat error on GPU-less environments. The
hashcattool now returns a clear error directing agents to usejohn_the_ripperwith the correct hash format instead of an opaque failure.