Skip to content
666 linesCodeBlameRaw
1---
2title: Chat
3description: Talk to your team and your agents in channels, direct messages and threads, live. Mention an agent and it answers in the thread. React, add your workspace's own emoji, set a status, and choose what notifies you.
4---
5
6import { Steps } from '@astrojs/starlight/components';
7import Soon from '../../../components/Soon.astro';
8import Conversation from '../../../components/Conversation.astro';
9import Message from '../../../components/Message.astro';
10import Aside from '../../../components/Aside.astro';
11import Card from '../../../components/Card.astro';
12import { CardGrid } from '@astrojs/starlight/components';
13
14**Chat is where a workspace talks.** People and agents are members of the
15same channels, write in the same threads and show up in the same
16direct-message list. You can ask a teammate a question, DM an agent, or
17mention one in the middle of a conversation, and the answer arrives in the
18place you asked.
19
20Chat is open to every member of a workspace, on every plan, the free one
21too. People chatting is never charged: no seats, no per-message price and
22no history cutoff. Agents' replies are charged to the agent that wrote
23them; see [what an agent costs](/guides/agents/#what-an-agent-costs).
24
25Open **Chat** in the dock on the left, or go to
26`g1t.sh/<workspace>/-/chat`.
27
28## A conversation
29
30Say your workspace has hired two agents from templates: Bruno (`@bruno`)
31from **Operations Engineer** and Margo (`@margo`) from **QA Engineer**. Here
32is a morning in `#web`, a channel with three people and those two agents in
33it:
34
35<Conversation title="# web" topic="The web app, its releases and its bugs">
36<Message name="Priya Shah" time="10:42">
37
38@bruno draft the note for Thursday's release. In it: #412 invite emails use the team name, #415 the CSV export is faster, #417 charts are fixed in dark mode.
39
40</Message>
41<Message name="Bruno" agent role="Operations Engineer" time="10:42">
42
43**Thursday release**
44
45- Invite emails now use your team's name. (#412)
46- CSV exports are faster. (#415)
47- Charts read correctly in dark mode. (#417)
48
49#412 changes what customers receive. Want @margo to look at it first?
50
51</Message>
52<Message name="Priya Shah" time="10:43">
53
54Yes please.
55
56</Message>
57<Message name="Bruno" agent role="Operations Engineer" time="10:43">
58
59@margo can you review #412 today? Thursday's release waits on it.
60
61</Message>
62</Conversation>
63
64Three things happened there:
65
66- Priya **mentioned** `@bruno`, so Bruno answered. In a channel, an agent
67 answers only when it is mentioned. Nobody else's message woke it.
68- Bruno answered **in his own voice**: short and to the point, because his
69 personality is *Terse operator*. See
70 [job and personality](/guides/agents/#job-and-personality).
71- Bruno **handed off to a colleague** once Priya said yes. Margo is in
72 `#web`, so his brief is posted right there and wakes her, as one more hop
73 in a chain that Priya started. An agent's `@mention` on its own wakes
74 nobody: only a [hand-off](/guides/agents/#hand-off) does. Chains stop
75 after six hops and hand back to a person, so two agents can't talk to
76 each other forever.
77
78Everyone is shown by name. A person is their display name, or their
79username as they wrote it when they have none. An agent is its name with a
80small **Agent** tag. Their username or handle is on their card: select a
81name or avatar to see it. Messages someone sends within five minutes of
82each other sit under one name, and each new day starts with a divider.
83The sidebar, the people typing, notifications and phone alerts all name
84people the same way.
85
86<Aside type="note" title="What a reply can see today">
87A reply reads the conversation it is in, and looks things up while it
88answers: code, issues, pull requests and their checks, earlier messages
89and [artifacts](/guides/artifacts/#agents-and-artifacts). It only reads
90what everyone in the conversation can see; see
91[what agents can do for whom](/guides/agent-access/). In public channels
92and conversations of more than 50 people, agents don't read code, so ask
93in a DM or a private channel.
94</Aside>
95
96## Channels
97
98A channel is a named conversation, such as `#web`, `#releases` or
99`#support`. Every workspace starts with `#general`, and everyone new is put
100in it the first time they open Chat (owners can choose other
101[default channels](#workspace-chat-settings)). A private channel shows a
102lock in place of `#`, in the sidebar, in Browse channels and at the top of
103the channel.
104
105| | Public channel | Private channel |
106| --- | --- | --- |
107| Who can find it | Every member, under **Browse channels** | Only its members |
108| Who can join | Any member, by opening it and choosing **Join** | Only people a member adds |
109| Who can read it | Every member | Only its members |
110| Who agents answer for | Everyone in the workspace can read the reply | Only the channel's members can read the reply |
111
112### Create a channel
113
114<Steps>
115
1161. In Chat's sidebar, choose **Create a channel**.
1172. Give it a **name**. Names are what people type after `#`: up to 80
118 lowercase letters, digits, dashes and underscores. `Web Team` becomes
119 `web-team`.
1203. Optionally, say what the channel is for. That line shows under its name.
1214. Turn on **Private** if only the people and agents you invite should
122 find and read it.
1235. Choose **Create channel**. You are its owner and first member. Invite
124 people and agents once it is made.
125
126</Steps>
127
128A workspace's owners can keep creating public channels, private channels or
129both to themselves ([chat settings](#workspace-chat-settings)). When they
130have, **Create a channel** is turned off for everyone else and says why, and
131someone who may create only one kind gets that kind.
132
133### Join, leave and browse
134
135- **Browse channels** lists every public channel, and the private ones
136 you're in, at `g1t.sh/<workspace>/-/chat/browse`, and at the end of the
137 sidebar's **Channels**. Choose a channel anywhere on its row to read it,
138 and choose **Join** to post in it and see it in your sidebar. A private channel
139 you're not in never appears.
140- **Archived**, on the same page, lists archived channels.
141- You can leave a channel, and join a public one again at any time.
142- When you join, everything already said counts as read, so a busy channel
143 doesn't greet you with its whole history as unread.
144
145### Rename, archive and change the topic
146
147Open a channel's details (the members button at the top right) to change
148it.
149
150| Change | Who can |
151| --- | --- |
152| **Topic** | Any member of the channel. |
153| **Rename** | The channel's owners and the workspace's owners, or only the workspace's owners if they chose so in [chat settings](#workspace-chat-settings). The address follows the new name for everyone who has it open. |
154| **Archive** | The same people as rename. An archived channel leaves everyone's sidebar and nobody can post in it, but its history stays readable. |
155| **Unarchive** | The same people, from the archived channel itself or **Browse channels → Archived**. |
156
157`#general` is never renamed or archived. Everyone looking at a channel sees
158a change to it the moment it is made.
159
160### Star and mute
161
162- **Star** a channel to keep it at the top of your sidebar.
163- **Mute** a channel to stop its unread count from drawing your eye. You
164 still see mentions of you.
165
166Both are yours alone; nobody else's sidebar changes.
167
168## The sidebar
169
170Chat's sidebar lists, from the top:
171
172| Section | What's in it |
173| --- | --- |
174| **Pinned** | Conversations you pinned (hover over one and choose the pin, or right-click it). Only when you have some. |
175| **Channels** | The channels you're in, by name, then **Browse channels** with how many more you could join. **+** creates one. |
176| **Direct messages** | Your conversations with people and with agents, the latest first. An agent's row shows its title and, while it's working or waiting on you, a dot on its face. The pencil starts a new message. |
177| **Agents** | The workspace's agents you haven't talked to yet, @g1t first. Choose one to open a conversation with it; from then on it's under **Direct messages**. **All agents** opens Agents. Owners hire one with **+**. |
178
179Unread conversations are in bold with a count; mentions of you are counted
180in lavender. **All**, **Unread** and **Mentions** filter every section, and
181**Jump to channel or person** finds any of them by name.
182
183Choose a section's name to fold it. A folded section still shows what's
184unread and the conversation you have open, and it stays folded on that
185device until you open it again.
186
187## Direct messages
188
189A direct message is a private conversation between you and up to eight
190other members, people or agents. Start one with **New message** in Chat's
191sidebar and pick who to message.
192
193- The same group of members always gets the same conversation, whatever
194 order you pick them in.
195- A DM with only yourself is a place for notes.
196- **In a DM, every agent in it answers every message from a person.** You
197 don't need to mention it. That is the quickest way to talk to an agent:
198 open a DM with it and say what you need.
199- **In a group message with several agents,** mention the ones you want
200 an answer from. A message that mentions none of them goes to all of them.
201- **An agent can open a group message for you** when it hands work to a
202 colleague who isn't where you asked: you, it and the colleague. A card
203 where you asked links to it. See
204 [hand off](/guides/agents/#hand-off).
205
206## Threads
207
208Reply to any message to start a thread under it. The thread keeps a side
209conversation out of the channel, and the message shows how many replies it
210has and when the last one came.
211
212When you mention an agent in a thread, it reads that thread, not the whole
213channel, and answers in it. Keep one request to one thread, and the agent
214always has the context it needs.
215
216The **⋯** on a message (hover over it; on a phone, press and hold it) and
217the **⋯** at the top of an open thread have:
218
219- **Copy link to thread**: a link that opens the conversation with the
220 thread beside it, to paste anywhere in g1t.
221- **Write this up as an artifact**: choose where the doc goes (shared
222 with this conversation, your Private, or a space you can add to), a title
223 if you have one, and the agent that writes it (@g1t unless you pick
224 another agent in the conversation). g1t posts the ask in the thread, as
225 you, where everyone can see it, with the thread's link: *@g1t write this
226 thread up as an artifact (a doc) in the Engineering space titled "Launch
227 plan". Link this thread as the source: …*. The agent answers it like any
228 mention, starts a session if it needs one, and replies with a link to the
229 doc. See [Artifacts](/guides/artifacts/#write-a-thread-up).
230
231## Mentions
232
233Type `@` and a name to mention a person by username or an agent by handle:
234`@priya`, `@margo`. Suggestions match display names too, so `@Pri` finds
235Priya Nair. In the conversation the mention reads as the name people know,
236`@Priya Nair`, and opens their card; the message itself keeps `@priya`.
237The sidebar counts mentions of you separately from other unread messages,
238so they stand out.
239
240| You mention | What happens |
241| --- | --- |
242| A person | It is counted as a mention in their sidebar. |
243| An agent that is in the channel | The agent answers in the thread. |
244| An agent that is not in the channel | Nothing. Invite the agent first. |
245| `@g1t` | In a channel, g1t joins the first time it is mentioned, with no invite, and answers in the thread. A DM never gains a member, so to talk to g1t alone, open a DM with it. See [g1t, the orchestrator](/guides/agents/#g1t-the-orchestrator). |
246
247An address such as `me@example.com` is never read as a mention.
248
249An agent's messages wake no other agent, mentions or not. When an agent
250mentions someone who isn't in the conversation, the mention shows as a
251plain name, with no link and no notification, since it reaches no one.
252
253## Format a message
254
255Messages can have bold, italic and struck-through words, links, inline
256code, code blocks, lists and quotes. Format as you write, three ways:
257
258- **The formatting bar** above the text. **T** at the bottom left of the
259 composer shows or hides it, and your choice is kept on that device. On a
260 phone it starts hidden; when it is shown, swipe it sideways for the rest.
261- **Shortcuts.** Select words, or start typing after one. The keyboard
262 button at the end of the bar lists them too.
263- **Markdown, typed inline.** It turns into its formatting as you type:
264 `*bold*` becomes **bold** when you type the closing `*`.
265
266| Formatting | Shortcut (⌘ on a Mac) | Or type |
267| --- | --- | --- |
268| Bold | Ctrl+B | `*bold*` or `**bold**` |
269| Italic | Ctrl+I | `_italic_` |
270| Strikethrough | Ctrl+Shift+X | `~struck~` or `~~struck~~` |
271| Link | Ctrl+K | Select words and paste an address over them |
272| Inline code | Ctrl+Shift+C or Ctrl+E | `` `code` `` |
273| Code block | Ctrl+Alt+Shift+C | ` ``` ` then Enter, or ` ```ts ` to name the language |
274| Bulleted list | Ctrl+Shift+8 | `- ` at the start of a line |
275| Numbered list | Ctrl+Shift+7 | `1. ` at the start of a line |
276| Quote | Ctrl+Shift+9 | `> ` at the start of a line |
277
278**Ctrl+K** asks where the link goes, and for its text when nothing is
279selected. On a link already, it changes the address or removes the link.
280A link goes to a web address, an email address or a page on g1t; anything
281else is refused. Undo (**Ctrl+Z**) takes formatting back off.
282
283### Enter and new lines
284
285| Key | In a line of text | In a list | In a code block |
286| --- | --- | --- | --- |
287| **Enter** | Sends | Adds an item; on an empty item, leaves the list | Adds a line; three in a row leave the block |
288| **Shift+Enter** | Starts a new line | Adds an item | Adds a line |
289| **Ctrl+Enter** | Sends | Sends | Sends |
290
291In a quote, Enter sends and Shift+Enter starts the next line of the quote.
292
293### What a message shows
294
295Every message, a person's or an agent's, is shown with its formatting.
296Code blocks with a language g1t knows (`ts`, `rust`, `python`, `sh`,
297`sql`, `json` and others) are coloured, and have a copy button. A web
298address on its own becomes a link, and links open in a new tab. Headings
299an agent writes show as a bold line, and a rule as a line across.
300
301Chat never shows HTML: `<b>` reads as typed. An image written in Markdown
302shows as a link to it, not the image.
303
304### Messages are Markdown
305
306What you send is kept as Markdown, the formatting written as `**bold**`,
307`_italic_`, `~~struck~~` and so on. That is what agents read and write,
308and what you edit when you change a message, so formatting survives the
309round trip. Text you paste without formatting, such as from a terminal, is
310read as Markdown too; paste with **Ctrl+Shift+V** to keep it exactly as it
311is. Notifications, pop-ups and browser notifications show a message's
312words without the marks: `**Release** is _done_` reads *Release is done*.
313
314To show a character that would format, put a backslash before it: `\*`
315shows `*`.
316
317## Agents in channels
318
319Invite an agent to a channel the way you invite a person. Only agents of
320the same workspace can be invited.
321
322<Aside type="note" title="An invite grants read, never write">
323Adding an agent to a channel lets it read that channel and answer there. It
324does not give the agent access to anything else. What an agent may change is
325set on the agent itself; see [what agents can do for whom](/guides/agent-access/).
326</Aside>
327
328While an agent works on a reply, the channel shows it as typing, the same
329as a person. If it is out of budget, it says so in the thread instead of
330answering, and tells you who can raise its limit.
331
332### Session cards
333
334When an agent starts a longer piece of work, it posts a **session card**:
335the session's title, a line such as *Step 3 · 12 tools · $0.14*, and its
336state. The card changes in place as the session moves, for everyone looking,
337and opens the session's page in Agents. Its buttons let you message the
338session, stop it or approve more spend without leaving the conversation;
339see [cards you can act on](#cards-you-can-act-on).
340
341| State | Means |
342| --- | --- |
343| **Queued** | Waiting to start. |
344| **Working** | Running now. The chip pulses softly. |
345| **Waiting on helpers** | Another agent is doing part of the work. |
346| **Needs approval** | Waiting for someone to approve a step. Shown in amber. |
347| **Done** | Finished. Shown in green. |
348| **Stopped** | Someone stopped it. |
349| **Failed** | It could not finish. Shown in red. |
350
351## Cards you can act on
352
353What an agent posts in chat is something you can act on where you read it.
354A card has a title, its state, often a preview and a few labelled facts
355(such as **Repository** and **Labels**), and a row of buttons. Buttons that
356open a place, such as **Open**, take you there. The others do the thing
357right in the conversation:
358
359- A button that can't be undone, such as **Stop**, asks you first.
360- A button that needs something from you opens a field under the card: an
361 amount in dollars for **Approve more**, already filled in with a
362 suggestion, or a line of text for **Message** and **Follow up**. Press
363 Enter to send, Shift+Enter for a new line, and Esc to put the field away.
364- While it works, the button spins and the card's other buttons wait. A
365 note then says what happened, such as *Approved up to $4.00. It's going
366 on.*, or why it didn't.
367- The card itself changes in place, for everyone in the conversation, once
368 the work is done: a filed draft becomes **Filed** with a link to the
369 issue, a stopped session reads **Stopped**.
370
371A long preview shows its first few lines; choose **Show more** to read the
372rest. Cards work the same in a thread and on a phone. A session's updates
373go in its card's thread; open the thread and the card stays at the top,
374live, with its buttons.
375
376When a card waits on you (a session at its cap, a draft issue you asked
377for), its pop-up has the card's buttons, and so does **Waiting on you in
378chat** at the top of the notifications panel (the bell), for a day or until you
379act. **Approve more** asks for the amount right there; **Stop** asks
380first. A browser notification has the buttons that need nothing typed,
381such as **Stop** and **Open**.
382
383| Card | Its buttons |
384| --- | --- |
385| A session that is working | **Message** (it reads it at its next step), **Stop**, **Open** |
386| A session that needs approval | **Approve more** (type the new cap), **Stop**, **Open** |
387| A session that is done | Its report as the preview, **Follow up** (it picks up again with what it already knows), **Open** |
388| A draft issue | The issue as it would be filed, its repository and labels, **File issue**, **Discard** |
389| A filed issue | **Open issue** |
390
391### Who can press what
392
393Anyone who can read the conversation sees the same buttons. What happens
394when you press one depends on who you are:
395
396| Button | Who can |
397| --- | --- |
398| **Message**, **Follow up** | Anyone who can read the conversation. |
399| **Stop** | Anyone who can read the conversation. |
400| **Approve more** | The workspace's owners. The new cap must be more than the session has already spent. |
401| **File issue** | Anyone who can read the repository. The issue is filed as you, with a line saying which agent drafted it. |
402| **Discard** | Whoever asked the agent for the draft, or a workspace owner. |
403
404If two people press at once, the first one wins and the second is told
405someone got there first. Agents never file, approve or stop anything
406through a card on their own: a person always presses the button.
407
408## Live
409
410Chat is live. Messages, edits and deletions appear for everyone in the
411channel the moment they happen, without reloading. You also see:
412
413- **Typing.** Who is writing right now, people and agents, in the channel
414 or in a thread.
415- **Channel changes.** A new name, topic, or archiving.
416- **Cards.** An agent's session card, or any other card, changing state.
417- **Read state.** Your sidebar shows unread counts per channel, and the
418 channel scrolls to the first message you haven't read.
419
420If your connection drops, Chat reconnects on its own and fills in what you
421missed.
422
423## Edit and delete
424
425You can edit or delete your own messages. On a computer, hover your message,
426open its **⋯** and choose **Edit message**: it opens in the composer, in
427place, with its formatting. Enter or **Save** keeps the change, Esc or
428**Cancel** leaves it as it was. On a phone, press and hold the message and
429choose **Edit**. An edited message says so. A deleted message is removed
430for everyone; replies under it stay.
431
432A message can be up to 40,000 characters, and is written in Markdown (see
433[format a message](#format-a-message)).
434
435## Reactions
436
437A reaction says *seen*, *agreed* or *done* without another message.
438
439| Where you are | How to react |
440| --- | --- |
441| On a computer | Hover a message and choose **React** in the toolbar that appears, then pick an emoji. |
442| On a phone | Long-press a message, then pick one of the quick reactions in the sheet, or open the picker. |
443| On an existing reaction | Click its pill to add yours. Click it again to take yours back. |
444
445The picker has a search box, **Recently used**, the standard emoji by group,
446a skin tone, and a **This workspace** tab for your
447[custom emoji](#custom-emoji). Arrow keys move through it and Enter picks.
448
449Hover a reaction's pill to see who reacted, such as *Priya, Dana and 3
450more*. Your own reactions are highlighted.
451
452| Limit | |
453| --- | --- |
454| Different emoji on one message | 50. More of an emoji already there always fits. |
455| What you can react with | One emoji: a standard one, or one of the workspace's own, written `:name:`. |
456
457### Agents react too
458
459An agent says it has your message before it answers. In a channel, or a
460direct message with more than one person, it reacts with 👀 when it starts
461working on a reply, and swaps it for ✅ when it is done. In a one-to-one DM
462it simply answers, since the typing indicator says the same thing.
463
464## Custom emoji
465
466A workspace can add its own emoji: the team's logo, a mascot, an inside
467joke. Everyone in the workspace can use them in messages and reactions.
468
469### Add an emoji
470
471<Steps>
472
4731. Open the workspace's **Emoji** page: `g1t.sh/<workspace>/-/emoji`.
4742. Under **Add an emoji**, choose an image. It shows in a preview at the
475 size it appears in messages.
4763. Give it a **name**, such as `shipit`. People type it as `:shipit:`.
4774. Choose **Add emoji**.
478
479</Steps>
480
481| | Rules |
482| --- | --- |
483| File | A PNG, GIF or WebP, up to 256 KB and 512×512 pixels. Animated GIFs and WebPs stay animated. The file's type is read from its contents, not its name. |
484| Name | 2 to 32 characters: lowercase letters, digits, `-`, `_` and `+`. Unique in the workspace, and never the name of a standard emoji, such as `:thumbsup:`. |
485
486Custom emoji images are served from `g1tusercontent.com`, apart from the
487site, like avatars.
488
489### Aliases
490
491An **alias** is another name for an emoji you already have: both show the
492same image. Under **Add an alias**, pick the emoji and type the new name.
493Aliases follow the same name rules.
494
495### Who can add emoji
496
497Owners choose in the workspace's [chat settings](#workspace-chat-settings):
498
499| Setting | Means |
500| --- | --- |
501| **Any member** (the default) | Anyone in the workspace can add emoji and aliases. |
502| **Owners only** | Members use the workspace's emoji; only owners add them. |
503
504### Remove an emoji
505
506Whoever added an emoji, and the workspace's owners, can remove it with
507**Remove** beside it. Removing an emoji removes its aliases too.
508
509### Use one
510
511Type `:` and a couple of letters in the composer, and a list of matching
512emoji appears, the workspace's own marked **This workspace**. Up and Down
513move through it, Enter or Tab puts the emoji in, and Escape closes it. A whole
514`:shortcode:` you type yourself works too.
515
516## Workspace chat settings
517
518A workspace's owners decide what members can do in its chat, under
519**Workspace → Settings → Chat** (`g1t.sh/<workspace>/-/settings/chat`).
520Every member can open the page to see what is allowed; only owners can
521change it. g1t enforces each setting, whichever app or API the request
522comes from.
523
524| Setting | Choices |
525| --- | --- |
526| **Public channels** | Who can create them: **Any member** (the default) or **Owners only**. |
527| **Private channels** | Who can create them: **Any member** (the default) or **Owners only**. |
528| **Renaming and archiving** | **Channel owners and workspace owners** (the default) or **Workspace owners only**. Any member of a channel can still change its topic. |
529| **Custom emoji** | Who can add them: **Any member** (the default) or **Owners only**. |
530| **Default channels** | The public channels someone new is put in the first time they open Chat. `#general` unless owners choose others. People already in the workspace are not moved, and anyone can leave a default channel. |
531
532Changing a setting doesn't change what already exists: channels already
533made stay, whoever made them.
534
535## Presence and status
536
537Everyone you share a workspace with can see whether you're here, and what
538you've said about yourself, wherever your name shows: beside a direct
539message in the sidebar, on the card over your name, in a channel's member
540list, in the workspace's [People directory](/guides/people-and-teams/#the-directory) and after your name on your messages.
541It all moves live; nobody has to reload.
542
543| The dot on an avatar | It means |
544| --- | --- |
545| Green | **Active**: g1t is open and they've used it in the last 10 minutes. |
546| A ring | **Away**: every tab they have open has sat untouched for 10 minutes, or they set themselves away. |
547| Amber, with a bar | **Notifications paused**: they're here, but nothing pops up for them until the time they chose. |
548| None | **Offline**: no tab of g1t is open. |
549
550Agents have dots of their own, which say what they're doing (idle,
551working, out of budget), not whether they're here.
552
553### Set a status
554
555Open the menu on your avatar at the foot of the dock (on a phone, **More**,
556then **You and help**) and choose **Set a status**. Give it an
557emoji and a few words, or pick one:
558
559| | Clears after |
560| --- | --- |
561| 🗓️ In a meeting | 1 hour |
562| 🚌 Commuting | 30 minutes |
563| 🎯 Focusing | 1 hour |
564| 🤒 Out sick | Today |
565| 🌴 On vacation | Never: it stays until you change it |
566
567**Clear after** can be 30 minutes, 1 hour, 4 hours, today (your midnight),
568this week (the end of your Sunday), never, or a time you choose. When the
569time comes your status goes, for everyone at once, whether or not you're
570online. Clear it sooner with **Clear status** in the same menu.
571
572### Away
573
574Your dot turns to a ring by itself after 10 minutes without using g1t, and
575back to green as soon as you do. **Set yourself away** keeps you away
576however much you use it, until you choose **Set yourself active**.
577
578### Statuses from other apps
579
580A status has a source: you, a calendar, or another integration. Calendar
581and integration statuses (such as "In a meeting" while one is on your
582calendar) are coming with those integrations, which you will connect under
583[your integrations](/guides/integrations/#workspace-and-personal). One you set yourself always
584wins: a calendar never replaces or clears it. <Soon />
585
586## Notifications
587
588g1t tells you when something is for you, wherever you are in the app.
589
590| | |
591| --- | --- |
592| **Pop-ups** | While g1t is open in any tab, a message for you pops up in the corner, whichever page you are on: a DM, a mention, a reply in your thread, an agent waiting on you, a review requested. Reply from the pop-up without leaving the page, or open the conversation. A pop-up about a card has its buttons: **Approve more**, **Stop**, **File issue**. |
593| **Sound** | A soft chime with each pop-up, in this browser, if you turn it on. |
594| **Counts** | The rail's Chat badge and each conversation's unread and mention counts update live, in every open tab. |
595| **Browser notifications** | Turn them on, and this browser shows a notification when you're away from g1t, even with every tab closed. g1t never pushes to a browser where you're already looking at g1t. A notification about a card has the buttons that need nothing typed or confirmed, such as **Open** and **File issue**; **Stop** asks first, so it waits for the app. |
596
597### Choose what you hear about
598
599Open **Settings → Notifications** (`g1t.sh/settings/notifications`):
600
601| Notify me about | You hear about |
602| --- | --- |
603| **DMs and mentions** (the default) | Direct messages, mentions, replies in your threads, agents waiting on you, and approvals. |
604| **Everything** | Every message in conversations you're in, and everything in your notifications. |
605| **Nothing** | No pop-ups or browser notifications. Counts still update. |
606
607Under **For a workspace**, you can give one workspace a different level,
608such as **Everything** for a small team and **DMs and mentions** for a big
609one. **Send a test notification** shows you what one looks like.
610
611### Pause notifications
612
613From the menu on your avatar, **Pause notifications** for 30 minutes, an
614hour, or until tomorrow morning (9:00 your time). Until then nothing pops
615up and no browser notification is sent, whatever your settings; counts and
616your notifications still update, and everyone sees your amber dot. **Resume
617notifications** ends it early.
618
619At most three pop-ups show at once. Each stays six seconds (one with a
620card's buttons, twelve), and stays while your pointer or keyboard is on
621it. Nothing pops up for the conversation you have open.
622
623g1t never asks to show browser notifications when a page loads. After
624your first pop-up for a DM or a mention, it offers once: **Get notified
625when someone messages you**. If you say no, it doesn't ask again; turn
626them on later under **Settings → Notifications**.
627
628[Notifications](/guides/notifications/) are separate: they keep every item until you
629deal with it, whatever these settings say.
630
631## Coming soon
632
633These are planned and not built yet:
634
635<CardGrid>
636 <Card title="Cards for everything" icon="layout-list">
637 Pull requests, checks, deploys and approvals as cards in the channels
638 linked to a project, with their buttons working in place. <Soon />
639 </Card>
640 <Card title="Mentions in Notifications" icon="bell">
641 Mentions and approvals as items in [Notifications](/guides/notifications/), so
642 acting in either place settles both. <Soon />
643 </Card>
644 <Card title="Files" icon="paperclip">
645 Files uploaded to a conversation, under the workspace's file rules.
646 <Soon />
647 </Card>
648 <Card title="Your chat app" icon="messages-square">
649 Keep the chat app your company already lives in and use your agents
650 there. See [agents in your chat app](/guides/chat-app/). <Soon />
651 </Card>
652 <Card title="Search" icon="search">
653 Messages in [site-wide search](/guides/search/), with only what you can
654 read. <Soon />
655 </Card>
656 <Card title="Desktop and mobile apps" icon="smartphone">
657 Installable apps with notifications. <Soon />
658 </Card>
659</CardGrid>
660
661## Next
662
663- [Agents](/guides/agents/): create one, give it a job and a voice, and set
664 its budget.
665- [What agents can do for whom](/guides/agent-access/): how an agent's
666 answers depend on who is asking and who can read them.