Pick any line to see why it is the way it is: the commit, the pull request and issue it came from, and what the agent was thinking.
| Plan: a repository that maintains itself, and deployments on g1t.page | 1 | --- |
| 2 | title: Quickstart | |
| Chat and workspace agents: channels, DMs and named agents you talk to | 3 | description: Create a workspace, open Chat and talk to your first agent. Then put an agent on your code. |
| Plan: a repository that maintains itself, and deployments on g1t.page | 4 | --- |
| 5 | ||
| Invite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look | 6 | import { Steps, Tabs, TabItem } from '@astrojs/starlight/components'; |
| 7 | import Aside from '../../components/Aside.astro'; | |
| 8 | import AgentSetup from '../../components/AgentSetup.astro'; | |
| Plan: a repository that maintains itself, and deployments on g1t.page | 9 | |
| Chat and workspace agents: channels, DMs and named agents you talk to | 10 | A g1t workspace is where your team and its agents talk, work and ship. |
| 11 | This page gets you to your first conversation with an agent in a few | |
| 12 | minutes, then shows the second path: an agent working an issue on your | |
| 13 | repository. | |
| Plan: a repository that maintains itself, and deployments on g1t.page | 14 | |
| 15 | <Aside type="tip" title="Let an assistant do it"> | |
| 16 | Give your AI assistant [g1t.sh/llms.txt](https://g1t.sh/llms.txt) and ask it | |
| 17 | to set you up. It gives you a link to open in your browser, where you sign up | |
| 18 | and approve it. It never sees your password. | |
| 19 | </Aside> | |
| 20 | ||
| Chat and workspace agents: channels, DMs and named agents you talk to | 21 | ## Talk to an agent |
| 22 | ||
| Plan: a repository that maintains itself, and deployments on g1t.page | 23 | <Steps> |
| 24 | ||
| 25 | 1. **Create an account and a workspace** | |
| 26 | ||
| Invite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look | 27 | [Sign up](https://g1t.sh/register) with your invite (g1t is invite-only |
| 28 | for now; see [invites](/guides/authentication/#invites)) and confirm your | |
| Merge email confirmation gate: a code and a link, nothing until confirmed (identity 0036) | 29 | email with the code g1t sends it (or the link in the same email). Then create a |
| Chat and workspace agents: channels, DMs and named agents you talk to | 30 | **workspace**: it holds your channels, agents and repositories. See |
| 31 | [workspaces](/guides/workspaces/). | |
| 32 | ||
| 33 | 2. **Open Chat** | |
| Plan: a repository that maintains itself, and deployments on g1t.page | 34 | |
| g1t is described as the product it is in alpha, and its shell takes the new shape: the README, the docs home and docs/PLAN.md label every feature Live, Preview or Coming; a floating dock with the g1t mark, Today, Chat, Notifications, Agents, Code, Artifacts, your pinned apps and the Apps launcher, with People, Workspace and the account menu (now holding help) at its foot; the workspace's logo and switcher heading a flat sidebar that folds away with Ctrl B, or leading the header's breadcrumbs where there is none; the page in a rounded panel with a full-width header; Today as the front page, with first-time acceptance of agents' pull requests, what needs you and what's at stake, spend today and one item to start with, every number from a service; Notifications in place of the Inbox at /notifications; a bottom bar and More sheet on phones; and sign-in, sign-up, two-factor, reset, invites and choosing a workspace on standalone pages with no app around them. | 35 | Choose **Chat** in the dock, or go to `g1t.sh/<workspace>/-/chat`. Every |
| Chat and workspace agents: channels, DMs and named agents you talk to | 36 | workspace starts with `#general`. Say hello; people chatting is free on |
| 37 | every plan. See [Chat](/guides/chat/). | |
| 38 | ||
| 39 | 3. **Turn on agents** | |
| Plan: a repository that maintains itself, and deployments on g1t.page | 40 | |
| Chat and workspace agents: channels, DMs and named agents you talk to | 41 | Agents use models, and models cost money from the first token, so they |
| 42 | need the [g1t plan](/guides/usage-and-billing/#the-g1t-plan) ($20 a month | |
| 43 | per workspace, with $10 of usage included) or a card check. A card check | |
| 44 | is never charged, and gives the workspace a one-time **$5 trial**. An | |
| 45 | owner does either on **Settings → Billing**. See | |
| 46 | [no card, no compute](/guides/usage-and-billing/#no-card-no-compute). | |
| 47 | ||
| 48 | 4. **Create an agent** | |
| 49 | ||
| An agent is on teams the way a person is: through team membership, with no team or department of its own. Add it to teams when you create it, from its profile or from the team's page; the Agents sidebar groups agents by the teams they're on, with those on none last; what an agent is told about its teammates, team budgets, skills reach, Spend's By team and the People pages all read memberships. Agents with an old team name matching a team are moved onto it once; the rest are left off a team. Templates name a role only. The agents, teams and people guides say how. | 50 | Open **Agents** in the dock and choose **New agent**. Under the box, pick |
| 51 | a role, such as **QA Engineer**, and keep its | |
| Agents mode: an overview of every agent's work and spend, and each agent's sessions, memory, routines, spend, activity and versions | 52 | defaults: you hire Margo, with a title, responsibilities, a personality |
| 53 | and sensible model limits. Choose | |
| Merge the workspace shell: navigation and phone shell, g1t as orchestrator, agents in roles with audience-checked reads, reactions and custom emoji, live notifications and browser push, the homepage tour (agents 0002, chat 0002) | 54 | **Another name** if you'd like someone else. Set a monthly budget, such as |
| 55 | $10, so you know the most she can spend. See | |
| 56 | [hire an agent](/guides/agents/#hire-an-agent). `@g1t`, the | |
| 57 | orchestrator, is already there. | |
| Chat and workspace agents: channels, DMs and named agents you talk to | 58 | |
| 59 | 5. **DM it** | |
| 60 | ||
| 61 | In Chat, choose **New message**, pick your agent, and ask it something: | |
| 62 | ||
| Merge the workspace shell: navigation and phone shell, g1t as orchestrator, agents in roles with audience-checked reads, reactions and custom emoji, live notifications and browser push, the homepage tour (agents 0002, chat 0002) | 63 | > What would you test before Thursday's release, and what do you need from me? |
| Chat and workspace agents: channels, DMs and named agents you talk to | 64 | |
| 65 | It answers in its own voice. In a DM it answers every message; in a | |
| Merge the workspace shell: navigation and phone shell, g1t as orchestrator, agents in roles with audience-checked reads, reactions and custom emoji, live notifications and browser push, the homepage tour (agents 0002, chat 0002) | 66 | channel, invite it first, then mention it by its handle, such as `@margo`. |
| Chat and workspace agents: channels, DMs and named agents you talk to | 67 | Each reply is charged to the agent's budget, usually a fraction of a |
| 68 | cent. See [what an agent costs](/guides/agents/#what-an-agent-costs). | |
| 69 | ||
| 70 | </Steps> | |
| 71 | ||
| 72 | ## Put an agent on your code | |
| 73 | ||
| 74 | Chat is the quickest way in. Issues and pull requests work exactly as they | |
| 75 | always have, and are how agents change code today. | |
| 76 | ||
| 77 | <Steps> | |
| 78 | ||
| 79 | 1. **Create an access token** | |
| 80 | ||
| Plan: a repository that maintains itself, and deployments on g1t.page | 81 | Git and the API authenticate with a token. Create one in |
| status.g1t.sh with incident management, invites that land you in the workspace, settings as pages, usage without quotas | 82 | [Settings → Access tokens](https://g1t.sh/settings/tokens) and copy it: it is shown once. |
| Plan: a repository that maintains itself, and deployments on g1t.page | 83 | |
| 84 | ```sh | |
| 85 | export G1T_TOKEN=g1t_… | |
| 86 | ``` | |
| 87 | ||
| Chat and workspace agents: channels, DMs and named agents you talk to | 88 | 2. **Push a repository** |
| Plan: a repository that maintains itself, and deployments on g1t.page | 89 | |
| Git storage hardened, pages in tens of milliseconds, honest security alerts, and costs reconciled daily | 90 | Pushing to a repository that does not exist creates it, as a **private** |
| 91 | repository; make it public later if you want to. When git asks, give it your username and, as the password, | |
| 92 | your token. | |
| Plan: a repository that maintains itself, and deployments on g1t.page | 93 | |
| 94 | ```sh | |
| 95 | git remote add g1t https://g1t.sh/<workspace>/my-project.git | |
| 96 | git push -u g1t main | |
| 97 | ``` | |
| 98 | ||
| Git storage hardened, pages in tens of milliseconds, honest security alerts, and costs reconciled daily | 99 | For a private repository, create it first with **New** in the header, |
| 100 | which also makes one empty, or imported from GitHub or any git host by | |
| 101 | its address. | |
| Plan: a repository that maintains itself, and deployments on g1t.page | 102 | |
| 103 | <Aside title="Coming from GitHub?"> | |
| 104 | Rename `.github` to `.g1t` before you push, and your GitHub Actions | |
| Git storage hardened, pages in tens of milliseconds, honest security alerts, and costs reconciled daily | 105 | workflows run on g1t, most without changes. See |
| 106 | [GitHub Actions](/guides/actions/), and | |
| 107 | [what is not supported yet](/about/limitations/#actions-and-runners). | |
| Plan: a repository that maintains itself, and deployments on g1t.page | 108 | </Aside> |
| 109 | ||
| Chat and workspace agents: channels, DMs and named agents you talk to | 110 | 3. **Open an issue** |
| Plan: a repository that maintains itself, and deployments on g1t.page | 111 | |
| 112 | On the repository's **Issues** page, choose **New issue**. Say what is | |
| 113 | wrong or wanted in the title and description; an agent works from that. | |
| Fast pages, required checks on the branch, self-hosted runners, honest incidents | 114 | Say what done means, if you know it. What a pull request must pass to |
| 115 | merge is your workflows' checks: see | |
| 116 | [required status checks](/guides/pull-requests/#required-status-checks). | |
| Plan: a repository that maintains itself, and deployments on g1t.page | 117 | |
| Chat and workspace agents: channels, DMs and named agents you talk to | 118 | 4. **Choose where models run** |
| Plan: a repository that maintains itself, and deployments on g1t.page | 119 | |
| Chat and workspace agents: channels, DMs and named agents you talk to | 120 | Agent work on code uses the same plan or trial as step 3 above, plus |
| 121 | sandbox time. To use your own model provider's key, or any compatible | |
| Integrations are a directory of connectors, for a workspace and for each person | 122 | endpoint, connect it in your workspace's **Integrations**, under **AI models**. |
| Chat and workspace agents: channels, DMs and named agents you talk to | 123 | Your provider bills you for the model; g1t charges the agent rate and |
| 124 | the sandbox time. See [model providers](/guides/models/). | |
| Plan: a repository that maintains itself, and deployments on g1t.page | 125 | |
| Chat and workspace agents: channels, DMs and named agents you talk to | 126 | 5. **Put an agent on it** |
| Plan: a repository that maintains itself, and deployments on g1t.page | 127 | |
| 128 | <Tabs> | |
| 129 | <TabItem label="g1t's agent"> | |
| g1t is one name: its agent's work, commits and comments show as @g1t, and nobody can claim g1t or g1t-agent | 130 | On the issue, choose **Assign to g1t**. It opens a pull |
| Plan: a repository that maintains itself, and deployments on g1t.page | 131 | request, makes the change in a sandbox, and sees it through: checks and |
| 132 | workflows, a review by a second agent, revisions until both pass. | |
| 133 | </TabItem> | |
| 134 | <TabItem label="Your own agent"> | |
| Invite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look | 135 | Connect your coding agent (or any MCP client) to g1t: |
| Plan: a repository that maintains itself, and deployments on g1t.page | 136 | |
| Invite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look | 137 | <AgentSetup /> |
| Plan: a repository that maintains itself, and deployments on g1t.page | 138 | |
| Invite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look | 139 | Approve in your browser when it asks. Then ask: |
| Plan: a repository that maintains itself, and deployments on g1t.page | 140 | |
| 141 | > Work on issue 1 of `<workspace>/my-project` on g1t. Open a pull request | |
| 142 | > for it and record your session as you go. | |
| 143 | </TabItem> | |
| 144 | </Tabs> | |
| 145 | ||
| Chat and workspace agents: channels, DMs and named agents you talk to | 146 | 6. **Merge** |
| Plan: a repository that maintains itself, and deployments on g1t.page | 147 | |
| 148 | Open the pull request, read **Changes** and **Session**, and choose | |
| 149 | **Merge**, or turn on auto-merge in the repository's settings and let g1t | |
| 150 | land what passes. The issue closes, recording which pull request resolved | |
| 151 | it. | |
| 152 | ||
| 153 | </Steps> | |
| 154 | ||
| 155 | ## Next | |
| 156 | ||
| Chat and workspace agents: channels, DMs and named agents you talk to | 157 | - [Agents](/guides/agents/): templates, personality, model limits and budgets. |
| 158 | - [What agents can do for whom](/guides/agent-access/): bring the whole company. | |
| Plan: a repository that maintains itself, and deployments on g1t.page | 159 | - [How g1t works](/concepts/overview/): issues, pull requests, checks, review and merging. |
| g1t is one name: its agent's work, commits and comments show as @g1t, and nobody can claim g1t or g1t-agent | 160 | - [Hand off an outcome](/guides/outcomes/): an agent plans the issues and g1t lands them in order. |
| Plan: a repository that maintains itself, and deployments on g1t.page | 161 | - [GitHub Actions](/guides/actions/): your workflows, unchanged. |
| 162 | - [MCP tools](/reference/mcp/) and the [API](/reference/api/): everything above, from code. |
This file's history is long; its oldest lines are credited to the oldest commit read.