The runbook link matters most at 3am, which is when nobody can find it

3am is a bad time to search Slack

The alert fires. You need four things: the dashboard that shows the failing metric, the runbook for this service, the deploy pipeline so you can see what shipped, and the status page you are about to update. The runbook link was posted in a thread eight months ago by someone who has since changed teams. The dashboard is bookmarked - on your old laptop.

Nothing about this is exotic. Every service has a handful of URLs that are obvious to whoever built it and invisible to everyone else: the repo, the CI pipeline, the Grafana or Datadog board, two staging environments, the API reference, the on-call rota, the runbook. They accumulate in individual browsers, which are the least shareable and least durable storage a team owns.

A wiki tells you why; a link board makes the five things you need under pressure reachable without reading anything.

One board per service

Give each service or project a board named after it, with fixed categories: Code, Deploy, Observe, Environments, Docs, Ops. It takes ten minutes per service and it stays useful because the shape never changes - on a service you have never touched, you already know where its staging URL is.

For the links that must exist everywhere - the incident channel, the status page, the on-call rota, the escalation runbook - an admin can mark that board required. It appears for everyone in the group and cannot be removed, so nobody joins the rotation without it and nobody accidentally cleans it out of their bookmarks bar.

Find it without leaving the browser

The extension puts search over your boards one shortcut away, and it can make your boards the new-tab page - rendered from a local cache, so it is up before the network is. Saving works the same way it should: a keyboard shortcut, the right-click menu, or the popup. Optional star capture means pressing the browser's own bookmark star files the page onto a private Unsorted board instead of into a folder you will never open.

In practice this changes the incident question from who knows the runbook URL to typing runbook in a new tab.

New laptop, same browser state

Sessions save every open tab and window as a named set, and a saved window reopens as one browser window rather than a pile of loose tabs - useful when a debugging setup is nine tabs in a specific arrangement. Opt-in whole-browser snapshots go further: they enable crash restore and new-machine restore, window positions included. Machine swap day stops being a half-day of rebuilding context.

Bookmarks that only exist in one Chrome profile also survive better once they live on a board. See sync bookmarks across browsers if you work across Chrome, Edge and Firefox on different machines.

No lock-in, and the honest limits

Export produces a standard bookmarks HTML file, any time, on every plan including the free one - the same format every browser reads. Import goes the other way from a browser HTML file or a Toby, Raindrop or Pocket export.

The limits are real. There is no Safari extension and no mobile app; the extension covers Chrome, Edge, Firefox and Opera. There are no integrations - no Slack, no PagerDuty, no SSO. Linksley does not run your service catalog: if you already have Backstage and people actually use it, keep it and treat boards as the personal and small-team layer above it. And if you are a solo developer with fifty bookmarks that you can find, a folder in Chrome is fine.