What happened
Greptile’s October 28, 2026 changelog entry announces computer use in TREX, its pull-request testing product. The entry says TREX starts the services touched by a change and then tests them end to end using computer control. It can work with desktop applications, browsers, and terminals as a real user would. When a flow requires more than one of those environments, TREX can use them at the same time. The entry also says it tests edge cases in parallel.
The update builds on TREX’s general availability announcement from October 16. Greptile describes TREX as a system that tests pull requests by starting an app in a sandbox and clicking through the flows affected by a change. Teams configure the environment with a setup script, build variables, setup instructions, and network access. They can test the setup with TREX Simulation. User journeys are specified step by step in Memory → TREX Flows.
Greptile says each tested flow links to a captioned video showing TREX using the app. A TREX run costs 3 credits and works with every review tier. The computer-use entry does not state a separate price, a new tier, or a change to those setup requirements. In practical terms, the update adds a way to operate the running application as part of the existing TREX testing workflow; teams still need an environment that can build and start their repository and flows that describe what should be exercised.
The changelog does not describe a particular browser automation engine, supported operating systems, or additional configuration specific to computer use. Nor does the announcement provide a new benchmark or measured result for this capability. Its concrete claim is about the kinds of interfaces TREX can operate and its ability to test multi-part flows and edge cases in parallel.
What the archive adds
New Runtime’s earlier coverage on October 27 described Greptile using GPT-6 Astra for application-level workflow testing, including simulated mobile use: Greptile takes bug detection beyond code review with GPT-6 Astra. This is a new product fact on a known story: the changelog now describes computer use as a TREX capability, rather than only a model-powered testing workflow.
Trend signal
This does not yet fit a pattern New Runtime tracks. The update is a specific product capability, but it does not by itself establish a broader shift in agent architecture, economics, or security boundaries.
Why now
The announcement follows TREX’s general availability on October 16, 2026. Teams could already configure TREX to start an app in a sandbox, test affected flows, and attach videos. The October 28 update extends that product’s interaction surface to computer use across desktop apps, browsers, and terminals.
Connections to other events
New Runtime’s October 27 coverage described Greptile using GPT-6 Astra to simulate application workflows, including mobile use, to find bugs that code review might miss. The current changelog entry connects that application-level testing direction to a named TREX capability: computer use across desktop software, browsers, and terminals.
Why it matters
Pull-request checks often validate code without exercising the complete path a user takes through a running application. Computer use can bridge that gap when a change depends on a sequence of interface actions, a browser flow, or interaction between an app and its supporting services. For teams already using TREX, this could make it easier to include those journeys in PR testing without treating every interface check as a separate manual exercise.
The announcement is especially relevant where regressions arise from interactions among components rather than from an isolated function. It also makes test design important: a tool can only exercise the paths a team configures or that it otherwise determines to test. TREX’s existing flow configuration and video evidence offer a place to inspect what was tested, but teams should still treat results as test evidence to review, not as proof that every user path is correct.
What happens next
- Greptile will document computer-use setup details beyond the changelog entry (6 months, 60%). Watch for: new TREX documentation covering configuration, supported environments, or access requirements.
Limits and uncertainty
Greptile’s announcement does not quantify how many additional defects computer use finds, how often its flows succeed, or how its results compare with conventional end-to-end testing. It does not specify the computer-control implementation, the supported operating systems, or whether every desktop application can be driven. Those details matter for teams assessing reliability and compatibility. The stated 3-credit cost applies to a TREX run; the announcement does not break down costs by flow, parallel edge case, or computer-use activity. These product claims have not been independently measured here.
Skill to build now
Pick one pull request that changes a user-facing flow and write down the shortest reproducible journey that would demonstrate the change: starting state, actions, and expected result. If you use TREX, configure that journey in Memory → TREX Flows, confirm its sandbox can start the affected services, then inspect the linked video and result. This gives the team a concrete test of whether computer use covers a meaningful path in its own application.
Reader takeaway
TREX’s new computer-use capability lets it exercise pull requests through real interfaces across desktop apps, browsers, and terminals. The practical value depends on whether a team can provide a working environment and meaningful flows—and on validating the resulting evidence rather than assuming the announcement establishes test coverage or accuracy.