Most people don't run one browser anymore. They run several, split across profiles. Safari for personal, Chrome for work, a separate Chrome profile for development, maybe Firefox for testing. Each profile is its own world of logins, history, and extensions.

macOS never got the memo. Click a link in Mail, Slack, or Terminal and it opens in one fixed default browser, usually the wrong one. So you copy the URL, switch browsers, find the right profile, and paste. All day. Burly exists to delete that little tax.

When Burly is your default link handler, every external link pauses for a fraction of a second to ask one question: where does this belong? A compact, keyboard-first picker lists your browser profiles as the destinations, not just browsers, so the link lands in exactly the right context.

CodeHerald provides a new way to keep track of your code review queue, grouped by your next action needed.

When would you use CodeHerald?

• You work in a team that does code reviews.
• Your team receives ad-hoc code review requests via multiple channels: DMs, emails, bookmarks of filtered lists.
• Your team sometimes loses track of small pull requests, delaying them days.
• Your team find ad-hoc code review requests distracting, but cannot put a finger on why.
• Your team tried different strategies to improve code review process, and none of them felt right.

If any of the above is true, CodeHerald will help you.

What can CodeHerald do for you?

CodeHerald groups pull requests by next action: must review, needs an update, can be merged. It allows you to replace slack, emails, filters, and browser bookmarks with one single page that you can open at a glance and decide which PR to tackle next.