Getting code in and out

Your remotes, your flow

The fastest path is the GitHub connection: press “Connect GitHub” on your dashboard and pick repositories on GitHub's own screen. New workspaces open with them already cloned and git ready to push, on tokens issued per session that expire within the hour.

Manual auth works the way it would on any new machine: gh auth login for GitHub, or a key you add to your provider, and it is set from then on. Either way you clone, branch, review and push exactly like you would locally, against the remotes you already use.

What persists between visits

• Files and working directories, including uncommitted edits an agent made while you were away.
• Git state: branches, stashes and remotes are where you left them.
• Your setup: dotfiles, shell history, and anything you installed.

There is no ssh into a pad

The browser terminal is the way in, from any device, with nothing to configure. Code leaves through git push; text leaves through select-to-copy in the terminal.