| 1 | --- |
| 2 | title: Ask g1t |
| 3 | description: Ask g1t about your work from the top bar of any page. It answers with your workspace's own AI provider and key, reads g1t as you with read-only access, and shows each step it takes and the pages it drew on. |
| 4 | --- |
| 5 | |
| 6 | **Ask**, in the top bar, opens a conversation with g1t beside the page |
| 7 | you are on. Ask about the issue you are reading, the pull request you are |
| 8 | reviewing, or anything else about your work, and the answer streams in as |
| 9 | it is written. |
| 10 | |
| 11 | Ask answers with **your workspace's own AI provider**, on your workspace's |
| 12 | own key: one of [your AI providers](/guides/ai/), |
| 13 | and **Auto** or the model an owner chose for it. g1t hosts no model for Ask and bills |
| 14 | nothing for it; what an answer costs is on your provider's bill. Your key |
| 15 | stays sealed in g1t: it is used to call the provider and is never sent to |
| 16 | your browser. |
| 17 | |
| 18 | ## Set it up |
| 19 | |
| 20 | An owner of the workspace sets it up once: |
| 21 | |
| 22 | 1. Open **AI**, in the workspace's settings, at |
| 23 | `g1t.sh/<workspace>/-/ai`. |
| 24 | 2. Add a provider if there is none yet: a frontier lab such as |
| 25 | Anthropic, OpenAI or Gemini, a model platform, or a model you host |
| 26 | yourself behind an Anthropic- or OpenAI-compatible endpoint. |
| 27 | 3. Under **Ask g1t**, choose the provider and its model, then **Use for |
| 28 | Ask**. The model starts at **Auto** (see [Auto](#auto)); choose one of |
| 29 | the models the provider offers to use that one for every answer. For |
| 30 | Azure OpenAI, give the deployment's name; for an endpoint that does not |
| 31 | list its models, the model's name. |
| 32 | |
| 33 | Every member can then ask. Until a provider is chosen, Ask says so: owners |
| 34 | get a link to set it up, and members are told to ask an owner. A message |
| 35 | to @g1t in Chat before then gets a short reply from g1t saying the same. **Turn Ask |
| 36 | off** on the same page stops it answering, and removing the provider it |
| 37 | uses does too. |
| 38 | |
| 39 | Every AI provider g1t connects works with Ask: Anthropic and |
| 40 | Anthropic-compatible endpoints through Anthropic's Messages API, and the |
| 41 | rest through OpenAI's Chat Completions API. |
| 42 | |
| 43 | ### Auto |
| 44 | |
| 45 | **Auto**, the default, picks one of the provider's models for each |
| 46 | question, by a fixed rule and with no extra call to the provider: |
| 47 | |
| 48 | | The question | Auto answers with | |
| 49 | | --- | --- | |
| 50 | | A lookup: who has an issue, a link, how many pull requests are open | The provider's newest fast model: Haiku, a `mini` or `flash` model, an `instant` one | |
| 51 | | One that needs several reads or reasoning: why or how something happened, what shipped, a day or a week summed up, a failure to diagnose, work to plan; a long question, several at once, or a long conversation | Its newest standard model: Sonnet, GPT, Gemini Pro, a `versatile` or `large` one | |
| 52 | |
| 53 | Auto tells models apart by the words in their names, from the list the |
| 54 | provider gave when it was last tested, so it works the same for every |
| 55 | provider. The largest and most expensive models, such as Opus or OpenAI's |
| 56 | `pro` models, are used only when the provider offers nothing else: every |
| 57 | answer is on your workspace's key. When a tier is missing, Auto uses the |
| 58 | nearest one. A provider that lists no models (an endpoint, an Azure |
| 59 | deployment) answers with its own model. If Auto has nothing to choose |
| 60 | from, Ask says so: test the provider to list its models again, or choose |
| 61 | one. |
| 62 | |
| 63 | Each answer names the model that wrote it, such as **Anthropic · Auto · |
| 64 | claude-sonnet-5-5**. Workspaces that chose Ask's model before Auto existed |
| 65 | and kept the one the picker started at moved to Auto; a model an owner |
| 66 | picked stays picked. |
| 67 | |
| 68 | ## What it can read |
| 69 | |
| 70 | Ask reads g1t to answer: whatever you can read, and nothing more. It uses |
| 71 | the same tools the [g1t MCP server](/reference/mcp/) gives any agent, run |
| 72 | as you: repositories and their files and commits, issues, pull requests |
| 73 | and their changes, workflow runs and their logs, deployments, releases, |
| 74 | production telemetry, and what happened across your workspace. Every read |
| 75 | goes through the same permission checks as your own, so it never sees a |
| 76 | repository, issue or log you could not open yourself. |
| 77 | |
| 78 | Each question asked from the panel is sent with a short note saying that |
| 79 | this is Ask in your workspace and which page you are on (a question |
| 80 | written in Chat says you are in Chat): the repository, and the issue or pull |
| 81 | request number, when there is one. On an issue or a pull request, g1t also |
| 82 | reads its title, state and description, as you can see them, and sends |
| 83 | those along, so you can ask "what is left to do here?" without pasting |
| 84 | anything. |
| 85 | |
| 86 | It only reads. For each answer g1t makes a credential that is yours, holds |
| 87 | read permissions only, reaches only this workspace, and ends with the |
| 88 | answer, a few minutes at most. Nobody sees it: not the model, not your |
| 89 | browser. Anything that would change g1t is refused, whatever your role. |
| 90 | |
| 91 | Each question is also sent with which page you are on and today's date. On |
| 92 | an issue or a pull request, g1t sends its title, state and description, so |
| 93 | you can ask "what is left to do here?" without pasting anything. Some |
| 94 | questions it answers well: |
| 95 | |
| 96 | - What shipped today across all our projects? |
| 97 | - Why did the last Deploy fail? |
| 98 | - Summarize this pull request. |
| 99 | - How do I run this project's tests? |
| 100 | - What changed in this file recently, and why? |
| 101 | |
| 102 | For a question about the whole workspace, Ask reads the workspace's |
| 103 | activity first: merged pull requests, releases, deployments, workflow runs |
| 104 | and pushes across every repository you can read, in one read |
| 105 | (`activity` on the MCP server's `workspace` tool, or |
| 106 | [`GET /workspaces/{workspace}/activity`](/reference/api/workspaces/get-workspace-activity/)). |
| 107 | |
| 108 | ### What Ask means by shipped |
| 109 | |
| 110 | A change ships when it reaches a repository's default branch, pushed or |
| 111 | merged from a pull request, and then production. Production is a |
| 112 | successful deployment: |
| 113 | |
| 114 | - a project's production deployment on g1t.page, or |
| 115 | - for a repository that deploys itself, a successful run of its deploy |
| 116 | workflow on the default branch: a workflow whose name or file says |
| 117 | deploy, such as `.g1t/workflows/deploy.yml`, and not one for previews. |
| 118 | |
| 119 | Releases and tags are one more signal, not what shipping means. So "What |
| 120 | shipped today?" is answered with the commits that reached default branches |
| 121 | since the start of your day (in your profile's time zone), grouped by what |
| 122 | changed, and for each: **live** (with the deploy that carried it), **still |
| 123 | deploying**, **failed to deploy** (with the run, linked), or **not |
| 124 | deployed**. A deploy carries the commit it ran for and every commit before |
| 125 | it on the branch. |
| 126 | |
| 127 | People are named by their g1t username. A commit's author is matched to |
| 128 | the account their address belongs to (a confirmed address or the account's |
| 129 | noreply address, as commits on g1t.sh show them); a commit by an address |
| 130 | no account has is named as git recorded it, without an @. |
| 131 | |
| 132 | Answers link to what they name on g1t, and every number, title and link |
| 133 | comes from what Ask read; when something does not exist, it says so. |
| 134 | Answers come from a model and can still be wrong: follow the links to |
| 135 | check. |
| 136 | |
| 137 | ### Steps and sources |
| 138 | |
| 139 | While Ask works, the panel shows each step as it runs, such as **Read |
| 140 | activity in acme since 2026-10-12** or **Read pull request #7 in |
| 141 | acme/web**, with what it found and a link to the page it read. A step that |
| 142 | was refused, or that failed, says why. Once the answer is written the steps |
| 143 | fold into one line you can open again. Under the answer, **Sources** lists |
| 144 | the pages on g1t it links to, and the ones it read directly. |
| 145 | |
| 146 | ### Asking for work |
| 147 | |
| 148 | Ask does not do the work itself: it does not write code or change |
| 149 | anything. g1t coordinates the work, and a session in your own harness does |
| 150 | it. When you ask for work to be done, such as planning a change, fixing a |
| 151 | bug or implementing an issue, Ask reads the issue the work belongs to, |
| 152 | checks whether a session already holds it, and proposes a session: a card |
| 153 | under the answer that names the issue (or a new one it would open) and |
| 154 | what the session should do (plan, implement or review). |
| 155 | |
| 156 | Nothing starts until you choose on the card: |
| 157 | |
| 158 | - **Start session** runs it on your workspace's Anthropic account as a |
| 159 | [Claude Managed Agents session](/guides/sessions/), with g1t's tools and |
| 160 | skills beside your own. It shows when an owner has connected Anthropic. |
| 161 | - **Copy Claude Code command** copies a `claude` command that runs it on |
| 162 | your computer with the [g1t plugin](/guides/claude-code-plugin/), with |
| 163 | your own skills, settings and subagents. |
| 164 | |
| 165 | Either way the session is tied to the issue: it shows on the issue, on the |
| 166 | repository's Work page and on its own session page, with its subagents, and |
| 167 | Ask can tell you where it stands. If a session already holds the issue, Ask |
| 168 | links it rather than proposing another. |
| 169 | |
| 170 | ## One conversation, in Ask and in Chat |
| 171 | |
| 172 | Ask is your **direct message with @g1t** in [Chat](/guides/chat/#talk-with-g1t). |
| 173 | What you ask in the panel is posted there, and g1t's answer is written |
| 174 | there as it streams, so it shows in both places at once: start a question |
| 175 | on an issue page, and read the answer later in Chat, on your phone, or |
| 176 | in the desktop app. **Open in Chat** at the top of the panel takes you to |
| 177 | it. Nobody else can read it, and it stays until you delete it or |
| 178 | [clear it](#clear-the-conversation). |
| 179 | |
| 180 | - **New conversation** leaves a mark in the direct message. From then on, |
| 181 | g1t reads only what comes after it, and the panel shows only that; what |
| 182 | came before stays in Chat to read. |
| 183 | - **Clear conversation…**, in the panel's **⋯** menu, deletes the whole |
| 184 | conversation for good. Typing `/clear` and pressing **Enter** does the |
| 185 | same. See [Clear the conversation](#clear-the-conversation). |
| 186 | - **Stop**, or **Esc** while an answer is coming, ends the answer; what had |
| 187 | come so far stays. Writing again while g1t is still answering does the |
| 188 | same: g1t stops and answers your newest words, reading both. |
| 189 | - **Answer again**, under g1t's latest answer, has it write that answer |
| 190 | anew. |
| 191 | - **Copy** copies an answer as Markdown. Each answer shows the provider |
| 192 | and model that wrote it, with **Auto** when Auto chose the model. |
| 193 | |
| 194 | Answers are Markdown: code is highlighted with its language and a Copy |
| 195 | button, tables scroll within the answer, and issues, pull requests and |
| 196 | commits (`acme/web#12`, a link to one, a commit hash) show as chips that |
| 197 | open their title and state when you hover over them. Links to |
| 198 | [artifacts](/guides/artifacts/) show their card. Pictures show only from |
| 199 | g1t itself; any other picture is a link. |
| 200 | |
| 201 | In the panel, **Enter** sends, **Shift+Enter** starts a new line, and |
| 202 | **⌘K** (**Ctrl+K**) puts you back in the box. On an empty conversation, |
| 203 | the panel suggests a few questions for the page you are on. |
| 204 | |
| 205 | ## Clear the conversation |
| 206 | |
| 207 | **New conversation** only changes what g1t reads: everything said before |
| 208 | the mark is still kept, and still in Chat. To delete it, clear the |
| 209 | conversation: |
| 210 | |
| 211 | 1. Open **Ask** in the top bar, or your direct message with **g1t** in |
| 212 | Chat. |
| 213 | 2. Choose **⋯ → Clear conversation…**, or type `/clear` in the box and |
| 214 | press **Enter**. |
| 215 | 3. Choose **Clear conversation** to confirm. |
| 216 | |
| 217 | Everything in your direct message with g1t is deleted for good, in Ask |
| 218 | and in Chat, on every device. It can't be undone, and g1t remembers none |
| 219 | of it: the next question starts with nothing before it. |
| 220 | |
| 221 | | Deleted | Kept | |
| 222 | | --- | --- | |
| 223 | | Your questions, and the page each was asked from | The direct message itself, empty, so Ask and Chat open it as before | |
| 224 | | g1t's answers, with their steps, sources and proposed sessions | Chat's daily count of messages and bytes for the workspace, which has no text and no names in it and is kept for billing | |
| 225 | | Thread replies, reactions, "New conversation" marks, and deleted messages' empty places | Issues, pull requests and sessions you started from an answer: they are your workspace's, not the conversation's | |
| 226 | | Your read mark and unread count for it | What your AI provider was sent to answer: it went to the provider, under your workspace's agreement with them | |
| 227 | | The notifications its answers sent you, in g1t's notifications panel | Browser and phone notifications already shown on a device | |
| 228 | |
| 229 | An answer still being written when you clear is stopped and thrown away, |
| 230 | not saved: it never comes back to the conversation, and it does not |
| 231 | notify you. A question you send after clearing is answered as the start |
| 232 | of a new conversation. |
| 233 | |
| 234 | Clearing is only ever your own: nobody else can clear your conversation |
| 235 | with g1t, not even a workspace owner, and you can't clear anyone else's |
| 236 | or a channel. Clearing a conversation that is already empty does nothing. |
| 237 | |
| 238 | ## Limits |
| 239 | |
| 240 | - 20 questions a minute for each person; past that, g1t says to wait a |
| 241 | moment. |
| 242 | - g1t reads the conversation since the last **New conversation**, up to |
| 243 | its latest 40 messages and 64,000 characters, the newest first; a |
| 244 | message longer than 16,000 characters is cut to that. |
| 245 | - An answer is at most 4,096 tokens long, and says when it was cut off. |
| 246 | - An answer reads g1t in at most 10 rounds and 30 reads, over at most 2 |
| 247 | minutes; then it answers with what it has read and says what it could |
| 248 | not check. |
| 249 | - The model is given at most 16,000 characters of any one read and 120,000 |
| 250 | in all. A longer read is trimmed: long lists keep their first items (a |
| 251 | job's log keeps its end, where a failure says why), long texts are |
| 252 | shortened, and each says how much was left out. |
| 253 | - Its reads count against the [API's rate limit](/reference/rate-limits/) |
| 254 | like any other access token's. Each step is also a call to your AI |
| 255 | provider, on your provider's bill. |