# Getting code in and out

> Code moves through your own git remotes. The pad is a machine your repos pass through, not a place they are held.

Part of the reachpad docs: https://reachpad.dev/docs. Rendered page: https://reachpad.dev/docs/git.

## Your remotes, your flow

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

## 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](https://reachpad.dev/docs/terminal).