DEV Community: 郭立 Guo Li

ChooseBrowser: every link on your Mac opens in the right browser and Chrome profile

郭立 Guo Li — Wed, 30 Sep 2026 02:18:51 +0000

You click a link in Slack or Mail and it opens in the wrong browser, signed in to the wrong Chrome account. Copy the URL, switch windows, paste, again.

ChooseBrowser makes that stop. Tell it where each site belongs, and every link lands in the right place from then on.

Try it free for 7 days · Mac App Store · Buy — US$4.99

What it does for you

Work and personal, kept apart: company GitLab, Jira and docs open in your work profile; personal GitHub and banking in another browser.
Test with many accounts without logging out: staging in the test account, the admin panel in the admin account, buyer and seller each in their own.
Down to the Chrome profile: every profile in Chrome, Edge, Brave and Vivaldi is its own target.
Even one site, split two ways: github.com/your-company in the work profile, the rest in your personal one.
One keystroke for everything else: links without a rule show a small chooser by the pointer; ⌘1–⌘9 picks, ⌘R saves the choice as a rule.
Learns as you go: remembers what you pick per site and puts it first.

Stays out of your way

It quits right after opening the link. Nothing running in the background.
No account, no analytics, no tracking. Rules live on your Mac, or sync through your own iCloud.
English, Chinese, Japanese and Korean.
macOS 26 or newer. A free Windows 10/11 preview is available too.

Price

US$4.99, one-time. No subscription.

Mac App Store: installs on every Mac with your Apple ID, updates automatically.
Buy direct: try it free for 7 days first; one licence activates up to 3 Macs.

The price of a coffee, for dozens fewer copy-pastes a day.

By Guo Li (郭立, leeguoo)

Pastyx: everything you've copied on your Mac, one keystroke away

郭立 Guo Li — Wed, 30 Sep 2026 02:16:08 +0000

You copy a snippet, then a link, and the snippet is gone. Your Mac's clipboard only remembers the last thing.

Pastyx remembers everything you copy. Press ⌘⇧V and your recent text, links, code and images line up; pick one and press Return to paste it into the app you're in.

Try it free for 7 days · Buy — US$9.99 · Product page

How it feels

⌘⇧V, then just type: find something you copied weeks ago with a few letters.
Return pastes, ⇧Return pastes as plain text with no stray formatting.
⌘1–⌘9 pastes one of your last nine clips.
Knows what you copied: links with their site icon, code detected automatically, colour values as swatches, and the app each clip came from.
Filter by type: Favorites, Text, Links, Code, Images — Tab to switch.
Favorites never expire: keep your signature, addresses and go-to commands one keystroke away.
Drag a clip straight into another app.

Safe by default

Passwords stay out: items password managers mark as concealed are skipped; Keychain, 1Password and Bitwarden are ignored; ignore any app you like, or pause capture from the menu bar.
Local-first: history lives on your Mac, kept for 30 days or forever, your choice. No account needed.
Sync only if you want: sign in to sync with the web app at paste.leeguoo.com and your other devices, or keep everything local.
Native and quick: a menu-bar app whose panel takes the keyboard without stealing focus or switching Spaces, so the paste lands where you were.

Requires macOS 26 or newer (Apple silicon or Intel).

Price

US$9.99, one-time. No subscription.

Try it free for 7 days, then buy if you like it. One licence activates up to 3 Macs.

Or install from the terminal:

curl -fsSL https://raw.githubusercontent.com/leeguooooo/pastyx/main/install.sh | sh

By Guo Li (郭立, leeguoo). Pastyx is an independent product, not affiliated with Paste (pasteapp).

Making Claude Code and Codex talk to each other — even across two computers

郭立 Guo Li — Tue, 29 Sep 2026 18:40:46 +0000

I usually have several AI coding sessions open at once: Claude Code writing a feature, Codex reviewing, Pi doing chores. Each is capable on its own. The problem is that they can't see each other. If I want Codex to look at the diff Claude just wrote, I copy it, switch windows, paste it, and carry the answer back. I had become the clipboard between two AIs.

Claude Code and Codex both ship native cross-session features, but each stops at its own product boundary. So I built ocs (Open Cross-session): a single binary that lets Claude Code, Codex, Pi and terminal agents message each other and wake each other up. No server, no account; everything lives in ~/.ocs.

What it looks like

Once installed, you can just tell any session "find another agent to review this" and it goes looking. By hand:

ocs who                                     # live sessions on this machine
ocs dm codex-01a06a98 "review this diff"    # message Codex and wake it
ocs rename reviewer                         # give this session a memorable name
ocs send dev "status? @reviewer"            # multi-party channel; @ wakes whoever you mention

The receiver doesn't just get a new line in a file. The message shows up in its conversation, with a ready-to-run reply command:

[ocs wake] claude-7043ea85 mentioned you in #dm-… (seq 7)

review this diff

Reply: ocs dm claude-7043ea85 "<your reply>"
Thread: ocs read dm-…

It replies, you get woken, and the two agents go back and forth while you watch with ocs watch.

0.6: across computers

The latest release extends this to the LAN. I have a Mac and a Windows PC at home; a Claude on the Mac can now hand "run the build on Windows" to the Claude or Codex on the PC:

# machine A                      # machine B
ocs lan up                       ocs lan up
ocs lan pair   # prints a code → ocs lan pair 7K2M-9QXD-…
                                 ocs dm claude-1a2b3c4d@mini "run the build on Windows"

Letting another machine type into your AI sessions needs a real threat model, so this assumes someone hostile is on the network:

Identity is a public key. Each machine has an Ed25519 key; IPs, hostnames and self-reported names are only hints.
Pair once, no trust-on-first-use. The pairing code carries a prefix of the issuer's key fingerprint, and the client verifies the server's key before sending its own identity or any request.
Mutual authentication and encryption. Signed X25519 handshake plus AES-256-GCM, with forward secrecy.
Unpaired machines can do nothing except redeem a valid pairing code, with frames capped at 1 KiB; a code burns after 5 wrong attempts.
Off by default. Nothing listens until ocs lan up. Remote senders always show up as name@<the label you gave that peer>, which the peer cannot change.

The hard part: "OK" doesn't mean delivered

In a messaging tool, the dangerous failures aren't errors. They're the ones that look like success while the message is gone. Several of ocs's hard rules come from those.

1. Claude answering ok doesn't mean the message reached the conversation. Injecting into a Claude Code session returns ok:true from the socket. But Claude's crossSessionInbound defaults to hold: the message waits for approval and is silently dropped after 5 minutes. ocs never treats that ok as delivered, and ocs doctor walks you through switching to accept.

2. codex queue writes to storage; it doesn't deliver. For terminal Codex the only official way in is codex queue, which appends to the thread store and returns success even if that session exited long ago. So ocs first proves the session is alive by finding a process holding its rollout file (lsof). Then it turned out that indexing tools hold those files too, so there's a second check: the holder, or one of its ancestors, has to actually be a codex process. Otherwise the message waits in the inbox.

3. Unknown outcome means never retry. Talking to ChatGPT Desktop goes through its private IPC. If a frame went out and no answer came back, the message may or may not have arrived. Retrying risks the other agent doing the work twice. ocs reports "unknown" as its own state (exit code 3) and never retries automatically.

4. One source of truth for sequence numbers. Every message gets a monotonically increasing seq. An early version kept the current seq in a separate file; a crash between "log written" and "seq file updated" produced a duplicate seq, and the reader's dedup permanently hid the later message. Now the seq is derived from the log itself under a lock, with a regression test pinning it.

None of these are hard in isolation. What makes them hard is that every one of them passes a normal test suite.

Install

# macOS / Linux
curl -fsSL https://raw.githubusercontent.com/leeguooooo/open-cross-session/main/install.sh | sh

# Windows (PowerShell)
irm https://raw.githubusercontent.com/leeguooooo/open-cross-session/main/install.ps1 | iex

The installer also adds the ocs skill to Claude Code, Codex and Pi; run ocs doctor --fix afterwards. macOS, Linux and Windows, MIT licensed.

If you outgrow one LAN — different networks, a team, several organizations — the same workflow carries over to Agent Party, hosted or self-hosted.

GitHub: leeguooooo/open-cross-session
Protocol and threat model: docs/lan.md

Issues and ideas welcome on GitHub.

By Guo Li (郭立, leeguoo), a full-stack engineer building tools that let AI agents do real work: chrome-use, iphone-use, mail-use and more.