ASTROHACKER

Since Hard Refresh: Engine Pins, Shell Tips, and the Cloud Behind TermSurf

July 26, 2026 · Ryan X. Charles

You upgrade Astrohacker TermSurf, open a pane, click into the URL field, and the caret lands where you meant. The nav chrome does not flash a second color under the pointer. The shell under it is still ahsh, still Nu-powered, on a newer upstream tip. None of that is a reorg. It is the same product, a few days of pin and host work after the last feel-good Chromium week.

On July 22 we wrote about hard refresh, flick scroll, and video—the day-to-day wins after Chromium only—for now. That post closed around product line ~0.1.69–0.1.78. This one is what landed after that window: fresher engines and shell pins you can install, quieter browser chrome, and honest progress on the cloud app that will back the terminal—not a launch, not a soft-open tour.

The short version

Downloadable TermSurf family

  • Chromium product pin moved to Electron-stable chrome 150.0.7871.129.
  • Ghostty host advanced to current main, on Zig 0.16, with TermSurf IPC/runtime hardening so the host still talks cleanly to the engine.
  • ahweb — no hover paint on the nav strip; Control-mode URL click inserts at the cursor instead of only “jumping” the field.
  • ahsh — Nushell and Reedline re-pinned to upstream main (path coupled); product shell patches rebased (PATH union / lazy env surface kept).
  • Line — monorepo product crates moved through roughly 0.1.79–0.1.83. Upgrade the cask when your tap has the bits you care about.

Cloud webapp (in development)

  • Same company arc: on-device TermSurf, cloud backend for the terminal.
  • Already real in code and deploy path: account/settings, identity keys, password vault groundwork (including KDBX 4.x), shared UI, oRPC data plane, AWS deploy.
  • Not pretend-shipped: bookmarks sync, polished password sync product, wallet, AI agent management and marketplace. Those are the destination.

If you only remember one sentence: keep upgrading TermSurf from the tap; the engines and shell got newer under your feet, and the cloud layer is being built to meet the terminal—not replace it with a web demo.

What you can install today

Fresher Chromium

The shipped engine pin is no longer stuck on an older patch of the same Electron 43 line. Product Chromium sits on 150.0.7871.129 (Electron stable chrome for that cadence). Same family as the Chromium-only bet: one engine, security and media path we actually ship—not tip-of-tree archaeology.

Host and IPC (Ghostty / TermSurf)

The host terminal is not a frozen fork. Ghostty is on a current main tip with the product patch series rebased, toolchain at Zig 0.16. Follow-up work hardened TermSurf runtime details that only show up when the host and engine handshake—socket env for children, interrupt-safe I/O, Darwin sockaddr details. You should not need to care about those names; you should get a host that still starts panes after the pin jump.

ahweb chrome that stays out of the way

Two small Control-mode / browse-chrome changes:

  • No hover paint on the nav strip—less visual noise when the pointer crosses buttons.
  • URL click → insert at cursor when you are editing the bar, so a click behaves like an editor, not only like “select everything and hope.”

Shell on newer Nu

ahsh still means Astrohacker Shell: Nu under the product CLI, Reedline as the line editor, path-pinned forks. Both Nushell and Reedline moved to upstream main tips in one pass so the path deps stay coherent. Product behavior we care about (lazy traditional shell env, Nu-first PATH union so tools like cargo do not vanish) was rebased with the tip—not thrown out for a clean merge.

Version line

After the last post’s ~0.1.69–0.1.78 window, the monorepo product crates walked 0.1.79 through 0.1.83. Exact cask revision is whatever you installed last; the story is “several release bumps of host/engine/shell pins,” not one magic number that fixes everything.

Upgrade

Apple silicon, Homebrew:

brew tap astrohackerlabs/astrohacker
brew trust astrohackerlabs/astrohacker
brew update
brew upgrade --cask astrohacker

Install layout and names stay the same: Astrohacker TermSurf in Applications, ahterm / ahweb / ahsh (and friends) on PATH. Details: docs/homebrew when you need the full contract.

The cloud app—progress, not a product tour

TermSurf is the interface you run locally. The webapp is the cloud side of the same product: account, sync, keys, vault, and later wallet and AI agent management / marketplace. That is the plan. It is not “go open a secret URL and pretend the backend launched.”

What has been built hard enough to name without lying:

  • Account and settings — change password, delete account with real confirmation, session-aware shell chrome.
  • Identity keys — KeyPears-shaped list/detail, rotation and re-encrypt flows, hybrid post-quantum framing where the product already claims it.
  • Password vault foundation — lock/unlock, secret entries, authorization that does not trust the client on a good day; plus a real KDBX 4.x package path so import/export is not a toy JSON dump.
  • UI system — shared kit and dialog shell so modals are one product, not five slightly different blurs.
  • Data plane and ops — oRPC under /api, models that loaders can own, AWS deploy path, blog and app content that actually ships in the image.

What is not ready for “it works for everyone” language:

  • Bookmarks and password sync as a finished product surface
  • Cryptocurrency wallet as a shipping feature
  • AI agent management and an agent marketplace as public UX

Those are why the backend exists. They are not today’s install checklist.

When the cloud side is ready for you, we will say so in plain English—with a normal entry path, not a scavenger hunt.

Not this post

  • Not a Chromium tip-of-tree diary.
  • Not a soft-launch map of guest vs signed-in homes.
  • Not “AI marketplace available now.”
  • Not a promise that every experimental route is public product.

One more thing

Keep the cask current. The last post fixed feel on Chromium-only panes. This stretch fixed freshness of the stack under those panes—and put real mass behind the cloud backend that TermSurf will plug into.

If something still feels wrong after upgrade, say so. The point of shipping every few days is not the version number; it is whether the terminal still behaves like a tool you trust with an open day.

← Back to blog