Hopper Review

★7.9/10

An AI agent environment for navigating TN3270, datasets, jobs, and z/OS workflows from one mainframe-aware workspace.

Review updated May 2026 • By The AI Way Editorial • 5 min read

Hypercubic Mac App No Credit Card Required Windows App Freemium

Our Verdict

Hopper is worth opening when the hard part of the job is not writing code from scratch, but moving safely through TN3270 screens, datasets, JCL, JES spool, and CICS steps that normal coding assistants cannot actually operate. Its real value is that the agent works inside the same mainframe session you are viewing, so debugging and change work stay tied to the live environment instead of getting flattened into pasted snippets. The cost is that this is a narrow tool. If your team does not live in z/OS work, Hopper's main advantage disappears fast.

Official site

A free plan is listed; verify current limits before upgrading.

open_in_new Try Hopper

Official Website Snapshot Visit Site ↗

Hopper official website and landing page preview

Visit Official Site ↗

check_circle Pros

✓It tackles a real mainframe bottleneck instead of pretending COBOL work is just another repo chat problem.
✓The shared-session design makes the agent's terminal moves, job submissions, and dataset reads visible instead of hidden behind a black box.
✓The approval flow is strict where it matters, because writes, job submissions, and CICS changes stop for review before anything mutates state.

cancel Cons

✕The product is highly specialized, so teams without regular TN3270, JES, VSAM, or CICS work will get very little out of it.
✕A lot of the promised payoff depends on shop-specific conventions such as compile procedures, dataset naming, and subsystem quirks that can vary sharply by customer.
✕HN reactions show an obvious trust hurdle around training data, customer IP, and language coverage beyond the cleaner COBOL examples on the landing page.

Should you use it?

mainframe teams debugging jobs, tracing spool, reading datasets, and making controlled changes in z/OS

Skip it if: your developers mostly live in Git repos and cloud CI, not JES, TN3270, datasets, or CICS

Is it worth the price?

Freemium

The free plan is credible because it lets you test Hopper on real mainframe work instead of a crippled toy tier. You only need the paid tier once security controls, deployment boundaries, or admin governance become part of the buying decision. The bigger money question is not Hopper alone, but whether it earns its keep inside an ecosystem where legal access, environment setup, and mainframe infrastructure are already expensive before AI enters the stack.

The Free Tier

Hobby is free, needs no credit card, runs on macOS, Windows, and Linux, and includes connection to your own mainframe plus core Hopper features.

Paid Upgrade

Custom

Enterprise adds SAML SSO, MCP Server Access, admin and model controls, org-wide privacy controls, no model training, priority support, and on-prem or VPC deployment.

One thing to know before you start

A failed batch job your team already knows well will tell you more than any polished demo. If Hopper can pull the spool, find the failing step, and stop at the right approval point, the fit becomes obvious quickly.

What people actually use it for

Debug a failed batch job from spool to source without hopping across separate tools

Hopper is strongest when the expensive part of the work is tracing a failure across JES output, return codes, dataset state, and the source member that caused it. That is a better fit than a generic assistant when the diagnosis path lives in SDSF-style surfaces, not only in code files.

Make controlled changes in a z/OS workflow where every mutation needs review

The product fits teams that want help writing JCL, editing members, or touching CICS resources, but still need a human checkpoint before anything changes state. That matters in environments where one careless write or submit step can create operational noise far beyond a normal dev sandbox.

Help newer engineers learn how the shop's mainframe workflow actually hangs together

Hopper can help when the hard part is not COBOL syntax itself, but understanding how datasets, jobs, return codes, terminal screens, and subsystem steps fit together in one working path. The shared session and attachable @ references give a junior developer something more concrete than copied screenshots and tribal knowledge. It will not replace experienced review, but it can shorten the time it takes to see what is happening.

What does Hopper actually do?

Most AI coding tools assume the work lives in a repo, a terminal, and a test run. Mainframe work breaks that loop fast. The clue you need may be on a TN3270 screen, inside JES spool, or buried in a dataset and job chain that never appears in a normal editor. Hopper matters because it starts from that reality.

The trust question is the real one. Hopper only earns its keep in teams where mainframe friction is already expensive and the surrounding z/OS workflow matters as much as the code. If it cannot win trust on shop-specific quirks, IP boundaries, and operational safety, the narrowness of the category becomes the whole story.

What you can do with it

Use one workspace for the TN3270 terminal, datasets browser, jobs browser, and AI chat instead of bouncing between separate mainframe tools.

Let the agent read members, write JCL, submit jobs, inspect spool, decode VSAM records, and act in CICS from chat.

Approve every mutating action before Hopper writes a member, submits a job, or changes a resource.

Track JES jobs with return codes and spool counts in a live jobs panel, then attach a failing job straight into chat with @ references.

Download desktop builds for macOS, Windows, and Linux and connect to your own mainframe or request trial credentials.

Technical details

approval_model: Read-only actions run immediately, but writes, job submissions, CICS resource changes, and other mutating actions pause for approval with the exact action shown first.
shared_session_model: Hopper opens one mainframe session and exposes it through four connected panels, terminal, datasets, jobs, and AI chat, so the agent and the user are acting on the same live state instead of separate copies.
runtime_and_deployment: The agent runs client-side on the user's machine, installs nothing on z/OS, and the enterprise tier adds on-prem or VPC deployment plus org-wide privacy controls and no model training on customer data.
mainframe_protocol_boundary: TN3270 is required for the live session, while FTP is optional but needed for datasets, jobs, builds, and most agent tools, which means the product's useful surface area depends on real mainframe protocol access, not just source parsing.

Top Alternatives to Hopper

If Hopper is close but still misses the job, try one of these instead.

goose

Switch when you want a general open-source coding agent, not Hopper's mainframe-native terminal and JES context.

Biela.dev

Switch when the real need is repo automation, not a z/OS environment with TN3270 and spool flows.

Key Questions

Is Hopper replacing the terminal, or working through it?

It works through it. Hopper keeps a real TN3270 terminal in the product and shares that live session across the terminal, datasets, jobs, and AI panels.

What can the agent actually do on a mainframe?

It can read and write dataset members, submit JCL, read spool, drive the terminal, work with CICS, and query VSAM snapshots. Mutating actions still stop for approval before they run.

Can a team try Hopper before talking to sales?

Yes. The homepage shows a free Hobby plan with no credit card required, plus trial credentials for people who need mainframe access to test it.

What is the biggest adoption risk with Hopper?

Trust. Teams running critical mainframe systems will care more about safety, IP boundaries, and environment coverage than about demo quality.