ASTROHACKER

Astrohacker 0.1.17: Real Browsers in Your Terminal

July 13, 2026 · Ryan X. Charles

You are mid-session on a MacBook Pro. Codex or Claude Code or Grok is grinding through a change in one pane. Another pane has the repo. A third has whatever you were editing before the agent rewrote it.

And the docs? The OAuth screen? The CI log that only renders as a web UI? Those are still in a separate browser, three spaces over, cookies mixed with your personal Gmail.

Astrohacker 0.1.17 puts real browser engines in panes next to that work.

Same window. Same flow. Chromium, WebKit, and Ladybird—each with isolated profiles—beside the shell and editor you already live in.

This post is for early adopters who already treat the terminal as home base: agentic builders on Apple silicon who run coding agents all day and are willing to try something rough if it kills the Cmd-Tab tax.

What 0.1.17 is

Astrohacker ships as one desktop install, not four consumer products.

You get:

  • Terminal — the host app. Ghostty-based. Panes, tabs, and configuration you expect from a serious terminal, plus browser panes in the same window.
  • Shell — included. Structured, Nushell-lineage tooling in a single binary.
  • Editor — included. Modal Helix-style editing with language tooling in-process.
  • Web — open a real engine in a pane from a shell command.
  • Engine helpers — Chromium, WebKit, Ladybird. You do not day-drive these; the product does.

Platform for this release: Apple silicon macOS. If you are not on that, this post is not your install path yet.

What is not in 0.1.17 as a shipped product surface:

  • Gecko / Firefox embedding (ah-geckod is research, not released)
  • Wallet
  • Mobile, web app, marketplace, or “Economy” start flows

0.1.17 is early. It is usable. It is not pretending to be polished forever software.

Why agentic builders care

Coding agents already made the terminal the control plane. The missing piece was the web surface that still owns half of software work.

With Astrohacker you can:

  • Keep the agent CLI, the repo, and the page you are verifying in one window
  • Use a work profile for GitHub / cloud consoles and a personal profile for everything else—without a second browser user ceremony
  • Open the same URL in Chromium, WebKit, or Ladybird when something smells engine-specific
  • Stay in flow when the agent says “check the docs” or “log into the dashboard”

Agents draft and edit. You still have to see the web. That loop should not require leaving the terminal.

Install with Homebrew

Apple silicon MacBook Pro. Homebrew. One cask.

brew tap astrohackerlabs/astrohacker
brew trust astrohackerlabs/astrohacker
brew install --cask astrohacker

Upgrade later:

brew update
brew upgrade --cask astrohacker

Smoke checks after install:

ahterm +version
ahsh --version
ahed --version
ahed --health rust

You should see 0.1.17 (or the version the cask currently points at after an upgrade). ahed --health rust should work without manually setting ASTROHACKER_EDITOR_RUNTIME.

What the install includes on PATH: ahterm, ahsh, ahed, ahweb, ahapp, plus engine helpers ah-chromiumd, ah-webkitd, and ah-ladybirdd. There is no meta ah dispatcher. Reserved for later: ahwallet.

Signing note (read this once): install uses ad-hoc codesign and clears quarantine. brew trust trusts the tap, not Apple notarization. Full Developer ID / notarized shipping is still ahead. That is honest early-adopter software, not a silent security claim.

First run can feel heavy. Engines are real engines. Warmup and disk use are part of the deal.

The workbench

Capability first. Identifiers second.

Terminal (ahterm)

Open Astrohacker Terminal. That is the app. ahterm is the launcher on PATH.

This is the host: multi-pane terminal work, plus browser panes that resize with the layout. Native terminal features come from the Ghostty lineage. Astrohacker adds the TermSurf protocol path, multi-engine profile servers, and the chrome that keeps browser and shell panes readable together.

Shell (ahsh)

ahsh is Astrohacker Shell—Shannon / Nushell family, packaged with Terminal. Tooling lives in the binary instead of starting life as a plugin zoo.

It is structured when you want structured pipelines. It also has a zsh alt mode when you need a familiar traditional subprocess without abandoning the shell you launched (macOS-default env via zsh, not bash).

Config follows Nushell habits (env.nu, config.nu under your Nushell config dir).

Editor (ahed)

ahed is a Helix-based modal editor. Vim-ish keys. Language tooling and syntax in-process. It ships with runtime assets so a normal Homebrew install does not require you to invent environment variables first.

Useful checks: ahed --version, ahed --health rust.

Web (ahweb)

This is the command you will actually type.

From a pane inside Astrohacker Terminal:

ahweb example.com
ahweb example.com --browser webkit
ahweb example.com --browser ladybird --profile work

ahweb draws the terminal chrome (URL bar, modes, status). The page itself is a real engine surface composited into the pane—not a toy HTML renderer.

Modes are intentionally modal: Control for terminal keybindings, Browse for keyboard/mouse into the page, Edit for the URL, Command for : commands. That is the same muscle memory most of us already have from editors and browsers that respect focus.

Engine selectors are family names: chromium, webkit, ladybird. Future gecko is not a product claim yet.

Apps (ahapp)

ahapp launches GTUI in-terminal apps when the Terminal pane environment is present. Same product install. Smaller surface area than ahweb for most people day one—know it exists when you need an app, not just a URL.

Engine helpers

ah-chromiumd, ah-webkitd, and ah-ladybirdd are profile servers and embed helpers. Prefer opening pages through Terminal / ahweb. Reach for the helpers only when you are debugging packaging or engine paths.

A multi-pane day

Here is the loop 0.1.17 is built for.

  1. Open Astrohacker Terminal.
  2. Pane A: your coding agent—Claude Code, Codex, Grok, OpenCode, Pi, whatever you actually use.
  3. Pane B: ahsh in the repo the agent is touching.
  4. Pane C: ahed on the file that just changed.
  5. Pane D: ahweb http://localhost:3000 (or the docs, or the provider dashboard) with --profile work if you want login isolation.

When the agent asks you to verify a UI, you do not leave. When the docs site and the app disagree, you split panes. When WebKit and Chromium disagree, you change --browser instead of installing a second browser lifestyle.

That is the product: agents, code, and real web in one window.

What 0.1.17 is not

Short list so we keep trust:

  • Not a promise that every site is perfect in every engine
  • Not Gecko parity
  • Not Wallet
  • Not a multi-SKU store of “Shell Inc.” and “Editor Inc.”
  • Not finished

It is a workbench release for people who install from a tap and send bug reports with stack traces.

What to do next

Install:

brew tap astrohackerlabs/astrohacker
brew trust astrohackerlabs/astrohacker
brew install --cask astrohacker

Then open Terminal, split a pane, and run:

ahweb example.com

Docs for components and engines live under astrohacker.com/docs—Terminal, Shell, Editor, Web, Chromium, WebKit, Ladybird.

If you are already living with coding agents on Apple silicon, this is the version to try: 0.1.17, one Homebrew cask, real browsers where your agents already are.

← Back to blog