Plan: the inbox, then channels and apps, instead of discussions
People and agents talk in real-time channels (Durable Objects with hibernation), with agents as members, threads tied to issues, pull requests, runs and deploys, and an installable app first, then native desktop and mobile. The inbox comes first as the delivery layer both need.
1 file+32−00/1 viewed
| 989 | 989 | start with the cheapest that is good enough, and escalate to a stronger one | |
| 990 | 990 | when checks fail. | |
| 991 | 991 | ||
| 992 | + | ## Talking: the inbox and channels | |
| 993 | + | ||
| 994 | + | Not a discussions forum. People and agents need one place to talk in real | |
| 995 | + | time, and an app that feels like one on desktop and phone. | |
| 996 | + | ||
| 997 | + | **The inbox comes first.** Everything that needs a person or that they | |
| 998 | + | follow, from people and agents: review requests, agent questions and | |
| 999 | + | handoffs, failures, mentions, deploys. Read and unread, saved, done, | |
| 1000 | + | snoozed; ranked so what an agent is blocked on comes first; email digests | |
| 1001 | + | and push. It is the delivery layer chat needs too (who is told what, read | |
| 1002 | + | state, push), so building it first makes channels cheap. | |
| 1003 | + | ||
| 1004 | + | **Channels** (working name): workspace channels, direct messages and | |
| 1005 | + | threads, live. | |
| 1006 | + | ||
| 1007 | + | - Each channel is a Durable Object holding its WebSocket connections with | |
| 1008 | + | hibernation, so idle channels cost nothing; history in D1, files in R2. | |
| 1009 | + | - Agents are members. `@g1t-agent` in a channel starts work, answers, or | |
| 1010 | + | posts a summary; agents post their questions and handoffs where people | |
| 1011 | + | already are. A thread becomes an issue or an outcome in one action, and | |
| 1012 | + | the agent's progress streams into that thread. | |
| 1013 | + | - Tied to the work: issues, pull requests, runs and deploys each have a | |
| 1014 | + | thread; links unfurl into live cards (checks, agent step, preview). | |
| 1015 | + | What a channel settles can become workspace memory, with its source. | |
| 1016 | + | - Apps: an installable PWA first (desktop and mobile, offline shell, Web | |
| 1017 | + | Push), then native shells on the same API: Tauri for desktop (tray, | |
| 1018 | + | deep links), React Native for iOS and Android (background | |
| 1019 | + | notifications). | |
| 1020 | + | ||
| 1021 | + | GitHub-style Discussions are not planned: channels and threads on the | |
| 1022 | + | work replace them. | |
| 1023 | + | ||
| 992 | 1024 | ## What GitHub ships today, and where g1t differs | |
| 993 | 1025 | ||
| 994 | 1026 | GitHub's Agent HQ and Copilot app give each agent session its own git |