TermSurf 1.0 on January 1, With APIs for Agents and Playwright
Notes from the Austin JS talk, the status of Astrohacker TermSurf, and the two developer APIs that the audience asked for: browser control for SI agents and a Playwright-compatible API. Both are now in the plan for 1.0 on January 1, 2027.
Last night I gave a talk called “Run Webapps in Your Terminal” at the Austin JS meetup, hosted at Cloudflare. The slides are at termsurf.com/talks/2026-10-20-austin-js, and every slide has its own URL.
The talk was about Astrohacker TermSurf. The best part was the questions afterward. Two of them changed the plan for 1.0, so this post is mostly about them.
The Talk in Two Minutes
TermSurf is a terminal with real browser panes. A pane can hold a shell or a Chromium page. You open a website the same way you open any other terminal app: type a command. No Cmd+Tab to a separate browser window.
I started with demos: Roamari (the browser),
ahcalc (a calculator) and TermPlot (Plotly charts
in a pane). Then I showed two browser profiles in one window at the same
time. Alice sends EarthBucks to Bob in the same webapp, side by side, with no
logout. That works because the browser runs in a separate process from the
terminal.
Then a short history: from the Teletype, to the CRT, to the GUI, to the GPU. The terminal survived all of it, and in 2025 the most powerful app of the year, Claude Code, launched in one. Developers still need the shell. What the shell is missing is graphics.
TermSurf is a protocol, not only an app. A TermSurf app connects to a Unix
socket, sends length-prefixed protobuf messages, and asks the host to put a
web page over its pane. Roamari is a Rust program that speaks the protocol.
ahcalc is TypeScript compiled into a binary with Bun. Any language can do
it. The protocol docs have the details.
Then the build story. I tried this on WezTerm in 2024 and gave up. I started again on January 1, 2026, with Claude Code. Since then TermSurf has run on WKWebView, CEF, and an in-process Chromium fork, and each one failed for a different reason. The current design is a fork of Ghostty, a fork of Chromium, and NuTorch (our Nushell fork), as separate processes on one protocol. I wrote the long version in What It Took to Build TermSurf. The whole talk, slide by slide, is in Run Webapps in Your Terminal.
Status: 1.0 on January 1, 2027
TermSurf is pre-1.0 today. You can install it with Homebrew and use it every day; I do. But the protocol can still change, and there are no published app libraries yet.
The target for TermSurf 1.0 is January 1, 2027. The plan for 1.0 before last night was:
- A stable protocol, with a spec.
- TermSurf libraries for Rust and TypeScript.
- Reliable CI tests.
- Full Chromium API support, for example notifications.
Last night added two items to that list.
DevTools: Already Done
The first question was about DevTools. Web developers live in DevTools, and a browser for developers without them is not a browser for developers.
TermSurf already has them. In a Roamari pane, press Esc, then type :devtools (or :dev) and press Enter.
Chromium DevTools opens in a new pane to the right, connected to the page you
are looking at. Add a direction to put it somewhere else: :devtools down,
:devtools left or :devtools up. It is the real Chromium DevTools, so the
elements panel, console, network tab and debugger are all the ones you know.
So the inspect half of the story works now. The discussion was about the other half: control.
API 1: Let Your Agent Drive the Browser
Most developers in that room build with an SI agent in a terminal: Claude Code, Codex, or another one. The agent writes the code. Then it has a problem. It cannot see the result. It cannot open the page, click the button, read the console error or take a screenshot. So you do it for it, and you paste what you saw back into the terminal.
That is backward. The agent and the browser are already in the same window. The agent should be able to use the browser.
TermSurf 1.0 will have an API for this. An agent such as Claude or Codex will be able to:
- Open a URL in a TermSurf browser pane.
- Take a screenshot of the page.
- Read the page, click, and type.
- Read console messages and errors.
The shape of the API is not final. The likely form is MCP tools, because that is what agents already speak. We are also looking at WebMCP, a proposed web standard from the W3C Web Machine Learning Community Group. In WebMCP, a web page exposes its own tools to the agent, instead of making the agent guess at buttons in a screenshot. Chrome has an early preview. We will support WebMCP or something like it. In both cases, the browser the agent controls is the pane next to it, which you can also see and use.
API 2: Playwright in the Pane
The second request came from anyone who has run end-to-end tests. When you run Playwright tests in headed mode, Playwright opens a new browser window. It takes your focus, it sits on top of your terminal, and it goes away when the test finishes. You run the tests in the terminal, but you watch them somewhere else.
TermSurf 1.0 will have a Playwright-compatible API. When you run Playwright
tests in a TermSurf terminal, the browser opens in the pane, next to the
test output, not in a separate window. You watch the test click through your
app in the same place you started it. When it fails, the page is still there,
and :devtools is one command away.
TermSurf already runs Chromium, and Playwright can already connect to Chromium through the Chrome DevTools Protocol. That gives us a good starting point. The goal is that an existing Playwright test runs in a pane with no change to the test.
Playwright compatibility was on the slides as a 2.0 item. After last night, it moved to 1.0. Both APIs are planned work, not shipped features. They are part of the 1.0 release on January 1, 2027.
The 1.0 List Now
- A stable protocol, with a spec.
- TermSurf libraries for Rust and TypeScript.
- Reliable CI tests.
- Full Chromium API support.
- A browser-control API for SI agents (MCP, and WebMCP or something like it).
- A Playwright-compatible API that runs tests in the pane.
Later, for 2.0: WebKit, Ladybird and Gecko engines, a community hub for TermSurf apps, a password manager and a bookmarks manager.
Try It
Thank you to Austin JS and to Cloudflare for hosting. If you were there and you have another API request, tell me at @AstrohackerLabs.
On an Apple-silicon Mac with macOS 26 or newer:
brew trust astrohackerlabs/astrohacker
brew tap astrohackerlabs/astrohacker
brew install --cask termsurf
Then open a page with roamari termsurf.com. Then press Esc and type :devtools.
More at termsurf.com and in the
docs.