Skip to main content

Links Launcher

The links launcher on the toolbar: links saved with a project or declared in its manifests, your own links, the active worktree's pull request, failing checks and deployments, and every dev server Daintree is running. Saved links to local addresses open in a panel; the rest open in your system browser.

Reviewed

Overview

The links launcher is the Links button, on the right side of the toolbar by default. It opens one list of the addresses that belong to the work in front of you: this project's saved links, the links its manifests declare, your own links, the active worktree's pull request with any failing or running checks, where that worktree is deployed, and every dev server Daintree is running.

Nothing in the launcher is a browser. A saved or declared link to a local address opens in a panel of the active worktree, and anything else opens in your system browser. See Where a link opens.

Note
The launcher replaced the Portal dock. Custom links you kept in the Portal are moved to Your links when you upgrade, and the Portal's dev servers list is now the launcher's Dev servers section. The built-in web chat entries were not carried over, and Daintree clears the Portal's stored sign-ins in the background when it starts after the upgrade.

Opening the launcher

Click Links in the toolbar. The button only appears while the launcher has something to show: a link of any kind, a pull request on the active worktree, or a dev server that is starting, installing, running, stopping or has failed. Deployments and a stopped server on their own don't bring the button back, even though the launcher would list them; open it from the command palette to see them.

The command palette (Shift-Command-P Control-Shift-P Control-Shift-P ) has Open links, which opens the launcher even while the button is hidden. It then opens from the right end of the toolbar. There is no default shortcut; bind links.open in Keyboard Shortcuts if you want one.

On a narrow window the button can move into its group's … overflow menu like other optional buttons. The menu then lists the launcher's links and the pull request as its own rows. The checks and the dev servers each get a single row, Checks… and Dev servers…, that opens the full launcher, which is also the only place deployments are listed. Right-click the button for Customize toolbar… and Unpin from toolbar. See Overflow.

Each opening rereads the project's links and asks the forge for the pull request's checks and the worktree's deployments. They are read again only when what they belong to changes, so reopen the launcher to refresh them. Nothing polls the forge for them while the launcher is closed.

With nothing to show, the launcher reads "Links you or the Assistant save for this project, links declared in its manifests, and dev servers running in any worktree show here." Its Add a project link button opens the project's link settings.

What it lists

Sections appear in this order, and a section with nothing in it is left out.

Links saved with this project and offered only with it, such as its staging site, its production dashboard or its CI page. They live in the project's local settings in Daintree's data folder on the machine that holds the project, never in the repository, so cloning a repository cannot add any. A project holds up to 50.

You add them in project settings. The project's Daintree Assistant can add them too, and a link it added carries an Assistant badge until someone edits it by hand. See Agent and MCP control.

Daintree reads four manifests at the project's root and lists the web addresses they name, one section per file, headed From package.json, From pyproject.toml, From Cargo.toml and From catalog-info.yaml.

FileRead fromRow names
package.jsonhomepage, repository and bugs, the last two as a string or an object with a urlHomepage, Repository, Issues
pyproject.tomlThe [project.urls] tableEach entry's label, or the address's host when the label is blank
Cargo.tomlhomepage, documentation and repository, including values a package inherits with field.workspace = true, or [workspace.package] in a virtual workspace's rootHomepage, Documentation, Repository
catalog-info.yamlmetadata.links of every entity in a Backstage catalog fileEach link's title, or its host

Only http and https addresses count, so npm's owner/repo shorthand and an ssh clone address are skipped. A clone address such as git+https://github.com/acme/app.git is shown as the repository's page, https://github.com/acme/app, and any username or password in an address is dropped. An address an earlier file already listed is not repeated, and each file adds at most 20 links.

These links are read from the files each time and never saved, so you can't edit or remove them in Daintree: change the file instead. The launcher follows edits to the files while the window is visible. A manifest larger than 512 KiB is ignored, as is a manifest that is a symbolic link to a file outside the project folder. For a project on a remote host, the files are read on the host.

Your own links, offered in every project on this machine, in the order you set. Only the ones switched on appear. Manage them in Settings > Links.

Pull request and checks

When the active worktree has a pull request, the launcher shows it under a heading named the way your forge names it (Pull request, or Merge request on GitLab) with the worktree's branch, or its name, beside it. The row shows the title, the reference and state, such as PR #42 · Open, and opens the pull request's page.

Under it are the checks that failed, timed out or are still running and have a page to open, in the same order as Review Hub. Other checks, passing, skipped or queued, are left to Review Hub. If the checks can't be read, the section says Couldn't load checks.

Only a pull request reported by the project's current code forge appears, and only while the worktree still has a remote. If the forge reports that the pull request no longer exists, the section goes away.

Deployments

A Deployments section, with the worktree's branch beside it, lists each environment the forge reports for the worktree's pull request, or for its branch when there is no pull request. Each environment gets one row from its newest deployment: its name, its state (Pending, Deploying, Deployed, Failed, Inactive or Unknown state) and the host of its address. A row with an address always opens it in your system browser; a deployment that reported no address shows its state only.

Of the built-in forges, GitHub reports deployments. A forge that doesn't report them shows no section, the same as a branch with nothing deployed. If the read fails, the section says Couldn't load deployments.

Dev servers

The Dev servers section lists every dev-server session Daintree is running on the machine this window works on, across worktrees and across projects, not just the one in front of you. Its heading counts the running and failed ones, for example 2 running · 1 failed.

Each row is one Dev Preview panel, named after its worktree, or after its project or scratch workspace when it has none. Two rows with the same name are told apart as panel 1 and panel 2. A running server shows its address, such as localhost:5824. A server still coming up shows its latest output line, and a failed one shows its error. For a running server, the latest output line is in the status's tooltip.

  • Click a running server to bring its own Dev Preview panel forward, when this window can show that panel. Otherwise, a server in another project for example, its address opens in your system browser.
  • Open in external browser opens a running server's address in your system browser.
  • Restart restarts the server, and Stop stops it. A stop from here sticks like any other: the preview stays stopped until you start it again. See Stops that stick.
  • A failed server can be stopped too, which is how you clear it. When no process is left behind it, the button reads Dismiss error.

Stopped sessions are hidden, with one exception: a session restored from the last time Daintree closed stays listed as Stopped with a Start button, because that row is the offer to start it again. If the list can't be read, the section says Couldn't load dev servers.

In a window on a remote host, dev servers run on the host, and Daintree forwards their ports to this machine as you need them. See Dev Servers and localhost.

Click a row and the launcher closes and opens its address:

  • A local address, meaning http or https on localhost, 127.0.0.1, ::1 or 0.0.0.0 (read as localhost), opens in a panel of the active worktree. That is the worktree's Dev Preview already serving that address if there is one, otherwise the Browser panel you used most recently in the worktree, otherwise a new Browser panel. A panel that is in the trash or shown as a dialog is skipped.
  • Any other address opens in your system browser with its path and query as saved, rather than through a panel's address rules.

Only http and https addresses open. Anything else is refused with a Couldn't open link notice.

In the full launcher, right-click any row that has an address for Open in external browser and Copy URL. Open in external browser sends even a local address to your system browser, which is the way to try a local server in a real browser.

In a window on a remote host, localhost means the host. A local address keeps its address and Daintree forwards the port to this machine, and an outside address whose sign-in returns to the host's localhost gets that port forwarded before it opens. A panel and a sign-in callback keep the host's port number, so that port has to be free on this machine; Daintree says so when it isn't.

Open Settings > Links. The Your links section lists your links with the ones that are switched off still in place.

  • Add a link takes a name and an http:// or https:// address, then Add.
  • Edit opens the name and address in place, with Save and Cancel.
  • With two or more links, Move up and Move down set the order the launcher shows.
  • The switch hides a link from the launcher without removing it.
  • Remove removes it at once, with Undo in the confirmation that follows.

Your links belong to this machine and are shared by every project and window on it.

Open Settings > Project > General and find Project links, or press Add a project link in an empty launcher. Add a link with a name, such as Staging, and its address; each saved link has Edit and Remove. An address can't carry a username or password, because the settings file is plain text. A link's name can be up to 80 characters.

See Project settings.

Agent and MCP control

A project's own Daintree Assistant keeps that project's links with four tools on its default Core tool set: project.links.list, project.links.add, project.links.update and project.links.remove. Ask it to save your staging address, for example, and the link appears in the launcher with the Assistant badge.

  • The Assistant may add an https:// address anywhere, and an http:// address only for localhost or 127.0.0.1.
  • Adding a link opens nothing. Daintree shows Assistant added a project link with an Undo.
  • The Assistant can change or remove only a link it added that nobody has edited since. Editing a link by hand makes it yours.

The global Assistant, other agents, plugins and external MCP clients can't change a project's links. Open links (links.open) is not offered over MCP: it opens a popover in your window, and the link tools already cover the list itself. See MCP Server.