apps/web/app/routes · flagon-io/g1t

notifyMerge branch 'main' into worktree-agent-a654d8ba46392bedd4d ago

repoA repository's settings, security and observability pages fail one part at a time, and never say something false because a read failed. Settings: Add team ("No other team to add" was what a failure said); the default branch's rules (a failure said no rules held for it and anyone could push); General's Branches, Artifacts, Features and Commits sections show Unavailable instead of forms that could save over values never read (Branches and retention used to fail the page); Rules' "what holds for a branch" and Insights. Security: the overview's code scanning, policy and advisories rows say Unavailable instead of guessing "None yet" or "Needs setup", and Open alerts says when code scanning is not in its counts; custom patterns (a failure showed the sales prompt); a secret's validity check (a failure said checks were off); whether reporting is on is unknown, not off. Observability: the overview, open errors ("No open errors in this period"), the g1t.page switch, retention, exports, usage, tokens and a metric's chart each say so in place; the lists use Unavailable. Kept quiet on purpose: the creator's name, the deployments-on preview warning, checks seen for offering CI and in a ruleset's suggestions, a security row's fix status, filter facets (a filter in the address still applies). Checked: apps/web tsc -b; npm test (987, 1 skipped).4d ago

settingsThe app's frame and your own pages fail one part at a time. Root loader: the viewer stays strict; the sidebar's projects, the open counts, Shared with you and the live feed's ticket go through part() and do without quietly, so one of them failing no longer drops the sidebar to its bare form or, for a visitor, takes down every page. A repository's frame: the repository and its project stay strict (404s, renames, transfers); its open counts and the project lookup do without. Profile: activity, workspaces, stars and contributions each say so in place. Notifications, invitations ("No invitations waiting" was what a failure said), pricing's usage and price changes, importing from GitHub on New, and the installations already on GitHub. Settings: account's erasure and deletion check show Unavailable instead of their forms; notifications' email, security and new-repository sections show Unavailable instead of forms that could save over unknown values (the page used to blank entirely), and watched repositories in place; GitHub ("not set up here" was what a failure said); integrations' GitHub link and grants; two-factor's message is Unavailable. Kept strict on purpose: sign-in, registration, invites, OAuth, device, two-factor sign-in and email confirmation, and every page that reads only its subject. Kept quiet on purpose: profile descriptions, notification tab counts, billing on pricing, hasPassword (it only asks for a password, which identity checks anyway), sounds. Checked: apps/web tsc -b; npm test (987, 1 skipped).4d ago

workspaceArchiving, transferring and deleting a project are on its General settings, and "Type … to confirm" reads as one sentence4d ago

auth-github-callback.tsxMerge main (membership, two-factor, GitHub repo roles) into tokens1w ago

auth-github-username.tsxMerge main into rm-agents: mirroring removal, open signups, free-tier limits, the g1t CLI and runner fixes, with the agent removal kept. The CLI's table of operations is regenerated from the API without the agent, customize and AI credit operations; no CLI command used them.1w ago

auth-github.tsstatus.g1t.sh with incident management, invites that land you in the workspace, settings as pages, usage without quotas1w ago

avatar-user.tsPeople wear their own avatars wherever g1t knows them only by name, and a workspace is never shown as a person. The activity feeds, recent changes, home's most active faces, issue and pull request authors, assignees, comments and the audit log drew a person from their username alone, so everyone got their letter avatar instead of the picture they uploaded. An avatar given no picture now draws the letter at once and lays the person's own picture over it once it loads, from /-/avatar/user/<username> (routes/avatar-user.ts): a redirect to the picture on the usercontent origin, or not found, read from identity's people only, so a workspace's icon can never stand in for someone. Kept five minutes, public like the profile. Agents, the product tour's people, "someone" and workspaces' square avatars are never looked up (image null), so an account with the same name never lends them its face.6d ago

confirm-email.tsxPersonal-data erasure has an intake, a staff case with its trail, and cleanup that identity commits with the purge and retries until each service confirms it; one-time-code fields work with password managers and take recovery codes; the Ask panel closes when you follow a link from it. Settings → Account records an erasure request (identity request_erasure / my_erasure, migration 0049), even when a workspace you own alone or billing stands in the way of closing the account; it deletes nothing, keeps the first deadline when asked again, and the deadline is the same day next calendar month, clamped to its last day. sudo → Customers → Privacy lists the cases (the sidebar counts open ones), records a request received elsewhere with its original receipt time (an intake for an open case joins its trail and can only move the deadline earlier), shows each case's trail of intake, reviews, refusal or completion, and refuses completion while the account or any of its cleanup jobs remain or any of the seven evidence areas is empty. Purging an account or a workspace now writes five purge jobs (avatar, Chat, Notify, Artifacts, the lifecycle event) in the same D1 batch as the deletion, guarded like every statement in it, so a restore that won leaves neither; the 15-minute tick runs them, keeps a failure pending with backoff to 16 hours, never stores a response body, and clears a done job's payload. Publishing user.deleted or workspace.deleted is delivery to the bus, not proof its consumers finished. A workspace's jobs carry its members at purge time and its former slugs no live workspace holds. Chat (migration 0006): the person's direct message with g1t goes with its answers and pending job; in shared conversations only the person is shut out and their messages show as ghost, where before the room's clear told every member's tab the conversation was emptied and dropped others' pending answers; a workspace's channels are deleted 500 messages at a time within a budget, answering pending until done; the channels to visit are listed once with the tombstone; tombstones, looked up by key with new indexes, refuse late messages, members, reactions, channels, settings, emoji and meter rows. Notify: an erased feed drops later deliveries quietly instead of throwing; a purged workspace's slug can be made again by the person whose username it is, so its marks are times, not bans: notifications from before the purge are dropped, counts, seeds and visits refused for a day, and its presence room refuses only words said before the purge; the purge reaches identity's members and the room's people under every slug, and clears complete:, forgot: and the workspace's notification level. Artifacts (migration 0010): unshared private folios and their files, versions, search rows and vectors go; authorship (now also cleared_by and repo_spaces.added_by) shows as ghost and mention lists drop the username; a workspace is swept a page at a time and resumes after a failure; full-text rows of a document are deleted by document; an index run that races an erasure writes no full-text row without a chunk row and takes back the vectors it wrote; a room's destroy waits for its index run; ordinary page deletion now destroys the page's live document. Not covered automatically, and listed in docs/operations/privacy-erasure.md as manual review: comment threads inside shared documents' live state and version snapshots, private-space pages, rooms of pages deleted before this, folio trash past 200 rooms, earlier folios' version and upload blobs, former members' and outsiders' notifications, backups. One-time codes: the sign-in's second step, two-factor settings and email confirmation share otpInputProps (lib/otp.ts): a stable id and label, autocomplete one-time-code, no password-manager ignore attributes; the sign-in field takes either kind of code at recovery-code length whichever is chosen, and Use a recovery code switches the keyboard. The Ask panel closes on every completed navigation (location.key), including its direct-message link and citations to the page you are on and back or forward; links opened in another tab and revalidation leave it open. The Privacy Policy distinguishes closure from erasure; the authentication guide says how to ask and how recovery codes are entered; the services page lists identity's new CHAT, NOTIFY and ARTIFACTS bindings. Deploy migrations first, then chat, notify and artifacts before identity, then web and sudo. Checked: cargo test -p g1t-identity --lib (175) and its wasm32 check; node --test conformance/erasure.test.mjs (11, new: a shared channel's room shuts out only the erased member, a large channel deleted in chunks with late writes refused, a reclaimed slug keeps new notifications and presence, vectors taken back after a racing erasure, an upload sweep resuming after a failure, late deliveries dropped quietly); artifacts' 126 tests and typecheck, notify's 49 and typecheck, chat's typecheck; the site's tsc -b --force, 926 tests (new: otp) and a production build; sudo's typecheck, 156 tests and build; contracts' 48; the deploy tool's tests (the one failure is services/runner/base.json, from separate uncommitted runner work); the docs build.5d ago

desktop-runner.tsMerge the desktop app's runner: it starts with the app for the signed-in person, sandboxed by default and running nothing where no sandbox is available yet, registers through the site, keeps itself up to date, and says everywhere what it is doing, why it is not, and how to fix it.1w ago

device.tsxThe site is built from its shared components: one Button with its variants and sizes, one Badge, Card for every panel, Alert for notices, Kbd for keys, Table for the security tables, and Avatar, Command, Progress, ScrollArea, ToggleGroup, Collapsible and Accordion in the kit; raw buttons, hand-drawn cards and pills and per-file button class lists are gone, outline buttons stand the same height as filled ones, and the phone's Ask g1t loses its tile. Every page was compared pixel by pixel before and after.1w ago

download.tsxThe download page says every build is unsigned while g1t is in alpha. A notice under the platform switcher says the desktop app, the Android app, the runner and the CLI aren't code-signed yet, so the system warns before opening them, with what to choose on the platform shown (Windows: More info, Run anyway; macOS: System Settings, Privacy & Security, Open Anyway; Linux: an unsigned package, an AppImage made executable; Android: Play Protect's More details, Install anyway). The macOS-only question becomes "Why does my system warn me before opening it?" covering all four, and the Android app is no longer said to be signed by g1t. The desktop guide gains "Unsigned during the alpha" in place of the old right-click-Open note, and the phone app guide says what to do when Play Protect warns.6d ago

downloads-runner.tsThe phone app with your own g1t, on g1t.sh/download until Google Play, and Node 24 (#5 )1w ago

explore.tsxExplore shows each repository's project's description, read from projects as the page renders: flagon-io/demo's card said "No description." while its project says "Countdown website to Cloudflare Connect SF 2026". Explore read search's own copy, kept from project.updated, which a new repository's description could miss. The workspace's Repositories, a repository's forks and starred lists already read projects.descriptions; Explore now does too, by the repository id search now gives each card (ExploreRepo.id). Until search is deployed with ids, the card keeps search's copy. Checked: apps/web tsc -b; search cargo check (wasm32).4d ago

forgot.tsxThe site is built from its shared components: one Button with its variants and sizes, one Badge, Card for every panel, Alert for notices, Kbd for keys, Table for the security tables, and Avatar, Command, Progress, ScrollArea, ToggleGroup, Collapsible and Accordion in the kit; raw buttons, hand-drawn cards and pills and per-file button class lists are gone, outline buttons stand the same height as filled ones, and the phone's Ask g1t loses its tile. Every page was compared pixel by pixel before and after.1w ago

github-install.tsConnecting GitHub to a workspace is one click and one trip to GitHub. A workspace owner's Connect GitHub on Import from GitHub links their GitHub account on the way if it is not linked yet and comes straight back to carry on: an installation they already have on GitHub and the workspace lacks is added rather than installed again (with several, they choose), and only with none are they sent to install the app; GitHub then returns them to the import page with the account connected. Before, linking and installing were separate chores (link, come back, install), Settings -> GitHub stopped at "Linked" with nowhere to go, and an app already on the account was "installed" again through GitHub's settings page. When GitHub returns after an installation that did not start from g1t, an unlinked account is linked on the way instead of showing an error with a button, and someone who owns one workspace has it added there without being asked which. Choose repositories on GitHub opens in the same tab, since GitHub brings you back after saving; Add a GitHub account still always installs on another account; Settings -> GitHub points to Import from GitHub once linked. A link that does not take shows the page instead of going round again. The GitHub guide describes the one-step flow. (The app's Setup URL was empty on GitHub, which left people there after installing; it is now set to /integrations/github/setup.) Checked: the site's typecheck (tsc -b --force), its 911 tests (new: what Connect GitHub does next), a production build and the deploy tool's 92 tests.5d ago

github-setup.tsxConnecting GitHub to a workspace is one click and one trip to GitHub. A workspace owner's Connect GitHub on Import from GitHub links their GitHub account on the way if it is not linked yet and comes straight back to carry on: an installation they already have on GitHub and the workspace lacks is added rather than installed again (with several, they choose), and only with none are they sent to install the app; GitHub then returns them to the import page with the account connected. Before, linking and installing were separate chores (link, come back, install), Settings -> GitHub stopped at "Linked" with nowhere to go, and an app already on the account was "installed" again through GitHub's settings page. When GitHub returns after an installation that did not start from g1t, an unlinked account is linked on the way instead of showing an error with a button, and someone who owns one workspace has it added there without being asked which. Choose repositories on GitHub opens in the same tab, since GitHub brings you back after saving; Add a GitHub account still always installs on another account; Settings -> GitHub points to Import from GitHub once linked. A link that does not take shows the page instead of going round again. The GitHub guide describes the one-step flow. (The app's Setup URL was empty on GitHub, which left people there after installing; it is now set to /integrations/github/setup.) Checked: the site's typecheck (tsc -b --force), its 911 tests (new: what Connect GitHub does next), a production build and the deploy tool's 92 tests.5d ago

home.tsxMerge branch 'main' into worktree-agent-a654d8ba46392bedd4d ago

hovercard-user.tsMerge commit authors and hovercards: commits show their accounts, every name opens a card (repos 0016)1w ago

inbox-json.tsInbox: a bell in the top bar opens it beside the page, and /inbox holds it all1w ago

inbox-moved.tsMerge branch 'worktree-agent-ac2922d9eb84a7909'4d ago

install-script.tsMerge main into rm-agents: mirroring removal, open signups, free-tier limits, the g1t CLI and runner fixes, with the agent removal kept. The CLI's table of operations is regenerated from the API without the agent, customize and AI credit operations; no CLI command used them.1w ago

invitations.tsxThe app's frame and your own pages fail one part at a time. Root loader: the viewer stays strict; the sidebar's projects, the open counts, Shared with you and the live feed's ticket go through part() and do without quietly, so one of them failing no longer drops the sidebar to its bare form or, for a visitor, takes down every page. A repository's frame: the repository and its project stay strict (404s, renames, transfers); its open counts and the project lookup do without. Profile: activity, workspaces, stars and contributions each say so in place. Notifications, invitations ("No invitations waiting" was what a failure said), pricing's usage and price changes, importing from GitHub on New, and the installations already on GitHub. Settings: account's erasure and deletion check show Unavailable instead of their forms; notifications' email, security and new-repository sections show Unavailable instead of forms that could save over unknown values (the page used to blank entirely), and watched repositories in place; GitHub ("not set up here" was what a failure said); integrations' GitHub link and grants; two-factor's message is Unavailable. Kept strict on purpose: sign-in, registration, invites, OAuth, device, two-factor sign-in and email confirmation, and every page that reads only its subject. Kept quiet on purpose: profile descriptions, notification tab counts, billing on pricing, hasPassword (it only asks for a password, which identity checks anyway), sounds. Checked: apps/web tsc -b; npm test (987, 1 skipped).4d ago

invite.tsxMerge main into rm-agents: mirroring removal, open signups, free-tier limits, the g1t CLI and runner fixes, with the agent removal kept. The CLI's table of operations is regenerated from the API without the agent, customize and AI credit operations; no CLI command used them.1w ago

login-two-factor.tsxPersonal-data erasure has an intake, a staff case with its trail, and cleanup that identity commits with the purge and retries until each service confirms it; one-time-code fields work with password managers and take recovery codes; the Ask panel closes when you follow a link from it. Settings → Account records an erasure request (identity request_erasure / my_erasure, migration 0049), even when a workspace you own alone or billing stands in the way of closing the account; it deletes nothing, keeps the first deadline when asked again, and the deadline is the same day next calendar month, clamped to its last day. sudo → Customers → Privacy lists the cases (the sidebar counts open ones), records a request received elsewhere with its original receipt time (an intake for an open case joins its trail and can only move the deadline earlier), shows each case's trail of intake, reviews, refusal or completion, and refuses completion while the account or any of its cleanup jobs remain or any of the seven evidence areas is empty. Purging an account or a workspace now writes five purge jobs (avatar, Chat, Notify, Artifacts, the lifecycle event) in the same D1 batch as the deletion, guarded like every statement in it, so a restore that won leaves neither; the 15-minute tick runs them, keeps a failure pending with backoff to 16 hours, never stores a response body, and clears a done job's payload. Publishing user.deleted or workspace.deleted is delivery to the bus, not proof its consumers finished. A workspace's jobs carry its members at purge time and its former slugs no live workspace holds. Chat (migration 0006): the person's direct message with g1t goes with its answers and pending job; in shared conversations only the person is shut out and their messages show as ghost, where before the room's clear told every member's tab the conversation was emptied and dropped others' pending answers; a workspace's channels are deleted 500 messages at a time within a budget, answering pending until done; the channels to visit are listed once with the tombstone; tombstones, looked up by key with new indexes, refuse late messages, members, reactions, channels, settings, emoji and meter rows. Notify: an erased feed drops later deliveries quietly instead of throwing; a purged workspace's slug can be made again by the person whose username it is, so its marks are times, not bans: notifications from before the purge are dropped, counts, seeds and visits refused for a day, and its presence room refuses only words said before the purge; the purge reaches identity's members and the room's people under every slug, and clears complete:, forgot: and the workspace's notification level. Artifacts (migration 0010): unshared private folios and their files, versions, search rows and vectors go; authorship (now also cleared_by and repo_spaces.added_by) shows as ghost and mention lists drop the username; a workspace is swept a page at a time and resumes after a failure; full-text rows of a document are deleted by document; an index run that races an erasure writes no full-text row without a chunk row and takes back the vectors it wrote; a room's destroy waits for its index run; ordinary page deletion now destroys the page's live document. Not covered automatically, and listed in docs/operations/privacy-erasure.md as manual review: comment threads inside shared documents' live state and version snapshots, private-space pages, rooms of pages deleted before this, folio trash past 200 rooms, earlier folios' version and upload blobs, former members' and outsiders' notifications, backups. One-time codes: the sign-in's second step, two-factor settings and email confirmation share otpInputProps (lib/otp.ts): a stable id and label, autocomplete one-time-code, no password-manager ignore attributes; the sign-in field takes either kind of code at recovery-code length whichever is chosen, and Use a recovery code switches the keyboard. The Ask panel closes on every completed navigation (location.key), including its direct-message link and citations to the page you are on and back or forward; links opened in another tab and revalidation leave it open. The Privacy Policy distinguishes closure from erasure; the authentication guide says how to ask and how recovery codes are entered; the services page lists identity's new CHAT, NOTIFY and ARTIFACTS bindings. Deploy migrations first, then chat, notify and artifacts before identity, then web and sudo. Checked: cargo test -p g1t-identity --lib (175) and its wasm32 check; node --test conformance/erasure.test.mjs (11, new: a shared channel's room shuts out only the erased member, a large channel deleted in chunks with late writes refused, a reclaimed slug keeps new notifications and presence, vectors taken back after a racing erasure, an upload sweep resuming after a failure, late deliveries dropped quietly); artifacts' 126 tests and typecheck, notify's 49 and typecheck, chat's typecheck; the site's tsc -b --force, 926 tests (new: otp) and a production build; sudo's typecheck, 156 tests and build; contracts' 48; the deploy tool's tests (the one failure is services/runner/base.json, from separate uncommitted runner work); the docs build.5d ago

login.tsxg1t 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.1w ago

logout.tsxTeam plan, an open-source pool, monthly trials and honest metering; the sidebar for everyone; a workspace that stays put1w ago

new-github.tsxThe app's frame and your own pages fail one part at a time. Root loader: the viewer stays strict; the sidebar's projects, the open counts, Shared with you and the live feed's ticket go through part() and do without quietly, so one of them failing no longer drops the sidebar to its bare form or, for a visitor, takes down every page. A repository's frame: the repository and its project stay strict (404s, renames, transfers); its open counts and the project lookup do without. Profile: activity, workspaces, stars and contributions each say so in place. Notifications, invitations ("No invitations waiting" was what a failure said), pricing's usage and price changes, importing from GitHub on New, and the installations already on GitHub. Settings: account's erasure and deletion check show Unavailable instead of their forms; notifications' email, security and new-repository sections show Unavailable instead of forms that could save over unknown values (the page used to blank entirely), and watched repositories in place; GitHub ("not set up here" was what a failure said); integrations' GitHub link and grants; two-factor's message is Unavailable. Kept strict on purpose: sign-in, registration, invites, OAuth, device, two-factor sign-in and email confirmation, and every page that reads only its subject. Kept quiet on purpose: profile descriptions, notification tab counts, billing on pricing, hasPassword (it only asks for a password, which identity checks anyway), sounds. Checked: apps/web tsc -b; npm test (987, 1 skipped).4d ago

new.tsxThe app's frame and your own pages fail one part at a time. Root loader: the viewer stays strict; the sidebar's projects, the open counts, Shared with you and the live feed's ticket go through part() and do without quietly, so one of them failing no longer drops the sidebar to its bare form or, for a visitor, takes down every page. A repository's frame: the repository and its project stay strict (404s, renames, transfers); its open counts and the project lookup do without. Profile: activity, workspaces, stars and contributions each say so in place. Notifications, invitations ("No invitations waiting" was what a failure said), pricing's usage and price changes, importing from GitHub on New, and the installations already on GitHub. Settings: account's erasure and deletion check show Unavailable instead of their forms; notifications' email, security and new-repository sections show Unavailable instead of forms that could save over unknown values (the page used to blank entirely), and watched repositories in place; GitHub ("not set up here" was what a failure said); integrations' GitHub link and grants; two-factor's message is Unavailable. Kept strict on purpose: sign-in, registration, invites, OAuth, device, two-factor sign-in and email confirmation, and every page that reads only its subject. Kept quiet on purpose: profile descriptions, notification tab counts, billing on pricing, hasPassword (it only asks for a password, which identity checks anyway), sounds. Checked: apps/web tsc -b; npm test (987, 1 skipped).4d ago

not-found.tsxMerge branch 'worktree-agent-a8385d293d42c913a'1w ago

notifications.tsxThe app's frame and your own pages fail one part at a time. Root loader: the viewer stays strict; the sidebar's projects, the open counts, Shared with you and the live feed's ticket go through part() and do without quietly, so one of them failing no longer drops the sidebar to its bare form or, for a visitor, takes down every page. A repository's frame: the repository and its project stay strict (404s, renames, transfers); its open counts and the project lookup do without. Profile: activity, workspaces, stars and contributions each say so in place. Notifications, invitations ("No invitations waiting" was what a failure said), pricing's usage and price changes, importing from GitHub on New, and the installations already on GitHub. Settings: account's erasure and deletion check show Unavailable instead of their forms; notifications' email, security and new-repository sections show Unavailable instead of forms that could save over unknown values (the page used to blank entirely), and watched repositories in place; GitHub ("not set up here" was what a failure said); integrations' GitHub link and grants; two-factor's message is Unavailable. Kept strict on purpose: sign-in, registration, invites, OAuth, device, two-factor sign-in and email confirmation, and every page that reads only its subject. Kept quiet on purpose: profile descriptions, notification tab counts, billing on pricing, hasPassword (it only asks for a password, which identity checks anyway), sounds. Checked: apps/web tsc -b; npm test (987, 1 skipped).4d ago

oauth-authorize.tsxThe site is built from its shared components: one Button with its variants and sizes, one Badge, Card for every panel, Alert for notices, Kbd for keys, Table for the security tables, and Avatar, Command, Progress, ScrollArea, ToggleGroup, Collapsible and Accordion in the kit; raw buttons, hand-drawn cards and pills and per-file button class lists are gone, outline buttons stand the same height as filled ones, and the phone's Ask g1t loses its tile. Every page was compared pixel by pixel before and after.1w ago

page-boundary.tsxA part of a page that fails stays a part: a card that breaks while drawing says so in its place, and a page that fails shows its error inside its repository's, workspace's or settings' frame, not over the whole app. Before, the root route was the only error boundary, so anything failing on any page replaced everything below the app shell, the repository's header and tabs included. Cards: Boundary (components/boundary.tsx) catches what breaks while drawing and shows Unavailable ("X could not be loaded just now") in its place, drawing again on the next refresh or navigation; every Panel wraps its contents in one. Data: lib/partial.server.ts soft() is the loader side, for a part beside what the page is about: null when it fails, which the part shows as Unavailable. Pages: routes.ts wraps the pages of a repository, a workspace and your settings in a pathless route (routes/page-boundary.tsx) whose boundary renders inside the layout's Outlet (a layout's own boundary would replace the layout too). Its error view is the root's, shared as RouteError (components/route-error.tsx): the stale-build reload, the self-healing "Can't reach g1t", the 404 page and developer details, now with Try again; contained, it says the rest of g1t is fine. The root keeps it as the last resort. Checked: apps/web tsc -b (with react-router typegen); npm test (986).4d ago

people-json.tsMerge workspace invitations: nobody joins a workspace without saying yes, people are found by username, your own invites can bring someone in, and nobody is left without a workspace (identity 0040)1w ago

policies.tsxThe policies no longer promise an email about changes either. Until they're finalized, a change takes effect when it's posted on the policies page and people are asked to check it from time to time; the Terms (section 17), the Privacy Policy, the policies page and today's history entry say so. The price-change notices in the Terms stay as they were.4d ago

policy.tsxThe policies say they are drafts: the policies index and every policy page open with a note that they are still being written and may change before g1t's general launch, with the address for questions. One flag in legal.ts, POLICIES_DRAFT, takes the note down everywhere.6d ago

pricing.tsxThe app's frame and your own pages fail one part at a time. Root loader: the viewer stays strict; the sidebar's projects, the open counts, Shared with you and the live feed's ticket go through part() and do without quietly, so one of them failing no longer drops the sidebar to its bare form or, for a visitor, takes down every page. A repository's frame: the repository and its project stay strict (404s, renames, transfers); its open counts and the project lookup do without. Profile: activity, workspaces, stars and contributions each say so in place. Notifications, invitations ("No invitations waiting" was what a failure said), pricing's usage and price changes, importing from GitHub on New, and the installations already on GitHub. Settings: account's erasure and deletion check show Unavailable instead of their forms; notifications' email, security and new-repository sections show Unavailable instead of forms that could save over unknown values (the page used to blank entirely), and watched repositories in place; GitHub ("not set up here" was what a failure said); integrations' GitHub link and grants; two-factor's message is Unavailable. Kept strict on purpose: sign-in, registration, invites, OAuth, device, two-factor sign-in and email confirmation, and every page that reads only its subject. Kept quiet on purpose: profile descriptions, notification tab counts, billing on pricing, hasPassword (it only asks for a password, which identity checks anyway), sounds. Checked: apps/web tsc -b; npm test (987, 1 skipped).4d ago

register.tsxMerge main into rm-agents: mirroring removal, open signups, free-tier limits, the g1t CLI and runner fixes, with the agent removal kept. The CLI's table of operations is regenerated from the API without the agent, customize and AI credit operations; no CLI command used them.1w ago

reset.tsxMerge branch 'worktree-agent-a985c01f43538af01'1w ago

robots-txt.tsMerge remote-tracking branch 'g1t/main' into HEAD4d ago

search-json.tsSearch across all of g1t, Explore, and a command palette2w ago

search.tsxThe site is built from its shared components: one Button with its variants and sizes, one Badge, Card for every panel, Alert for notices, Kbd for keys, Table for the security tables, and Avatar, Command, Progress, ScrollArea, ToggleGroup, Collapsible and Accordion in the kit; raw buttons, hand-drawn cards and pills and per-file button class lists are gone, outline buttons stand the same height as filled ones, and the phone's Ask g1t loses its tile. Every page was compared pixel by pixel before and after.1w ago

security-txt.tsInvite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look1w ago

security.tsxThe site no longer has g1t's own agents. g1t is where the coding agents you already use do their work, so the Agents mode is gone from the rail, with every page under /<workspace>/-/agents: personas, faces, skills, abilities, routines, computers, sessions and agent spend. Customize (skills, connectors, plugins, marketplaces), the context hub, model providers, the AI Gateway page, the Spend page and pill, Ask g1t, and the repository's Agents, Plans and agent settings pages go too, and their addresses now answer 404.1w ago

settings-menu-json.tsMerge branch 'worktree-agent-a6da31375506fc440'6d ago

sitemap-xml.tsMerge branch 'main' into worktree-agent-a654d8ba46392bedd4d ago

status-json.tsstatus.g1t.sh with incident management, invites that land you in the workspace, settings as pages, usage without quotas1w ago

status.tsxstatus.g1t.sh with incident management, invites that land you in the workspace, settings as pages, usage without quotas1w ago

support.tsxThe site no longer has g1t's own agents. g1t is where the coding agents you already use do their work, so the Agents mode is gone from the rail, with every page under /<workspace>/-/agents: personas, faces, skills, abilities, routines, computers, sessions and agent spend. Customize (skills, connectors, plugins, marketplaces), the context hub, model providers, the AI Gateway page, the Spend page and pill, Ask g1t, and the repository's Agents, Plans and agent settings pages go too, and their addresses now answer 404.1w ago

user.tsxThe app's frame and your own pages fail one part at a time. Root loader: the viewer stays strict; the sidebar's projects, the open counts, Shared with you and the live feed's ticket go through part() and do without quietly, so one of them failing no longer drops the sidebar to its bare form or, for a visitor, takes down every page. A repository's frame: the repository and its project stay strict (404s, renames, transfers); its open counts and the project lookup do without. Profile: activity, workspaces, stars and contributions each say so in place. Notifications, invitations ("No invitations waiting" was what a failure said), pricing's usage and price changes, importing from GitHub on New, and the installations already on GitHub. Settings: account's erasure and deletion check show Unavailable instead of their forms; notifications' email, security and new-repository sections show Unavailable instead of forms that could save over unknown values (the page used to blank entirely), and watched repositories in place; GitHub ("not set up here" was what a failure said); integrations' GitHub link and grants; two-factor's message is Unavailable. Kept strict on purpose: sign-in, registration, invites, OAuth, device, two-factor sign-in and email confirmation, and every page that reads only its subject. Kept quiet on purpose: profile descriptions, notification tab counts, billing on pricing, hasPassword (it only asks for a password, which identity checks anyway), sounds. Checked: apps/web tsc -b; npm test (987, 1 skipped).4d ago

verify.tsxThe site is built from its shared components: one Button with its variants and sizes, one Badge, Card for every panel, Alert for notices, Kbd for keys, Table for the security tables, and Avatar, Command, Progress, ScrollArea, ToggleGroup, Collapsible and Accordion in the kit; raw buttons, hand-drawn cards and pills and per-file button class lists are gone, outline buttons stand the same height as filled ones, and the phone's Ask g1t loses its tile. Every page was compared pixel by pixel before and after.1w ago

well-known-g1t.tsThe phone app with your own g1t, on g1t.sh/download until Google Play, and Node 24 (#5 )1w ago