# Zigzag, a native Mac browser for Arc refugees, built with Claude Code

> Zigzag is a free, open-source macOS browser that copies Arc's sidebar of tabs grouped into spaces, running on Apple's WebKit engine instead of Chromium.

- Project: Zigzag by ZigaoWang
- Kind: app
- Built with: Claude Code
- Noticed: 123 points on Hacker News (when we found it)
- Added: 2026-11-21T13:08:00+00:00
- Web page: https://ai-news.ikangai.com/built/zigzag/

Zigzag keeps Arc's sidebar, spaces, pinned tabs, and split view of up to four pages. It runs Chrome extensions installed from the Chrome Web Store. The app is written in Swift on WebKit, the engine macOS already ships. The README puts the installed size at about 35 MB, while the Hacker News post says around 18 MB. The author, a high school student in Shanghai, started the project after The Browser Company announced Arc would shut down. He says Arc's spaces, pins, and passwords can be imported.

The author writes that he built Zigzag with help from Claude Code. He first tried forking Helium, but that source was about 100 GB and builds took three to four hours on his Mac, so he switched to WebKit. The post says Claude writes most of the code while he decides what the app does, reviews quality and UI, and runs every change through his own daily browsing. The hardest part, he says, was Tampermonkey. WebKit has no userScripts API, so he built one on top of its content scripts. Where WebKit lacks Chrome APIs such as history or bookmarks, Zigzag answers the calls itself, but only for extensions that hold the matching permission.

By the author's own list, plenty is unfinished. There is no sync between Macs, no Easels or Notes, Boosts are limited to CSS, and there is no debugger API or chrome.identity. The full uBlock Origin does not run, though the lite version does. The post calls it a beta that has been his main browser for three weeks. It requires macOS 15.4 or later.

## In the author's words

> Honest up front: I built Zigzag with the help from Claude Code.

## What to take from it

Before forking a huge codebase, check whether a system component already provides the core engine. Zigzag dropped a Chromium fork that took hours to build in favor of WebKit, then wrote only the missing pieces itself, such as the userScripts layer.

## See it

- [Zigzag](https://github.com/ZigaoWang/zigzag)
- [Discussion on Hacker News](https://news.ycombinator.com/item?id=50496787)

---

AI wrote this entry from the project's own README or its author's post. That AI built the project is the author's statement, quoted here. Nobody at IKANGAI ran or tested it.
