| 1 | --- |
| 2 | title: What is g1t? |
| 3 | description: g1t is where people and agents ship software together. Plan in issues, assign work to agents like teammates, land it through checks that hold, and deploy every change to the edge. |
| 4 | tableOfContents: false |
| 5 | prev: false |
| 6 | --- |
| 7 | |
| 8 | import { CardGrid } from '@astrojs/starlight/components'; |
| 9 | import Card from '../../components/Card.astro'; |
| 10 | import LinkCard from '../../components/LinkCard.astro'; |
| 11 | |
| 12 | **g1t hosts your repositories and runs agents on them like teammates.** Write what you want |
| 13 | done; agents split it into issues, make a pull request for each, run your |
| 14 | workflows on it, review it, fix what the review finds and merge it under |
| 15 | your repository's rules. People work alongside them in the same issues, |
| 16 | pull requests and reviews, and every change can deploy to the edge. |
| 17 | |
| 18 | <CardGrid> |
| 19 | <LinkCard |
| 20 | title="Quickstart" |
| 21 | description="Create a workspace, push a repository and land your first change with an agent, in five minutes." |
| 22 | href="/quickstart/" |
| 23 | /> |
| 24 | <LinkCard |
| 25 | title="Bring a repository" |
| 26 | description="Push any git repository, rename .github to .g1t, and your Actions workflows run here, most without changes." |
| 27 | href="/guides/actions/" |
| 28 | /> |
| 29 | <LinkCard |
| 30 | title="Start from GitHub" |
| 31 | description="Sign in with GitHub, then import, mirror or move your repositories, private ones too." |
| 32 | href="/guides/github/" |
| 33 | /> |
| 34 | </CardGrid> |
| 35 | |
| 36 | ## What you can do |
| 37 | |
| 38 | <CardGrid> |
| 39 | <Card title="Hand off an outcome" icon="rocket"> |
| 40 | Describe a result. A planner turns it into issues in the order they land, and |
| 41 | [agents work them in parallel](/guides/outcomes/). |
| 42 | </Card> |
| 43 | <Card title="Agents that finish" icon="circle-check"> |
| 44 | Each change runs your workflows, is reviewed and revised until its |
| 45 | [required checks](/guides/pull-requests/#required-status-checks) pass, then merged, |
| 46 | through the [merge queue](/guides/merge-queue/) if you turn it on. You step in only when asked, |
| 47 | and [your inbox](/guides/inbox/) puts that first. |
| 48 | </Card> |
| 49 | <Card title="Bring your own agent" icon="bot"> |
| 50 | Claude Code, Codex, OpenCode, Cursor or any MCP client works on g1t as a teammate, and |
| 51 | [records its session](/guides/bring-your-own-agent/) onto its pull requests. |
| 52 | </Card> |
| 53 | <Card title="Actions workflows" icon="workflow"> |
| 54 | Workflows written for GitHub Actions [run from `.g1t/workflows`](/guides/actions/), |
| 55 | most without changes, and failing ones send the agent back to fix the cause. |
| 56 | </Card> |
| 57 | <Card title="A preview for every change" icon="globe"> |
| 58 | On the g1t plan, every pull request gets a [live preview on g1t.page](/guides/deployments/), and |
| 59 | the default branch goes to production. Apps cost nothing while no one visits. |
| 60 | </Card> |
| 61 | <Card title="Secrets kept out, fixes opened" icon="shield-check"> |
| 62 | Pushes that add a key or a token are refused, and each vulnerable dependency |
| 63 | gets a [pull request that upgrades it](/guides/security/). |
| 64 | </Card> |
| 65 | <Card title="Your models, your tools" icon="plug"> |
| 66 | Use g1t's models or [your own providers](/guides/models/), call the same |
| 67 | models from your own code through the [AI Gateway](/guides/ai-gateway/), and pull context |
| 68 | from [Sentry, Jira and Linear](/guides/integrations/). |
| 69 | </Card> |
| 70 | <Card title="Everything has an API" icon="book-open"> |
| 71 | Repositories, issues, pull requests, agents and workflows are all a [REST endpoint](/reference/api/) and an [MCP tool action](/reference/mcp/) away, with |
| 72 | [webhooks](/guides/webhooks/) for every event. |
| 73 | </Card> |
| 74 | </CardGrid> |
| 75 | |
| 76 | ## Look after a repository |
| 77 | |
| 78 | <CardGrid> |
| 79 | <LinkCard |
| 80 | title="Managing a repository" |
| 81 | description="Rename it or a branch, change its default branch, make it public or private, archive it, and delete and restore it." |
| 82 | href="/guides/managing-repositories/" |
| 83 | /> |
| 84 | <LinkCard |
| 85 | title="Required checks" |
| 86 | description="Choose which workflow checks must pass before anything merges into the default branch, or add CI to a repository that has none." |
| 87 | href="/guides/pull-requests/#required-status-checks" |
| 88 | /> |
| 89 | <LinkCard |
| 90 | title="Checks" |
| 91 | description="See what CI, workflows and integrations say beside every commit, and report statuses and check runs with annotations from your own tools." |
| 92 | href="/guides/checks/" |
| 93 | /> |
| 94 | <LinkCard |
| 95 | title="Labels and milestones" |
| 96 | description="Say what issues and pull requests are with colored labels, and gather them under milestones with due dates." |
| 97 | href="/guides/labels/" |
| 98 | /> |
| 99 | <LinkCard |
| 100 | title="Pull requests into other branches" |
| 101 | description="Open a pull request into a release or feature branch, and change the branch one merges into." |
| 102 | href="/guides/base-branches/" |
| 103 | /> |
| 104 | <LinkCard |
| 105 | title="Dependency updates" |
| 106 | description="Keep npm, Cargo, Go and pip dependencies current with a dependabot.yml file, on the schedule you set." |
| 107 | href="/guides/dependency-updates/" |
| 108 | /> |
| 109 | <LinkCard |
| 110 | title="Access and roles" |
| 111 | description="Give people a role on a repository, invite outside collaborators, and set what every member gets." |
| 112 | href="/guides/access-and-roles/" |
| 113 | /> |
| 114 | <LinkCard |
| 115 | title="Teams" |
| 116 | description="Group members into teams, give a team a role on repositories, mention it, and have it pick who reviews." |
| 117 | href="/guides/teams/" |
| 118 | /> |
| 119 | <LinkCard |
| 120 | title="Rules" |
| 121 | description="Protect branches and tags with rulesets: pull requests, checks, signed commits, merge windows, and rules for agents' changes." |
| 122 | href="/guides/rules/" |
| 123 | /> |
| 124 | <LinkCard |
| 125 | title="CODEOWNERS" |
| 126 | description="Say who owns which paths, ask them to review the changes to their files, and require their approval before a merge." |
| 127 | href="/guides/codeowners/" |
| 128 | /> |
| 129 | <LinkCard |
| 130 | title="Transferring a repository" |
| 131 | description="Move a repository to another workspace you own, while its old address keeps working." |
| 132 | href="/guides/transferring-repositories/" |
| 133 | /> |
| 134 | </CardGrid> |
| 135 | |
| 136 | ## Know the limits |
| 137 | |
| 138 | [What g1t can't do yet](/about/limitations/) lists every limit you can |
| 139 | hit today, why it exists, what to do instead, and whether it is planned. |
| 140 | |
| 141 | ## Using an AI assistant? |
| 142 | |
| 143 | Give it [g1t.sh/llms.txt](https://g1t.sh/llms.txt), which describes g1t for |
| 144 | agents, and ask it to set you up. Every page here also has **Copy page** at |
| 145 | the top, to paste into a conversation, and a plain Markdown version at its |
| 146 | address plus `.md`. |