# Setting up codebases

Use fl0w as a coding agent that can work along all of your codebases — on your machine or on your [personal remote computer](/docs/overview#your-remote-agent-gets-its-own-computer). See the [Quickstart](/docs/quickstart#using-your-cloud-computer-workspace) for the remote filesystem and `@` file attachments in the [slash commands](/docs/slash-commands) reference.

## Cloning a repo via PAT

1. Open **Computer** > **Terminal** in the [fl0w remote](/remote) app (after the [Quickstart](/docs/quickstart#starting-fl0w-remotely) sign-up).

   <Image src="/docs/terminal.png" width={2062} height={1500}
     alt="Generating a workflow from a session with /generate"
     sizes="(max-width: 800px) 100vw, 640px"
     className="mt-4 h-auto w-full max-w-2xl rounded-lg border border-line/80" />

2. We recommend using a PAT (Personal Access Token) to clone your repo, make commits, and push with your own GitHub account

   * Go to [GitHub Settings](https://github.com/settings/profile/)
   * Create a PAT with the scopes you'd like your token/fl0w to have
   * Copy your PAT

3. Clone into the default working area, embedding your PAT in the remote URL:

   ```bash
   git clone https://<username>:<PAT>@github.com/your-org/your-repo.git
   ```

4. Fl0w can now work with version control in your codebase. For login-heavy Git hosting flows in the browser, combine this with [Browser use](/docs/guides/browser-use) or store a PAT via [`fl0w secrets`](/docs/cli#secrets) when appropriate.

Long-running coding tasks can be turned into [automated workflows](/docs/guides/automating-sessions) so they keep going with your laptop closed.