Changelog

🔒 Governed mode​

Previously, workspace admins could restrict the data available to the Hex agent for Explorers by enabling Endorsed mode, which limited access to tables, models, and projects marked as “Endorsed.”

Governed mode takes things one step further and lets admins define their own rules for which data sources the Hex agent can access for Explorers, rather than relying solely on the “Endorsed” classification.

Some ways to set it up:

• Semantic models only: Have the agent answer using only your defined metrics, without querying warehouse tables directly or exploring projects.
• Projects only: Have the agent use dashboards and analyses your team has already built. It can run projects and change inputs, but won’t write new warehouse queries.
• A custom mix of sources: For example, you could use all semantic models, only warehouse tables marked Gold, and only projects marked Certified or Trusted.

Already using Endorsed mode? Nothing changes. Your settings carry over as a Governed mode configuration that allows only endorsed data.

Governed mode controls what the agent uses, not what people can access. Anyone with access to a data connection can still query it directly. To restrict data access, set permissions in your warehouse.

Admins can set up Governed mode in Settings > Governed mode.

📊 Access usage and credit grants data​

Admins need a clearer picture of who’s using credits, and on what.

Agent Usage and Credit Spend API endpoints let Admins pull historical agent activity and credit purchase data from their Hex workspace.

Use the data to:

• Create daily usage reports to track credit consumption trends
• Attribute costs by user or group for chargebacks
• Monitor budgets by setting up alerts for spending thresholds
• Generate finance reports with detailed use and purchase data

Access this data via API, or pull it directly into your agent or terminal through the Hex MCP server or CLI.

Available to workspace Admins on Enterprise plans.

⬆️ Import Apache Ossie models​

If you’ve already defined your business logic in Apache Ossie, bringing it into Hex shouldn’t mean rebuilding the model by hand. Now you can convert an Ossie model into Hex semantic-project YAML with the Hex CLI:

hex context semantic-project convert \
  --from=ossie \
  --to=hex \
  --input your-model.ossie.yaml \
  --output ./hex-model/

This one-way conversion saves files locally for review.

To bring them into your workspace, configure sync for a semantic project in Settings → Data sources → Semantic projects. Test the changes on a dev branch, then merge to main to import them into Hex.

🗂️ Agent activity classifications​

Where someone opens the agent doesn’t tell you much about what they’re working on. People often explore data in a notebook, and a thread that starts as a quick question can end with a finished app.

Context Studio now categorizes agent activity by what they’re for, not where they started. Instead of separate "Threads" and "Notebook agent" categories, filters and charts now show three types:

• Analysis: asking questions and exploring data
• App building: building or improving an app, dashboard, or notebook
• Modeling: building and editing semantic models

Managers and Admins can now see how their workspace uses the agent: how much is analysis and how much is building for others. Filter by type in Context Studio or with hex thread list --classification.

⚡ Fast chart edits in Generative Apps​

A small chart edit shouldn’t require the full Hex Agent. Hex can now route targeted changes (like moving a legend, adjusting formatting, or adding a metric to the tooltip) to a smaller, faster model to reduce both wait time and token usage.

If a request goes beyond a simple property change, it goes to the full Hex Agent as usual, so you don’t have to decide which to use.

💬 Chat with Generative Apps​

Data apps are built to answer questions, but the best insights often lead to new ones. Explorers can now chat with published Generative Apps to ask follow-up questions, investigate metrics, and keep exploring in an agent Thread without leaving the app.

Tip: @-mention a specific cell or name the tab or section you’re viewing, along with any relevant filters or inputs.

Learn more about Chat with App.

📎 Schedule CSV exports for Generative Apps​

You can already set scheduled notifications for your Generative Apps, giving your stakeholders updated insights when they need it. Now you can include a CSV export.

Scheduled exports use the project’s underlying cell outputs — not transformations made in the app interface. Before scheduling an export, confirm that its cell outputs contain only data appropriate for the notification’s recipients.

🤖 New models to pick from​

Different tasks call for different models. Six new options are now available in Hex:

• Opus 5.5 for hard, open-ended investigations
• Fable 5.1 for complex, nuanced work
• GPT 6 Sol for maximum reasoning depth on tough problems
• GPT 6 Astra for involved analytical work
• GPT 6 Luna for quick, lightweight tasks
• Grok 4.6 for another model to try across everyday workflows

GPT 6 Sol, Astra, and Luna also support an optional Fast mode for quicker responses, at a higher credit cost.

Availability: Fable 5.1 is available on multi-tenant and non-EU, non-HIPAA single-tenant stacks.

To enable Fable 5.1, go to Settings → AI & Agents and turn on Allow data retention for specific models. No action is needed for the other models, they're already available in the model picker in the prompt bar.

⚖️ Publish and version eval suites​

Did last week’s guide change actually make the agent better? Now you can answer that question without rerunning every test by hand.

Publish an eval suite from the CLI, schedule it to run automatically, and track its performance over time in Context Studio.

Turn the questions you test repeatedly into a versioned suite, then compare results as your guides or semantic models evolve. You’ll quickly see what improved agent performance or get an earlier warning when a change causes a regression.

Publishing and scheduling eval suites requires a Manager or Admin workspace role. Learn how scheduled evals work.

✅ Skip agent approvals​

No one wants to babysit their agent or come back to find it waiting for approval. Now you can let the Hex Agent run in YOLO mode (responsibly, of course).

There are two options in the prompt bar when building with the Hex Agent, you can either:

• Stick with Ask for approval mode and the agent will pause for confirmation before destructive actions like deleting a cell or publishing.
• Choose Skip approvals mode and the agent works straight through without pausing for confirmation on every edit. Don’t worry, you can still undo changes from the last agent turn.

Anything that expands access like granting OAuth, reconnecting an app, or authorizing an MCP server still stops and waits for your approval.

🛠️ Your chat agent can build in Hex​

Your chat agent can do a lot more than ask Hex questions.

Once you connect Hex to an MCP client like Claude, ChatGPT, or Cursor, your agent can create, retrieve, and update Hex projects with the create_project, get_project, and update_project tools.

That means you can stay in your chat agent to:

• Investigate what happened and why with an ad hoc analysis
• Plan what happens next with a forecast or scenario model
• Turn a recurring workflow into an interactive data app

Project editing requires an Editor role or higher and the appropriate project permissions. Changes made through MCP apply directly to a project’s draft notebook, so they do not update its published app version.

Learn more about editing Hex projects via MCP.