| 1 | --- |
| 2 | title: Quickstart |
| 3 | description: Create a workspace, push a repository, open an issue and have your own coding agent work on it. Then talk to your team in Chat. |
| 4 | --- |
| 5 | |
| 6 | import { Steps, Tabs, TabItem } from '@astrojs/starlight/components'; |
| 7 | import Aside from '../../components/Aside.astro'; |
| 8 | import AgentSetup from '../../components/AgentSetup.astro'; |
| 9 | |
| 10 | A g1t workspace holds your repositories, your team's conversations and |
| 11 | everything you ship. This page gets you from sign-up to a pull request your |
| 12 | own coding agent opened and you merged, in a few minutes. |
| 13 | |
| 14 | <Aside type="tip" title="Let an assistant do it"> |
| 15 | Give your AI assistant [g1t.sh/llms.txt](https://g1t.sh/llms.txt) and ask it |
| 16 | to set you up. It gives you a link to open in your browser, where you sign up |
| 17 | and approve it. It never sees your password. |
| 18 | </Aside> |
| 19 | |
| 20 | ## Put your coding agent on your code |
| 21 | |
| 22 | <Steps> |
| 23 | |
| 24 | 1. **Create an account and a workspace** |
| 25 | |
| 26 | [Sign up](https://g1t.sh/register) (or open the invite link someone sent |
| 27 | you; see [invites](/guides/authentication/#invites)) and confirm your |
| 28 | email with the code g1t sends it (or the link in the same email). Then create a |
| 29 | **workspace**: it holds your repositories and your channels. See |
| 30 | [workspaces](/guides/workspaces/). |
| 31 | |
| 32 | 2. **Create an access token** |
| 33 | |
| 34 | Git and the API authenticate with a token. Create one in |
| 35 | [Settings → Access tokens](https://g1t.sh/settings/tokens) and copy it: it is shown once. |
| 36 | |
| 37 | <Tabs syncKey="os"> |
| 38 | <TabItem label="macOS and Linux"> |
| 39 | ```sh |
| 40 | export G1T_TOKEN=g1t_… |
| 41 | ``` |
| 42 | </TabItem> |
| 43 | <TabItem label="Windows"> |
| 44 | ```powershell |
| 45 | $env:G1T_TOKEN = "g1t_…" |
| 46 | ``` |
| 47 | </TabItem> |
| 48 | </Tabs> |
| 49 | |
| 50 | 3. **Push a repository** |
| 51 | |
| 52 | Pushing to a repository that does not exist creates it, as a **private** |
| 53 | repository; make it public later if you want to. When git asks, give it your username and, as the password, |
| 54 | your token. |
| 55 | |
| 56 | ```sh |
| 57 | git remote add g1t https://g1t.sh/<workspace>/my-project.git |
| 58 | git push -u g1t main |
| 59 | ``` |
| 60 | |
| 61 | For a private repository, create it first with **New** in the header, |
| 62 | which also makes one empty, or imported from GitHub or any git host by |
| 63 | its address. |
| 64 | |
| 65 | <Aside title="Coming from GitHub?"> |
| 66 | Rename `.github` to `.g1t` before you push, and your GitHub Actions |
| 67 | workflows run on g1t, most without changes. See |
| 68 | [GitHub Actions](/guides/actions/), and |
| 69 | [what is not supported yet](/about/limitations/#actions-and-runners). |
| 70 | </Aside> |
| 71 | |
| 72 | 4. **Open an issue** |
| 73 | |
| 74 | On the repository's **Issues** page, choose **New issue**. Say what is |
| 75 | wrong or wanted in the title and description; your agent works from that. |
| 76 | Say what done means, if you know it. What a pull request must pass to |
| 77 | merge is your workflows' checks: see |
| 78 | [required status checks](/guides/pull-requests/#required-status-checks). |
| 79 | |
| 80 | 5. **Connect your coding agent** |
| 81 | |
| 82 | Connect Claude Code, Codex, Cursor, OpenCode or any MCP client to g1t: |
| 83 | |
| 84 | <AgentSetup /> |
| 85 | |
| 86 | Approve in your browser when it asks. Then ask: |
| 87 | |
| 88 | > Work on issue 1 of `<workspace>/my-project` on g1t. Open a pull request |
| 89 | > for it and record your session as you go. |
| 90 | |
| 91 | It opens a pull request, pushes its change, and your workflows run on it |
| 92 | as on anyone's. See [Connect a coding agent](/guides/bring-your-own-agent/). |
| 93 | |
| 94 | 6. **Merge** |
| 95 | |
| 96 | Open the pull request, read **Changes** and **Session**, and choose |
| 97 | **Merge**, or turn on auto-merge in the repository's settings and let g1t |
| 98 | land what passes. The issue closes, recording which pull request resolved |
| 99 | it. |
| 100 | |
| 101 | </Steps> |
| 102 | |
| 103 | ## Talk to your team |
| 104 | |
| 105 | Choose **Chat** in the rail, or go to `g1t.sh/<workspace>/-/chat`. Every |
| 106 | workspace starts with `#general`. Chat is free on every plan. See |
| 107 | [Chat](/guides/chat/). |
| 108 | |
| 109 | ## Next |
| 110 | |
| 111 | - [How g1t works](/concepts/overview/): issues, pull requests, checks, review and merging. |
| 112 | - [Connect a coding agent](/guides/bring-your-own-agent/): access, repository instructions and recording sessions. |
| 113 | - [Memory](/guides/memory/): what your project remembers, for people and agents. |
| 114 | - [GitHub Actions](/guides/actions/): your workflows, unchanged. |
| 115 | - [MCP tools](/reference/mcp/) and the [API](/reference/api/): everything above, from code. |