61 sources from practitioners, by month and sentiment.
Teams and data leaders praise Hex's AI agents most, followed by its SQL and Python notebook and published apps. Large notebooks and scheduled runs draw the most complaints about speed. Where accounts say whether Hex replaced their BI tool, most say it did.
Positive, mixed and negative sources
2211
The score counts them as 20 positive, 11 mixed and 0 negative votes, one per author. No source is negative. See How the numbers work.
Counted for Leaders and teams rolling it out, from 35 sources. Change group
What practitioners praise
Every capability practitioners describe positively, ranked by how many sources say so. Open one to read who said it.
1AI Agents15 of 17 sources on it praise itSQL and code generation by Hex's agents, including Magic, Notebook Agent, and Threads, and their answers about warehouse data.
After six months preparing clean Kimball models and a semantic layer, the commenter's company uses Hex as its BI tool, with 90% of use through Threads. It trades some quality for much faster development.
Published Oct 2, 2026self-described: Data team that prepared its dbt project for agents and uses Hex as its BI tool
Positive
Thiago Baldim, Director of Engineering, Data at Mitti
Mitti raised dbt test coverage from 40% to full coverage across more than 500 models before adding AI, and its clean lineage and documentation made natural-language analytics possible. Hex became the company's fastest-adopted AI tool, growing from 30 to 150 users in its first month.
"Hex became the company's fastest-adopted AI tool, growing from 30 to 150 users in its first month…"
Excerpt, Thiago Baldim
Published Sep 15, 2026Mitti's data team, which rebuilt more than 500 dbt models with full tests and documentation before rolling out natural-language analytics in Hex
At a larger company where Claude and Hex connect to the warehouse and semantic layer, the analyst finds the agent picks tables, writes and runs SQL, and checks results. That makes the work far more productive.
Published Aug 9, 2026self-described: Data analyst at a large company where Claude and Hex connect to the warehouse and semantic layer
A one-year user relies on Hex's built-in LLM agent for customer reporting, saying it roughly halved report-gathering time and saves about 20% of reporting effort, and wants AI review of finished work.
Published Jul 20, 2026self-described: Customer-facing data analytics reporting with a team
Mixed
Reviewer on G2 in Entertainment, Operations department head at a mid-market entertainment company
An operations head whose non-technical team builds visuals and automations with Hex AI says the new credit system would stop them. Some of the team use 500 credits against a 40-credit grant.
Published Jun 5, 2026self-described: Mid-market entertainment company (51 to 1,000 employees), operations team without SQL or Python experience
Mixed
Reviewer on G2 in Insurance, Dashboard builder at an enterprise insurance company
The reviewer says the new Hex agent fixes code far better than the old Magic assistant, but shared editing lets one teammate publish over another's changes, and large dashboard notebooks lag.
Published May 27, 2026self-described: Enterprise insurance company (more than 1,000 employees), team-built dashboards
Positive
tomtomau, Hacker News commenter and Hex workspace admin
As an admin at a long-time customer, the commenter values seeing what the team asks Hex's agent and where context is weak. They see generative apps answering requests to wire Claude straight to Snowflake.
Published May 13, 2026self-described: Company that has been a Hex customer for several years
Positive
Camden W., Manager, Analytics Engineering (G2 reviewer)
An analytics engineering manager uses Hex as one interface for BI assets and conversational analytics, replacing homegrown tools, and wants faster search and cached results for the Threads agent.
Published May 11, 2026self-described: Mid-market company (51 to 1,000 employees), small analytics team running BI and conversational analytics in Hex
A Hex admin runs the whole analysis workflow in Hex with its AI, but says non-technical users treat AI outputs as a source of truth despite errors and wants per-group rules.
Published May 8, 2026self-described: Small business (50 or fewer employees), analysis and monitoring dashboards
Positive
nonobility86, Reddit commenter in r/dataengineering
The commenter's team uses Hex: an exceptional analysis tool whose Threads agent works very well over the warehouse, though dedicated BI tools are better for dashboards alone.
Published Jan 20, 2026self-described: Team using Hex for analysis
Positive
Tom N., Co-Founder and Head of Data, AI, and R&D (G2 reviewer)
A head of data runs internal BI reporting in Hex; its agents read the Snowflake warehouse, dbt metadata, and past projects, and the reviewer wishes explorer seats cost less.
Published Nov 24, 2025self-described: Internal BI reporting on MySQL, PostgreSQL, and Snowflake with dbt metadata
Positive
Emily Hawkins, Analytics Engineering Manager at LangChain
LangChain layers dbt project docs, Hex workspace guides, a semantic layer, and endorsed models under its Hex agent, and rewrote column descriptions for an AI reader. Self-serve analytics questions rose 40x, and the data team shifted from answering every question to owning the context.
"The payoff was a 40x increase in self-serve analytics questions, letting the data team shift from answering every question to owning the context that lets other teams self-serve directly…"
Excerpt, Emily Hawkins
Published Sep 15, 2026LangChain's analytics engineering team, which keeps its Hex agent grounded with dbt docs, workspace guides, a semantic layer, and endorsed models
Positive
Emily Hawkins, LangChain data team (byline author)
LangChain's data team left its legacy BI tool for Hex in six weeks. Its Hex-based data agent now handles about 40x the requests the three-person team could field, with analysts still validating important answers.
Published Jul 27, 2026self-described: LangChain, three-person data team serving the whole company
A VP of data builds dashboards faster in Hex than in Power BI. At several companies, though, scheduled runs froze, piled up, and crashed the kernel, with days of downtime until support cleared them.
Published Nov 17, 2025self-described: Data leader who has run Hex at multiple companies
The commenter's team upgraded its Hex license for the built-in agent and opened its semantic layer to it; the agent is good but needs a solid context file and well-written prompts.
Published Nov 12, 2025self-described: Team that upgraded its Hex license for the AI agent and opened its semantic layer to it
Mixed or negative, 2
Mixed
Reviewer on G2 in Higher Education, Developer at a mid-market higher education organization
The reviewer says Hex gives engineers and analysts one place to work, but found Magic useless for developers next to ChatGPT, and stakeholders miss totals in pivot tables.
Published Mar 13, 2025self-described: Mid-market higher education organization (51 to 1,000 employees), company dashboards and reports
Mixed
Reviewer on G2 in Information Technology and Services, Developer of LLM applications at a small IT services company
The reviewer rates Hex's notebook above Mode and Tableau and says it connects well to Snowflake and ClickHouse, but finds Hex Magic weaker than plain ChatGPT and support slow.
Published Jan 30, 2025self-described: Small IT services company (50 or fewer employees), team data science projects
2Analysis Workspace11 of 12 sources on it praise itSQL and Python analysis alongside no-code cells in Hex's reactive notebook, including everyday analysis speed.
The reviewer likes chaining SQL and Python cells, but says their team's use of components to share metrics across notebooks produced bloat, and chart customization is thin.
Published Nov 18, 2025self-described: Team sharing Snowflake and Redshift connections
Positive
Ethan Brown, Director, Data & Applied Science at Amazon Web Services
Brown's team uses Hex as its BI tool and finds the notebook-first layout very helpful. Each day, Airflow pulls the YAML file of each Hex project and an LLM summarizes it, and the team's Slack bot uses those summaries to recommend trusted reports.
"We use Hex as a BI tool, which is quite nice…"
Excerpt, Ethan Brown
Published Apr 22, 2025Data and applied science team for Amazon IVS and Twitch Video, which runs its BI in Hex and feeds Hex project files to its own Slack bot
Positive
Reviewer on G2 in Telecommunications, Report builder at a mid-market telecommunications company
The reviewer gets dashboards running quickly, switching between Python and SQL and querying dataframes, and calls the cost fair, though scheduled and cached runs sometimes return different results.
Published Apr 10, 2025self-described: Mid-market telecommunications company (51 to 1,000 employees), reports for system design
Mixed
Reviewer on G2 in Information Technology and Services, Developer of LLM applications at a small IT services company
The reviewer rates Hex's notebook above Mode and Tableau and says it connects well to Snowflake and ClickHouse, but finds Hex Magic weaker than plain ChatGPT and support slow.
Published Jan 30, 2025self-described: Small IT services company (50 or fewer employees), team data science projects
Mixed
Reviewer on G2 in Insurance, Dashboard builder at an enterprise insurance company
The reviewer says the new Hex agent fixes code far better than the old Magic assistant, but shared editing lets one teammate publish over another's changes, and large dashboard notebooks lag.
Published May 27, 2026self-described: Enterprise insurance company (more than 1,000 employees), team-built dashboards
An analytics manager builds dashboards quickly by chaining SQL, but slow loads push colleagues to Looker Studio, and link sharing exposes a dashboard to the whole workspace.
Published Mar 23, 2026self-described: Mid-market company (51 to 1,000 employees), dashboards for a wide internal audience
Positive
nonobility86, Reddit commenter in r/dataengineering
The commenter's team uses Hex: an exceptional analysis tool whose Threads agent works very well over the warehouse, though dedicated BI tools are better for dashboards alone.
Published Jan 20, 2026self-described: Team using Hex for analysis
A VP of data builds dashboards faster in Hex than in Power BI. At several companies, though, scheduled runs froze, piled up, and crashed the kernel, with days of downtime until support cleared them.
Published Nov 17, 2025self-described: Data leader who has run Hex at multiple companies
Without a data engineer on the team, an analyst moved dbt models and old dashboards into Hex, now the company's only BI tool. On their plan they cannot work with tables of millions of rows.
Published Oct 27, 2025self-described: Mid-market company (51 to 1,000 employees), Hex is the company's only BI tool
Mixed
Reviewer on G2 in Sporting Goods, Data scientist at a mid-market sporting goods company
A data scientist builds forecasting models their team can rerun, but Hex bogs down once a pandas dataframe passes a million rows, and the reviewer switches tools for quick charts.
Published Feb 5, 2025self-described: Mid-market sporting goods company (51 to 1,000 employees), forecasting models
A data scientist develops in local Jupyter and moves work to Hex to share it, since Hex pins old Python and pandas versions and its chart editor adds latency for power users.
Published Jan 28, 2025self-described: Mid-market company (51 to 1,000 employees), team with mixed notebook experience
The reviewer gets dashboards running quickly, switching between Python and SQL and querying dataframes, and calls the cost fair, though scheduled and cached runs sometimes return different results.
Published Apr 10, 2025self-described: Mid-market telecommunications company (51 to 1,000 employees), reports for system design
Positive
Reviewer on G2 in Mental Health Care, Data analyst supporting the business side at a mid-market mental health care company
An analyst builds three or four Hex dashboards every two weeks, and stakeholders now request Hex apps for team, department, and company metrics; the reviewer compares it favorably with Looker.
Published Feb 11, 2025self-described: Mid-market mental health care company (51 to 1,000 employees), dashboards for business stakeholders
A data scientist develops in local Jupyter and moves work to Hex to share it, since Hex pins old Python and pandas versions and its chart editor adds latency for power users.
Published Jan 28, 2025self-described: Mid-market company (51 to 1,000 employees), team with mixed notebook experience
A one-year user relies on Hex's built-in LLM agent for customer reporting, saying it roughly halved report-gathering time and saves about 20% of reporting effort, and wants AI review of finished work.
Published Jul 20, 2026self-described: Customer-facing data analytics reporting with a team
Their company uses Hex to put all its data in one place and see what is happening at high and low levels, finding it customizable with a simple interface.
Published Feb 24, 2025self-described: Startup putting its data in one place
Mixed or negative, 3
Mixed
Cormac M., Senior Data Analytics Manager (G2 reviewer)
An analytics manager builds dashboards quickly by chaining SQL, but slow loads push colleagues to Looker Studio, and link sharing exposes a dashboard to the whole workspace.
Published Mar 23, 2026self-described: Mid-market company (51 to 1,000 employees), dashboards for a wide internal audience
A VP of data builds dashboards faster in Hex than in Power BI. At several companies, though, scheduled runs froze, piled up, and crashed the kernel, with days of downtime until support cleared them.
Published Nov 17, 2025self-described: Data leader who has run Hex at multiple companies
Mixed
Reviewer on G2 in Higher Education, Developer at a mid-market higher education organization
The reviewer says Hex gives engineers and analysts one place to work, but found Magic useless for developers next to ChatGPT, and stakeholders miss totals in pivot tables.
Published Mar 13, 2025self-described: Mid-market higher education organization (51 to 1,000 employees), company dashboards and reports
The reviewer gets dashboards running quickly, switching between Python and SQL and querying dataframes, and calls the cost fair, though scheduled and cached runs sometimes return different results.
Published Apr 10, 2025self-described: Mid-market telecommunications company (51 to 1,000 employees), reports for system design
Mixed
Reviewer on G2 in Sporting Goods, Data scientist at a mid-market sporting goods company
A data scientist builds forecasting models their team can rerun, but Hex bogs down once a pandas dataframe passes a million rows, and the reviewer switches tools for quick charts.
Published Feb 5, 2025self-described: Mid-market sporting goods company (51 to 1,000 employees), forecasting models
Mixed
Reviewer on G2 in Information Technology and Services, Developer of LLM applications at a small IT services company
The reviewer rates Hex's notebook above Mode and Tableau and says it connects well to Snowflake and ClickHouse, but finds Hex Magic weaker than plain ChatGPT and support slow.
Published Jan 30, 2025self-described: Small IT services company (50 or fewer employees), team data science projects
A data scientist develops in local Jupyter and moves work to Hex to share it, since Hex pins old Python and pandas versions and its chart editor adds latency for power users.
Published Jan 28, 2025self-described: Mid-market company (51 to 1,000 employees), team with mixed notebook experience
Mixed or negative, 2
Mixed
Reviewer on G2 in Insurance, Dashboard builder at an enterprise insurance company
The reviewer says the new Hex agent fixes code far better than the old Magic assistant, but shared editing lets one teammate publish over another's changes, and large dashboard notebooks lag.
Published May 27, 2026self-described: Enterprise insurance company (more than 1,000 employees), team-built dashboards
The reviewer likes chaining SQL and Python cells, but says their team's use of components to share metrics across notebooks produced bloat, and chart customization is thin.
Published Nov 18, 2025self-described: Team sharing Snowflake and Redshift connections
An analytics manager builds dashboards quickly by chaining SQL, but slow loads push colleagues to Looker Studio, and link sharing exposes a dashboard to the whole workspace.
Published Mar 23, 2026self-described: Mid-market company (51 to 1,000 employees), dashboards for a wide internal audience
A VP of data builds dashboards faster in Hex than in Power BI. At several companies, though, scheduled runs froze, piled up, and crashed the kernel, with days of downtime until support cleared them.
Published Nov 17, 2025self-described: Data leader who has run Hex at multiple companies
Without a data engineer on the team, an analyst moved dbt models and old dashboards into Hex, now the company's only BI tool. On their plan they cannot work with tables of millions of rows.
Published Oct 27, 2025self-described: Mid-market company (51 to 1,000 employees), Hex is the company's only BI tool
Mixed
Reviewer on G2 in Sporting Goods, Data scientist at a mid-market sporting goods company
A data scientist builds forecasting models their team can rerun, but Hex bogs down once a pandas dataframe passes a million rows, and the reviewer switches tools for quick charts.
Published Feb 5, 2025self-described: Mid-market sporting goods company (51 to 1,000 employees), forecasting models
Mixed
Reviewer on G2 in Insurance, Dashboard builder at an enterprise insurance company
The reviewer says the new Hex agent fixes code far better than the old Magic assistant, but shared editing lets one teammate publish over another's changes, and large dashboard notebooks lag.
Published May 27, 2026self-described: Enterprise insurance company (more than 1,000 employees), team-built dashboards
Positive
Camden W., Manager, Analytics Engineering (G2 reviewer)
An analytics engineering manager uses Hex as one interface for BI assets and conversational analytics, replacing homegrown tools, and wants faster search and cached results for the Threads agent.
Published May 11, 2026self-described: Mid-market company (51 to 1,000 employees), small analytics team running BI and conversational analytics in Hex
Discussed without concern, 2
No opinion stated
David Cramer, Sentry (issue filed through Sentry's Junior agent)
Asking Sentry's agent for today's paid-account count took about 4 minutes 18 seconds. Ten Hex get_thread polls took about 166 seconds, most about 18 seconds each, and the team plans one result-focused Hex call.
Published Sep 25, 2026self-described: Sentry's internal Slack agent, Junior, answering business questions through Hex Threads over MCP
A one-year user relies on Hex's built-in LLM agent for customer reporting, saying it roughly halved report-gathering time and saves about 20% of reporting effort, and wants AI review of finished work.
Published Jul 20, 2026self-described: Customer-facing data analytics reporting with a team
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.Medium compute (8 GB, 1 CPU) is included on paid plans. Team and Enterprise can add larger profiles billed per minute, from US$0.32 an hour. Hex pricing
Questions the sources split on, with the count on each side.
Evidence remains mixed
Does Hex replace a team's BI tool?
82
Replaces BI, 8 sources
Some run their dashboards and reports in Hex and retired or never adopted a separate BI tool.
Alongside BI, 2 sources
Others use Hex for analysis that a BI tool handles poorly and keep a BI tool for dashboards.
The evidence
Whose experience this is
The three groups, then every practitioner by the context they work in, and how emphasis changes with scale.
Three groups drawn from the same sources. Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. Signals open on Leaders and teams rolling it out.
Leaders and teams rolling it out
35 sources. Accounts from data teams and departments, including leaders choosing an analysis workspace for their company.
Individual users
26 sources. Accounts from individual analysts and data scientists using Hex for their own work.
All users
61 sources. All reviewed accounts, combining solo analysts with teams opening Hex to business users. Their conclusions differ.
61 sources from practitioners, by the context they work in. Filled rows count for this group.
Individual userOne person using it for their own work26 sources
Emphasizes The SQL and Python notebook, and speed on large datasets
Small team2 to 10 people sharing it16 sources, counted here
Emphasizes Shared notebooks and reusable components
DepartmentA department, or a named company's team10 sources, counted here
Emphasizes Apps for stakeholders and AI help with SQL
IT & leadershipIT and business leaders deciding the rollout7 sources, counted here
Emphasizes Agents for non-technical staff, and what seats and credits cost
Organization-wideCompany-wide rollout2 sources, counted here
Emphasizes Curated context for a company-wide data agent
What changes with scale. Individual analysts talk about the notebook and its speed. Small teams add shared components and the apps they publish. Data leaders weigh whether non-technical staff can use the agents and what seats and credits will cost.
Where the sources come from
Where this group's sources were published.
Counted for Leaders and teams rolling it out, from 35 sources. Change group
50 sources for this group, 15 of them documentation
Blogs, Newsletters & Reviews19, 38% of 50 sources
Product Documentation15, 30% of 50 sources
Data Communities11, 22% of 50 sources
Videos5, 10% of 50 sources
Every public account is dated 2025 or later. Sources that review a feature Hex has since replaced, such as Magic, stay in the record because their point about Hex still holds.
Removes the 22 public accounts dated before 2025 and a competitor's roundup of 14 analytics agents.
Adds 29 G2 reviews and six Reddit comments from r/dataengineering, so the page draws on 61 public accounts from Jan 28, 2025 to Oct 2, 2026.
Shows a finding for an audience only when at least 5 sources from 3 different authors discuss it, and a disagreement only with at least 2 sources on each side.
Restores Warehouse Connections as a theme with 6 sources. Cost (3 sources) and Version Control & Portability (5) each have fewer than 5 sources from 3 authors and appear only in Evidence & Methodology; AI answer accuracy (0) is not a theme.
Checks every documentation page against Hex's current documentation and pricing.
Oct 25, 2026: adds 2 GitHub sources, a production regression in Hex's run status API and Sentry's measured Threads response times.
Oct 26, 2026: adds 5 talks from dbt Summit 2026 and Data Council 2025. The speakers are named data leaders and teams at Mitti, Genius.AI, Amazon IVS and Twitch, Basecamp Research, and LangChain.
Method
A running review of what people using Hex at work report, from individual users to company-wide rollouts. Each finding links to its sources, and each conflict shows both sides.
Counts cover only the sources GILD reviewed.
Who counts
Leaders and teams rolling it out
Small team, Department, IT & leadership, Organization-wide
Individual users
Individual user
All users
Everyone in the leaders and teams and individual users groups
Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. GILD files each source in a group from how the account describes its author. A role or employer marked self-described is what the source states about themselves. Documentation checks facts for every group and never counts toward sentiment.
How the numbers work
Overall signal. Positive votes minus negative ones, per 100 votes from the sources that take a side. Each author counts once, with their latest view, whoever they are and wherever they posted. The older weighted reading, where accounts GILD matched to a named person count three times when GILD lists the author among IT and business leaders and twice otherwise, is shown beside it as a second view. Where an author wrote more than one source, the line beside the split gives the votes, one per author, so the score follows from it. When one author's sources from the same day disagree, that author counts as mixed, and a half point rounds away from zero. Sources with no opinion are listed and not counted. Strong positive is +50 or higher, positive +20 to +49, mixed −19 to +19, negative −20 to −49, strong negative −50 or lower.
Weighted reading, second view. Counted the older way, where an account GILD matched to a named person counts two or three times, leaders and teams read +74 strong positive (method sentiment/S1). GILD printed that number as "GILD score" until October 29, 2026; most of those matches rest on a name or a self-described role.
Method change, Oct 30, 2026. GILD changed how practitioner sentiment counts, to one vote per author. Weighted, it read +74 Strong positive; with one vote per author it reads +65 Strong positive. No evidence changed.
Unscored. A group gets a score only with 20 sources from 15 authors. Below that, one source moves the score about 5 points, so the read says "Unscored until 20 sources from 15 authors" and shows its counts.
Independence. A source whose author works for the vendor, for one of its partners or programs, or for a competitor, and a page the vendor published or ran, is listed with that tie and counts toward nothing. One author counts on at most two records per product. The line under the score says how many authors and how many separate discussions the counted sources come from: comments in one thread are one discussion.
Praise and concerns. How many of the sources that discuss a theme praise it or raise it.
Consensus. A statement joins when 20% of the group's sources support it and fewer contradict it. Contradicting sources are counted separately. Below that line a statement shows as building. At 40% or more it reads Strong agreement; below, Recurring point.
Disagreements. The count on each side. GILD names no winner and gives no share of all users.
Minimum evidence. A finding needs 5 sources from 3 authors; a disagreement also needs 2 on each side. Smaller counts stay in the table below, marked under the minimum.
Labels on a source
A source's date and whether it still applies are separate: a recent post can describe an old version, and an old one can still hold.
Documented
Stated in official documentation.
Reported
A practitioner's account of their own use.
Measured
Backed by the source's own measurements, such as a comparative test or tracked team metrics.
GILD analysis
GILD's check of a claim against official documentation.
Current
Describes the product as it is now.
Still applicable
Older, and the behavior or lesson still holds.
Needs a recheck
May depend on a plan, version or setting that changed since it was written. It keeps counting until GILD rechecks it, since the rest of the account usually holds, and its card says so.
Out of date
No longer accurate. Kept in the record; counts toward nothing current.
Flagged for a recheck, of the sources that take a side: leaders and teams 0 of 33, individual users 0 of 26, all users 0 of 59.
Limits
These figures count reviewed public sources. They are not a customer survey. 29 of 61 sources are G2 reviews read from Internet Archive captures because G2 blocks automated fetches. G2 labels most as incentivized reviews collected on Hex's behalf, and they lean positive. Reddit comments came from the Arctic Shift archive. GILD also checked TrustRadius, Capterra, and PeerSpot; each blocks copies of its pages, so the review evidence comes from G2, Product Hunt, and AWS Marketplace. 2 sources describe company-wide use: LangChain's data agent and Sentry's Slack agent, which answers business questions through Hex.
Sources name their plan and features inconsistently. Reviews from early 2025 describe Magic, the AI assistant Hex had before the Notebook Agent (August 2025) and Threads (October 2025). A June 2026 review describes credit limits that were about to start.
Every count, and the sources behind it
18 findings for 3 groups
Each row opens its sources for the group you are reading.
GILD's checks of claims against official documentation, kept apart from the source counts.
Speed. Medium compute (8 GB, 1 CPU) is included on paid plans. Team and Enterprise can add larger profiles billed per minute, from US$0.32 an hour. Hex pricing, checked Oct 12, 2026
Fit for Business Users. Threads is intended for people outside the data team and available to Explorer roles and above on every plan. The Notebook Agent is intended for technical users who can audit its SQL and code. AI in Hex, checked Oct 12, 2026
Cost. Every Hex agent run consumes credits by effort, and paid seats get monthly grants that do not roll over. Admins can cap add-on spend with an auto top-up limit and per-user or per-group credit limits. Credits, checked Oct 12, 2026
Version Control & Portability. Git project export and package import are on Team and Enterprise, and eval suites are YAML files that can live in version control alongside context files. Evals, checked Oct 12, 2026