Skip to main content
A launch link starts or continues work in r5d from anywhere you can put a link: an issue tracker, a pull request, a chat message or a script. The GitHub App and the Threadline plugin make these links for you. Opening it shows a dialog in your signed-in r5d, filled in from the link. Nothing starts, and no branch is created, until you confirm it. If you aren’t signed in, r5d asks you to sign in first and then shows the dialog. The link survives the sign-in and a reload of the page.

The dialog

The dialog is marked From a link and titled Check before starting. Everything in it can be changed before you choose Start session:
  • Work items: the issues, pull requests or other tracker items the link names, with links to them. A link can carry a snapshot of an item, such as an issue’s description and latest comments. View issue shows the snapshot and Copy issue copies it, so you can paste it into the first message if the agent should have it; for a pull request the buttons say View pull request and Copy pull request, and for other items View item and Copy item. Whoever made the link wrote the snapshot, so it may be outdated or wrong.
  • Project: your project whose remote is the link’s repository, however its URL is spelled. A renamed GitHub repository still matches. If you have no such project, the dialog offers to add the repository as a project, with a suggested name, or to use another of your projects.
  • Branch: a new branch, starting from an r5d branch or from a branch of the repository, or an existing r5d branch. A link only proposes a branch: choose an existing one, such as main, to work there instead. A new branch’s name has up to 45 characters: lowercase letters, digits and hyphens, in /-separated parts. The dialog says when it changed what the link asked for, and why: for example because a branch of that name already exists, or because the name is longer than 45 characters, in which case whole words are dropped from its end. A new branch created from a branch of the repository, such as a pull request’s, keeps that branch’s name whenever r5d can use it, so the session’s pushes go to the pull request. For a prompt-only link without a branch name or work items, the new branch is named after the first message’s opening words, like a new chat’s suggested branch, and follows the message as you edit it. Explicit branch names and issue/PR-derived names are preserved. Editing the branch settings stops automatic name updates.
  • Share: whether to share the session, its branch or its project read-only with one of your teams. A link can propose a team; the GitHub App proposes its team and all sessions on the branch. When the branch, or the whole project, is already shared with a team, the dialog doesn’t ask: it shows how the session will be shared and links to the team’s Members and shares page, where the share’s owner or a team admin can revoke it. A tracker shows a session’s status only while the session is shared with the tracker’s team, so the dialog says when the team a link asks for won’t see the session.
  • First message: the chat composer, prefilled with exactly the message the agent receives: the link’s prompt, or Implement <url> for an issue and Continue work on <url> for a pull request. Snapshots aren’t part of it unless you paste them in. Edit any part of the message. As in any chat, you can attach files and choose the model, its effort and the worker. Enter adds a line; Start session (or Ctrl/⌘+Enter) starts the session.
The model and the worker are the link’s, otherwise the project’s launch defaults, otherwise your last choice in this dialog. When none of your providers offers the link’s model, or the model doesn’t take the link’s effort, the dialog says so and starts from the next choice. A launch needs a connected worker: the composer offers only connected workers, and Start session stays disabled, saying why, while none of yours is connected. Your edits survive a reload of the page, like the link itself. Start session creates the new branch, if you chose one, and opens the new session once the branch exists. If the branch can’t be created, the dialog says why and you can choose another branch; when your synchronized workspace has no room for the branch’s files, for example, it says how many files or how much file content the workspace would hold, against its limits (200,000 files and 10 GiB, unless your plan gives more), and asks you to archive or delete branches or files you no longer need, after which Start session creates the branch. If the launch’s worker disconnected since you opened the dialog, the session says it waits for that worker and starts on its own as soon as the worker connects again. The session is named after the link’s work items; a launch without work items is named after the start of its first message. Either way, its agent can give it a name that says what the work is (chat names). If r5d couldn’t confirm the start, for example because the connection dropped, choose Start session again: it repeats the same launch, with the same session and uploads, and never starts a second session. Once a launch was sent, its project, branch, worker and share stay as they were; Start over discards it so you can change them. Cancel discards it too. A launch that was discarded, or never confirmed, leaves no branch behind. A launch whose first message already reached r5d starts even when its answer was lost, for example because r5d was switching to a new release: Cancel then opens its session instead of discarding it.

Launch defaults

A project’s settings have a Launch links section: the model and effort, and the worker, that the dialog preselects for that project when a link names none. Choose Your last choice to keep the dialog’s last choice, or A model to pick one. A launch model that none of your providers offers any more shows a warning there.

Work items on sessions

A session started from a link remembers its work items. The chat header (on phones, its menu) shows them as links to the tracker, for example acme/api#42, and the session lists show their short labels, for example #42; point at one to see its title. Sessions started from the former issue board have their issues as work items too. An agent can show the item it works on itself, for example after linking its session to an issue in your tracker:
These act on the session -s names, else on R5D_SESSION_ID, which in an agent’s shell is the agent’s own session. Adding a URL the session already has updates that item. The header and the session lists update at once, and teams the session is shared with see the change. The agent receives the first message exactly as you sent it. A snapshot reaches it only if you pasted it into the message. The simplest link uses readable query parameters:
To have a new branch named exactly as your link proposes, keep its name within r5d’s rule for new branches: up to 45 characters of lowercase letters, digits and hyphens, in /-separated parts, such as issue/42-fix-login. The dialog makes any other name fit, dropping whole words from the end of a longer one, and says so. A branch to work on (branch alone) can be any name r5d accepts for a branch: up to 150 characters of letters, digits, - and _, in /-separated parts that each start with a letter or digit. A link can also carry everything in its fragment, which your browser never sends to a server: https://r5d.dev/launch#<payload>. The payload is JSON, compressed with deflate (the zlib format) and base64url-encoded:
A work item is shown, wherever r5d shows it, from these fields alone: Without a label, r5d builds the item from its url and title, as for the url parameter: a GitHub issue or pull request is acme/api#42, #42 with its icon, any other URL its host and path with a link icon. Fields r5d doesn’t know are ignored. Up to 20 work items fit in one link. For example, in Node.js: