deep links

overview

atlas registers the atlas:// url scheme on your system. clicking an atlas link — in slack, a jira ticket, a browser, or anywhere else — opens atlas and performs the requested action. links work whether atlas is already running or not.

link types

add a repository

clone and add a repository to atlas.

atlas://add-repo?url=https://github.com/org/repo

parameter	required	description
`url`	yes	git repository url (https or ssh)

create a workspace

create a new workspace from a branch or pull request.

atlas://create-workspace?repo=my-app&branch=feature/login
atlas://create-workspace?repo=my-app&pr=42
atlas://create-workspace?github=org/repo/pull/123

parameter	required	description
`repo`	one of `repo` or `github`	repository name as it appears in atlas
`github`	one of `repo` or `github`	github pr path in `org/repo/pull/NUMBER` format
`branch`	no	branch name to create the workspace from
`pr`	no	pull request number
`mode`	no	workspace mode: `standard` (default), `quick`, or `browse`

the share button in the workspace header generates atlas links you can copy to your clipboard.

branch link — creates a create-workspace link with the current repo and branch
pr link — if the workspace has a pull request, creates a link with the github pr path

teammates who click the link will get a confirmation prompt before atlas creates anything.

cold launch

links work even when atlas isn’t running. the os launches atlas, and the app picks up the pending link once it’s ready. there’s a brief delay while the app starts up, but the link is never lost.

security

atlas validates every deep link before acting on it:

a confirmation dialog shows exactly what the link will do — you must approve before anything happens
git urls must use https or ssh (no file:// or path traversal)
parameter values are capped at 2048 characters
pr paths must match the expected org/repo/pull/NUMBER format
invalid or malformed links are rejected with a logged error