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

ai-elementsg1t coordinates the work and the person's own sessions do it: Ask g1t reads g1t with the same tools any agent gets, answers in one conversation shared with the @g1t direct message in Chat, and hands work to sessions in the person's own harness, whose subagents g1t records, ties to issues and pull requests, and lets see each other.3d ago

chatPublic channels come first in the chat sidebar: above Pinned and the workspace's own Channels, so what's open to anyone on g1t is the first thing in the list. Checked: apps/web tsc -b.yesterday

emojiPeople 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.4d ago

foliosPeople 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.4d ago

notificationsPeople 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.4d ago

uiSix-digit codes are typed into six boxes: the sign-in's second step, turning two-factor on or off in settings, and confirming an email address. It is shadcn's Input OTP (components/ui/input-otp.tsx, on input-otp 1.4.2) in g1t's tokens: two groups of three with a rule between, the current box ringed in lavender with a blinking caret (still under reduced motion), every box red when the code was refused. One real input sits under the boxes with the field's id, name="code" and autocomplete="one-time-code", so password managers and phones' code suggestions fill it and the form posts what it did before. A pasted "123 456" or "123-456" lands as six digits. On sign-in and email confirmation the form is sent as soon as the sixth digit is in, and a refused code is cleared and the boxes focused for the next. Where a recovery code is also taken (signing in, turning two-factor off), "Use a recovery code" switches to the text field, and a recovery code pasted into the boxes switches by itself with the code carried across, so one is never cut to digits (lib/otp.ts looksLikeRecoveryCode, codeDigits). components/one-time-code.tsx holds CodeSlots and TwoFactorCodeField. Checked: apps/web tsc -b and npm test (993; new: pasted codes and telling a recovery code apart; the confirm page's field test reads the boxes), and the fields rendered alone in headless Chrome driven over CDP: focus on load, typing 123456 submitted 123456, pasting "987 654" gave 987654 and submitted, pasting k7m2q-9xw4d into the boxes moved it whole to the Recovery code field. Not tried with a real password manager or on a phone.yesterday

access.tsxPeople 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.4d ago

account-settings.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.6d ago

actions.tsxMerge remote-tracking branch 'origin/claude/cool-newton-7nm8r9'4d ago

add-ci.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.6d ago

agent-avatar.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.4d ago

agent-setup.tsxPeople 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.4d ago

analytics-consent.tsxPeople 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.4d ago

apps.tsxRoutines has its place in the app, every control off: a mode of its own in the rail after Artifacts (for every member, not only those with Code), in the phone's More sheet and the command palette, at /<workspace>/-/routines, full width like Home and Apps. A routine is standing work for @g1t, and not only about code: say what, say when (a schedule, once, when something happens, by hand), say where it lands (your DM, a channel, an artifact, a pull request), and whose it is (yours, run as you; or the workspace's, kept by a team). The page draws all of it and none of it can be used: the composer is a disabled fieldset, Yours shows an empty list and the workspace's and Runs tabs are disabled, and the starting points (Keep up, Team, Code, Watch) cannot be picked. A notice says Routines are not on yet. Nothing is read or saved; the loader only checks membership. Checked: apps/web npm run typecheck, node --test app/lib/workspace-nav.test.ts and app/lib/apps.test.ts (19; new: /-/routines is the routines mode), and the page rendered alone with mock data in headless Chrome at 1280 and 390 wide. The rail, the More sheet and the palette were not looked at in a browser.yesterday

art.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.4d ago

ask-button.tsxg1t-runner is 0.3.5 and the desktop app 0.3.9: guided runner setup (#50 ).yesterday

ask-composer.tsxHome opens with an Ask box (#51 ): "What are we building today?" over a box that asks g1t, with starters (what changed since I was last here, what needs me first, what shipped today, who's working on what), in place of "Welcome back". Summarize, beside the span switch on "Since you were last here", asks g1t what changed in that span in plain English, from its start in the viewer's zone; Explain on each Landed row asks what that one change did, why, and whether it is live. Each hands its question to the top bar's Ask (askG1t, a g1t:ask window event), which opens and sends it, or leaves it in the box when Ask is not set up or an answer is still coming. Checked: the site's typecheck and tests (956), and the real Home route and Ask panel rendered with mocked data at desktop and phone width, dark and light, clicking the box, a starter, Summarize and Explain.yesterday

ask-steps.tsxAsk's card remembers what it did, step by step, on the answer that proposed it (#53 ): the card kept its progress only in the page that clicked it, so back in Chat the same answer offered Start session again, and a second click on the new-repository card opened a second issue and started a second session on the same empty repository (flagon-io/ask-hello-test got #1 and #2 , each with a session racing to push the first version). What a click does is now kept on the @g1t answer as it happens, in a proposal_state step beside the proposal: chat's new g1t_proposal merges it in (the viewer's own direct message with g1t only, known fields only) and tells the room, so every open copy of the answer updates. The card starts from it wherever the answer is read: Created with the repository, Live once the first version is pushed at with the address or Not deployed: with why, and Started with its links. Another click carries on from there rather than over: a session already started is shown, not started again; a repository already made, its deployments and the issue already opened are used; and while a click is still starting it (90 seconds at most), another says it's already starting. A failed step clears that hold so a retry works. Ask's steps also stop marking a read that found nothing as not read: checking that a new repository's name is free answers "not found", which showed as 1 not read on every new-repository answer.yesterday

attempts.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.6d ago

audit.tsxPeople 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.4d ago

auth-card.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.6d ago

avatar-field.tsxPeople 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.4d ago

base-branch.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.6d ago

billing-settings.tsxMerge main into project-descriptions2d ago

billing.tsxFixes from reviewing the per-card commits. An issue's Save assignees cleared every assignee when the workspace's people could not be read (74236dee showed Unavailable in place of the picker but kept the button, so the form sent no one): the picker stays, holding who is assigned now, with the note above it, as the pull request page already did. A large repository's About sidebar said its releases, contributors, languages and packages could not be loaded whenever they took longer than the page waits (4 s), which is slow, not failed: it is left out quietly again, as before, and only a service that did not answer or answered with an error says so. Raise my limit and Tell g1t offered their forms when the requests could not be read, so a second request could go while one was open (not new: the page read none before): each card now takes the failed requests and shows Unavailable under its heading instead of its form. Checked: apps/web tsc -b; npm test (987).yesterday

blame-view.tsxMerge branch 'worktree-agent-ac2922d9eb84a7909'yesterday

boundary.tsxEach part of a page can say it failed, in its own place: part() (lib/partial.ts, replacing f1687c9a's soft()) reads a part beside what a page is about and keeps a failure (a service that did not answer, or answered with a 5xx) as { failed: true, what } instead of throwing, so the page can tell a part that failed from one with nothing to show and put Unavailable beside it, the way a form puts an error beside its field. A refusal or a 404 is still an answer. orElse() is for a part that can quietly do without. Unavailable has a compact one-line form for a sidebar card or a count's place. Checked: apps/web tsc -b; node --test app/lib/partial.test.ts.yesterday

branch-list.tsxA commit's hover hint is its subject, cut on a word past 160 characters (commitHint, lib/commit-message.ts): on flagon-io/g1t's Files list a commit whose subject runs to a paragraph filled the screen with its tooltip. The Files list, Branches, Compare and Tags each use it; Branches, Compare and Tags showed the whole message, body and trailers too. The commit's page has it all. Checked: apps/web tsc -b; npm test (988; new: a commit's hint).yesterday

branches.tsxMerge branch 'worktree-agent-a7823ad540eb3433b'3d ago

checks.tsxMerge branch 'worktree-agent-ad7c6d88d93adc817'1w ago

clone-box.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.4d ago

code-lines.tsxMerge 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)1w ago

codeowners.tsxMerge commit '9232a85b'2d ago

coding-agent.tsxMerge remote-tracking branch 'origin/claude/cool-newton-7nm8r9' into claude/cool-newton-7nm8r94d ago

command-palette-dialog.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.6d ago

command-palette.tsxThe left-hand navigation takes less room and reads at a glance. The dock becomes a rail: a 56-pixel column of icons with the g1t mark on top, the current app marked by a filled square, hover hints naming each with its shortcut, the apps you pinned in a scrolling band, and Apps, People, Workspace and your account at the foot. Each mode's sidebar sits flush against it, 240 pixels wide, opening on Search or jump to and listing its groups under small labels in 36-pixel rows; Ctrl B hides it and the page grows into the room. Every mode's list is built on the shadcn Sidebar now in the kit, so Workspace, Code, People, Notifications, account settings, Chat, Artifacts and Agents all share one frame; the phone keeps its bottom bar and drawer. The workspaces guide describes the rail, the sidebar and the page.6d ago

commit-checks.tsxPeople 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.4d ago

commit-message.tsxMerge main into project-descriptions2d ago

commit-person.tsxMerge remote-tracking branch 'origin/claude/cool-newton-7nm8r9' into claude/cool-newton-7nm8r94d ago

confirm-name.tsxArchiving, transferring and deleting a project are on its General settings, and "Type … to confirm" reads as one sentenceyesterday

connection-toast.tsxA page left open survives a moment without a network: sitting on /flagon-io/g1t/settings/repository, one background refresh met "TypeError: Failed to fetch" (Wi-Fi changing, a laptop waking, a connection cut during a deploy) and the root error page replaced the whole page, in the browser and the desktop app alike. The router's own reads (its .data requests and /__manifest, GET and same-origin only) are now asked again when they get no answer at all (lib/resilient-fetch.ts, installed in entry.client.tsx): after 0.25 s, 0.5 s, 1 s, 2 s, 4 s, then every 5 s, at once when the browser says it is back online. A refresh of the page already showing keeps trying for as long as it takes, and the page stays as it is meanwhile; a click elsewhere cancels it. From the second miss a toast says "Can't reach g1t. Trying again…" and goes once a read arrives (components/connection-toast.tsx). A read for another page (a click) tries for 45 s, under the stuck-navigation rescue's 75 s, then reaches the error page, which for a network failure now says "Can't reach g1t" and loads the page again by itself (3 s, 6 s, 12 s, then every 30 s, and at once on coming back online or into view; lib/reconnect.ts) instead of showing an error with a link home. Writes are never sent again: one that failed may have arrived. A stale build's "Failed to fetch dynamically imported module" is not a network failure and still reloads the page as before. Checked: apps/web tsc -b; npm test (982; new: each browser's no-answer message and what is not one, which requests are retried, a refresh told from a navigation, the delays).yesterday

connectors.tsxA workspace's AI is its own setting, not an integration. AI providers and what Ask answers with were connections like Sentry's or Linear's: rows of `connections`, cards in the Integrations directory, `provider` values of the integration operations. Integrations are becoming a directory others publish to; a workspace's AI is a base setting g1t looks after itself. Contracts: `g1t_contracts::ai` (and packages/contracts ai.ts) has AiProvider (the 14), AiGroup (labs, platforms, self_hosted), AiConfig, AiConnection and their methods' arguments, and the Ask types moved there; AskSetup names the provider by `provider_id` and `provider_name` (were connection_id, connection_name). `integrations::Provider` is sentry, datadog, webhook, jira and linear; ProviderKind loses Models, ConnectionConfig its base_url, auth_header and model, Connection its models. Storage: integrations migration 0011 makes `ai_providers` and `ai_routes`, moves the AI rows out of `connections` with their ids (sealed keys are bound to the id, and managed_agents and agent_runs keep finding them), keeps Ask's route and drops `model_routes`; renaming and deleting a workspace cover both tables. The service keeps them in src/ai.rs with methods of their own (ai_list, ai_add, ai_update, ai_remove, ai_test, ask_settings, set_ask_settings, ask); a provider's key is checked when added and on each test; removing one turns Ask off when it answered with it and forgets its managed agent. Sessions on issues find the workspace's Anthropic provider there. API: list_ai_providers, add_ai_provider, update_ai_provider, remove_ai_provider, test_ai_provider (/workspaces/{workspace}/ai/providers[/{id}[/test]]), get_ask_settings and set_ask_settings (/workspaces/{workspace}/ai/ask), under the OpenAPI tag AI; reading takes workspace:read, changing workspace:admin and an owner's own token; the integration operations take only integration providers. MCP: a tool `ai` (list_providers, add_provider, update_provider, remove_provider, test_provider, get_ask, set_ask). The CLI's operation table and command reference are regenerated. Site: AI at /<workspace>/-/ai (the sidebar's AI → Models, the command palette's AI models) holds Ask g1t, the providers and Add a provider, grouped Frontier labs, Model platforms, Self-hosted or your own gateway; AI providers are no longer in the Integrations directory or Apps, and the integrations pages are alerts and trackers only; -/integrations/models and ?add=<an AI provider> lead to -/ai. Ask's settings link, and @g1t's "not set up yet" in Chat, point there. Docs: the AI providers guide (with its API), and the integrations, Ask, sessions, CLI, plugin and MCP pages say so. Deploy the integrations migration first, then integrations, then api, chat and web. Checked: cargo test for g1t-contracts (309), g1t-integrations (70), g1t-api (204, the OpenAPI document regenerated) and the CLI (105 and 44, the command reference current); cargo check --workspace; wasm32 checks of api and integrations; every migration applied in order to SQLite with an AI provider, a Sentry connection and Ask's route; the site's tsc -b --force, 927 tests and a production build; contracts' 48; chat's 76 and typecheck; the deploy tool's 92; the docs build (521 pages).2d ago

contribution-calendar.tsxPeople 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.4d ago

coordination.tsxEnding a session by hand is a soft close: like one that timed out, it comes back the moment its harness is heard from again. An update or a recorded entry now brings it back, where before both were refused with 'This session has ended. Start a new one.' A start already did. So a harness that was still running picks up where it was, and one that is truly gone stays ended. A session its harness ended itself still stays ended. g1t_contracts::work::revives(end_reason) is the one rule, for timed_out and 'ended by hand by @…', and update, record and subagents' late hooks use it. The End session dialog and the sessions guide say so. Checked: cargo test -p g1t-contracts (322, new: what comes back when heard from), -p g1t-work (214), cargo check -p g1t-work (wasm32).yesterday

danger-zone.tsxInvite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look1w ago

debug-details.tsxDeveloper mode: a page that fails can say why. Under Settings, Account, a Developer mode switch (kept per browser in a g1t_dev cookie, like Appearance) makes the error page show the error itself, its message and stack, the address, the time, whether it came from a page the server drew or a navigation in the browser, the routes it was drawn from, the site's build (its stylesheet's hashed name), the browser and the desktop app's version, with Copy details to paste it all into a report; with it off, the page says where to turn it on. A signed-in request with developer mode on is answered by React Router in its development mode (workers/app.ts, a second handler made the first time it is wanted), so an error on the server comes through in full instead of "Unexpected Server Error"; that mode differs from production only in that and in hooks only Vite's dev server sets, and only ever covers the person's own requests. Checked in a production build: a failing repository page shows "counts failed with status 503" and its stack with developer mode on, and the usual page with it off. The workspaces guide covers it under Developer mode.4d ago

delete-account.tsxArchiving, transferring and deleting a project are on its General settings, and "Type … to confirm" reads as one sentenceyesterday

dependency-updates.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.6d ago

deploy.tsxMerge branch 'site-fixes' into fast-push1w ago

deployments-panel.tsxMerge branch 'site-fixes' into fast-push1w ago

desktop-app.tsxMerge branch 'main' into rm-agents4d ago

desktop-runner-link.tsxMerge 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.4d ago

desktop-runner-menu.tsxMerge branch 'main' into rm-agents4d ago

desktop-runners.tsxPeople 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.4d ago

desktop-settings.tsxMerge branch 'worktree-agent-a6b141eb3a7e9cf01'4d ago

details-disclosure.tsxMerge 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)1w ago

developer-mode-switch.tsxDeveloper mode: a page that fails can say why. Under Settings, Account, a Developer mode switch (kept per browser in a g1t_dev cookie, like Appearance) makes the error page show the error itself, its message and stack, the address, the time, whether it came from a page the server drew or a navigation in the browser, the routes it was drawn from, the site's build (its stylesheet's hashed name), the browser and the desktop app's version, with Copy details to paste it all into a report; with it off, the page says where to turn it on. A signed-in request with developer mode on is answered by React Router in its development mode (workers/app.ts, a second handler made the first time it is wanted), so an error on the server comes through in full instead of "Unexpected Server Error"; that mode differs from production only in that and in hooks only Vite's dev server sets, and only ever covers the person's own requests. Checked in a production build: a failing repository page shows "counts failed with status 503" and its stack with developer mode on, and the usual page with it off. The workspaces guide covers it under Developer mode.4d ago

diff-view.tsxMerge remote-tracking branch 'g1t/main' into HEAD2d ago

emails-section.tsxPeople 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.4d ago

footer.tsxThe footer and the landing page name Flagon, Inc. and stop there: "g1t is designed, built, and backed by Flagon, Inc." and "g1t is made by Flagon, Inc.", without "a small, independent software company founded by Chase Pierce". COMPANY.about is gone; COMPANY.founder stays for the structured data search engines read. Checked: apps/web tsc -b.yesterday

fork-bar.tsxMerge branch 'forking': repository forking, pull request merge methods and every repository setting for pull requests, commits, pushes and issues2d ago

fork-button.tsxMerge branch 'forking': repository forking, pull request merge methods and every repository setting for pull requests, commits, pushes and issues2d ago

github.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.4d ago

guardrails.tsxMerge branch 'main' into ask-integration3d ago

home-ask.tsxHome fits a phone, and Getting started can be opened again from it: on a phone Home's grid had no column template, so its one column took the width of its widest row (526 px on a 390 px screen); every card ran off the right edge, and the Ask panel, sized to the page, opened as wide and cut off too. The grid's column is now minmax(0, 1fr) below lg. An owner who closed Getting started had no way back on Home itself: a Getting started button now sits at the top of Home for them (GettingStartedButton, as on Settings → General). Home's ask box is 16 px on a phone, so tapping it doesn't zoom the page, and drops the g1t mark there. Home and workspaces guides say where the button is. Checked: apps/web typecheck; the live Home at 390 px with the grid rule applied: page width 390, nothing past the edge; Ask panel on a page that fits: full width, nothing cut off.yesterday

home-summary.tsxHome says what changed on the page (#51 ): What changed, first under "Since you were last here", streams g1t's plain-English summary of the span into the card (components/home-summary, loaded when Summarize is first pressed), with Ask a follow-up, Summarize again and a link to the direct message it is kept in. The box's first starter, "Summarize what changed since I was last here", brings the card into view and starts it. The questions read as a person would ask them ("Summarize what changed since I was last here (2:12 PM) in plain English.", "Explain pull request #47 in flagon-io/g1t in plain English: what changed, why, and is it live?"): what to read and how comes from g1t's own prompt. Explain shows on every Landed row, not on hover. Checked: the site's typecheck and tests (955), and the real Home route rendered with mocked data and a streaming answer at desktop and phone width, dark and light: Summarize, the starter, Ask a follow-up and Explain.yesterday

home.tsxHome's People shows who did what as a chart, and nobody is 'someone' any more: @g1t's chat replies are stored under system:g1t, which Home took for an unnamed person. Now system:g1t, g1t's account and a workspace acting as it are one g1t row, and the card counts agents beside people instead of leaving them out. Each person or agent is a row (agents wear the agent marker) with a bar split by kind of work: pushes, pull requests, issues, shipped, docs, chat. A hover on a segment names it. Under the bars a legend gives each kind's totals in words and links to where they are listed; it replaces the bullet lines. The badge reads '2 people · 1 agent'. The summary sentence above still counts people only. A name that can't be read shows as 'unknown account'. Chart colours are new --color-series-1..6 tokens in app.css, a fixed categorical order checked for colour-blind separation on both surfaces. The landing page's Home tour gets the same People card between What changed and Landed (jordan, alex, claude, g1t). Checked: apps/web tsc -b, npm test (989; new: g1t is one row whichever key, unknown account), the tour's card rendered in a browser. The signed-in Home still needs a look with real data.yesterday

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

inbox.tsxA notification put away in the panel stays away: dismissing several quickly made one come back for a moment and go again. Each card hid itself only while its own Done, Snooze or Move back was in flight; once that settled it showed again until the panel's list reloaded without it, and each further dismissal put that reload off. A card that stepped out now stays out until the list drops it, coming back only if its request failed or the item itself changed. Checked: apps/web tsc -b.yesterday

inline-markdown.tsxMerge branch 'worktree-agent-a4babc5b5815f6f3a'3d ago

invitation-list.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.6d ago

invite-dialog.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.4d ago

invites-section.tsxMerge branch 'worktree-agent-a6da31375506fc440'3d ago

labels.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.6d ago

landing-home.tsxThe landing page's picture of Home calls its first card Settled for you, as Home does since 04d55e31 (#52 ): the card that lists what finished by itself was While you were away until #54 renamed it. Checked: components/home.tsx's SettledCard title and hint; the site's typecheck and tests.yesterday

landing.tsxThe hero says where the day starts: its line under the headline opens with Home (what landed, what is live, what needs you next), with the forge behind it, and the Home section calls Home the daily update and the way into the forge, taking you straight to what is yours to decide. Checked: apps/web tsc -b.yesterday

landmark.tsxPageMain takes the attributes a main and a div share, so the full typecheck passes1w ago

legal-doc.tsxInvite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look1w ago

logo.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.4d ago

markdown.tsxMerge branch 'worktree-agent-a9934473c8cf2bca6'3d ago

mention-textarea.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.4d ago

merge-actions.tsxMerge branch 'forking': repository forking, pull request merge methods and every repository setting for pull requests, commits, pushes and issues2d ago

merge-box.tsxMerge commit '9232a85b'2d ago

merge-queue.tsxMerge branch 'worktree-agent-aa68cf6ecc03dffaf'4d ago

merge-settings.tsxMerge branch 'forking': repository forking, pull request merge methods and every repository setting for pull requests, commits, pushes and issues2d ago

milestones.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.6d ago

mission-control.tsxMerge branch 'worktree-agent-aa8485640dce3cc93' into ship-batch2d ago

mission.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).yesterday

mobile.tsxRoutines has its place in the app, every control off: a mode of its own in the rail after Artifacts (for every member, not only those with Code), in the phone's More sheet and the command palette, at /<workspace>/-/routines, full width like Home and Apps. A routine is standing work for @g1t, and not only about code: say what, say when (a schedule, once, when something happens, by hand), say where it lands (your DM, a channel, an artifact, a pull request), and whose it is (yours, run as you; or the workspace's, kept by a team). The page draws all of it and none of it can be used: the composer is a disabled fieldset, Yours shows an empty list and the workspace's and Runs tabs are disabled, and the starting points (Keep up, Team, Code, Watch) cannot be picked. A notice says Routines are not on yet. Nothing is read or saved; the loader only checks membership. Checked: apps/web npm run typecheck, node --test app/lib/workspace-nav.test.ts and app/lib/apps.test.ts (19; new: /-/routines is the routines mode), and the page rendered alone with mock data in headless Chrome at 1280 and 390 wide. The rail, the More sheet and the palette were not looked at in a browser.yesterday

model-providers.tsxAdding an AI provider now says where to get its key, and how. The hint under each key links to the provider's key page (Anthropic's is now platform.claude.com, where the Console lives) and says what to choose there, and whether the account needs credit first: a Claude.ai or ChatGPT subscription does not include the API. Azure OpenAI links to the portal and says where Keys and Endpoint are. The AI guide has the same in a table under "Get a key", and a test asks every provider that takes a key for both. Checked: the AI providers' tests (3 passing) and the site's type-check of these files.2d ago

not-found.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.6d ago

notifications.tsxPeople 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.4d ago

observability-logs.tsxPeople 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.4d ago

observability.tsxPeople 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.4d ago

onboarding.tsxGetting started works on a phone: at 390px the sheet hid the step rail and offered only Finish once every step was done, so a finished workspace (flagon-io) could not reach any other step; the sheet changed height on every Next (447 to 836px); a step opened at the previous step's scroll position (on a computer too); and its buttons, tabs and copy buttons were 24 to 32px. A phone now has a strip of six segments under the workspace's name and the step's place, each tapped to go to its step (green done, lavender here, dim skipped); once all is done, Next sits beside Finish to look back over the steps (on a computer too); the split sheet is one height (44rem, less while the keyboard is up) with the pane scrolling inside it; each step starts at its top; on a touch screen the step's small buttons grow to 40 and 36px, tabs to 32px and CopyLine's copy button to 34px; the sheet takes focus itself on open rather than the first segment; numbered instructions run full width under their number; a provider's line wraps rather than cuts its key hint. Checked: rendered with fresh, part-done and all-done workspaces at 320, 360, 390 and 1280px (no sideways overflow, every step reachable); apps/web tsc -b --force shows no errors in the changed files.yesterday

one-time-code.tsxSix-digit codes are typed into six boxes: the sign-in's second step, turning two-factor on or off in settings, and confirming an email address. It is shadcn's Input OTP (components/ui/input-otp.tsx, on input-otp 1.4.2) in g1t's tokens: two groups of three with a rule between, the current box ringed in lavender with a blinking caret (still under reduced motion), every box red when the code was refused. One real input sits under the boxes with the field's id, name="code" and autocomplete="one-time-code", so password managers and phones' code suggestions fill it and the form posts what it did before. A pasted "123 456" or "123-456" lands as six digits. On sign-in and email confirmation the form is sent as soon as the sixth digit is in, and a refused code is cleared and the boxes focused for the next. Where a recovery code is also taken (signing in, turning two-factor off), "Use a recovery code" switches to the text field, and a recovery code pasted into the boxes switches by itself with the code carried across, so one is never cut to digits (lib/otp.ts looksLikeRecoveryCode, codeDigits). components/one-time-code.tsx holds CodeSlots and TwoFactorCodeField. Checked: apps/web tsc -b and npm test (993; new: pasted codes and telling a recovery code apart; the confirm page's field test reads the boxes), and the fields rendered alone in headless Chrome driven over CDP: focus on load, typing 123456 submitted 123456, pasting "987 654" gave 987654 and submitted, pasting k7m2q-9xw4d into the boxes moved it whole to the Recovery code field. Not tried with a real password manager or on a phone.yesterday

package-icon.tsxMerge branch 'worktree-agent-a6a121745e81f639f'1w ago

package-settings.tsxPeople 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.4d ago

people-picker.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.6d ago

people.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.4d ago

pin-button.tsxPin button: its hint is the site's tooltip, not the browser's title1w ago

platform-mark.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.4d ago

policies-draft.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.4d ago

policy-notice.tsxMerge main (membership, two-factor, GitHub repo roles) into tokens1w ago

presence.tsxPeople 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.4d ago

product-tour.tsxHome's People shows who did what as a chart, and nobody is 'someone' any more: @g1t's chat replies are stored under system:g1t, which Home took for an unnamed person. Now system:g1t, g1t's account and a workspace acting as it are one g1t row, and the card counts agents beside people instead of leaving them out. Each person or agent is a row (agents wear the agent marker) with a bar split by kind of work: pushes, pull requests, issues, shipped, docs, chat. A hover on a segment names it. Under the bars a legend gives each kind's totals in words and links to where they are listed; it replaces the bullet lines. The badge reads '2 people · 1 agent'. The summary sentence above still counts people only. A name that can't be read shows as 'unknown account'. Chart colours are new --color-series-1..6 tokens in app.css, a fixed categorical order checked for colour-blind separation on both surfaces. The landing page's Home tour gets the same People card between What changed and Landed (jordan, alex, claude, g1t). Checked: apps/web tsc -b, npm test (989; new: g1t is one row whichever key, unknown account), the tour's card rendered in a browser. The signed-in Home still needs a look with real data.yesterday

production-image-field.tsxMerge branch 'worktree-agent-a5b0d9e2733e9e382'4d ago

production-shot.tsxMerge branch 'worktree-agent-a9934473c8cf2bca6'3d ago

profile-form.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.6d ago

project-about.tsxOnly projects have descriptions now; a repository no longer keeps one of its own (#45 ). Every repository already had a project of its own name, which showed the repository's description until it was given another, so the same line lived in two places with two settings pages. Now:2d ago

project-head.tsxAn app that deploys itself says so, instead of "Deployed elsewhere". A project whose own workflows (or another pipeline) deploy it, as g1t's do, read as if g1t had nothing to do with it: grey "Deployed elsewhere" in the workspace's Projects, "App, deployed elsewhere" on its badge, and the API said `runs` is `g1t` "when g1t deploys it". What tells the two apart is who hosts it, so they are now named that way: App or site, hosted on g1t.page (badge App on g1t.page) and App or site that deploys itself (badge App, deploys itself), in settings, the badge's menu, the overview's "Where does it run?" (It deploys itself), the Deployments pages, the guides and the API's descriptions; `runs` keeps its values. In Projects an app that deploys itself shows the rocket, Deploys itself, and the Deploys filter counts it. Its production card says which workflow run deployed it when g1t Actions did ("deployed 16m ago by its workflow"), else "by its own pipeline". An app nobody has placed that deploys production itself (a successful production deployment from a workflow or the API, not g1t.page's) now deploys itself everywhere, where before only its overview inferred it: the projects service keeps that it has (migration 0013, `reports_production`), and Deployments being on or a setting still win. Checked: the site's typecheck (tsc -b --force), its 911 tests and a production build; the projects service's typecheck and 49 tests (new: an app that deploys production itself); the API's openapi tests with the docs copy regenerated; the deploy tool's 92 tests.2d ago

project-icon.tsxProjects show what they are by their icon: the projects list and grid, and the sidebar's Pinned, Recent and Projects rows, drew the same box for every project. ProjectIcon (components/project-icon.tsx) now picks one from Project.kind: a window for an app or site, books for a library, a terminal for a tool or CLI, an open book for documentation, and the box for anything else. The sidebar still shows a lock for a private project, where nothing else on its row says so; the list keeps its private badge beside the name. Sidebar shortcuts (shortcutOf, ShortcutProject) carry the kind. Checked: apps/web typecheck, lib/pins tests.yesterday

project-lifecycle.tsxArchiving, transferring and deleting a project are on its General settings, and "Type … to confirm" reads as one sentenceyesterday

public-header.tsxg1t.sh/download is a marketing page: it is drawn with the site's header and footer whoever opens it, never inside the app's rail and sidebar, in the shape of Pricing, with Download in the public header, its phone menu and the footer. The desktop app's check in CI runs on the larger machine the Rust tests use; on the small one the linker ran out of room and died with a bus error on every push since the app arrived.5d ago

qr-code.tsxMerge main (membership, two-factor, GitHub repo roles) into tokens1w ago

rail.tsxRoutines has its place in the app, every control off: a mode of its own in the rail after Artifacts (for every member, not only those with Code), in the phone's More sheet and the command palette, at /<workspace>/-/routines, full width like Home and Apps. A routine is standing work for @g1t, and not only about code: say what, say when (a schedule, once, when something happens, by hand), say where it lands (your DM, a channel, an artifact, a pull request), and whose it is (yours, run as you; or the workspace's, kept by a team). The page draws all of it and none of it can be used: the composer is a disabled fieldset, Yours shows an empty list and the workspace's and Runs tabs are disabled, and the starting points (Keep up, Team, Code, Watch) cannot be picked. A notice says Routines are not on yet. Nothing is read or saved; the loader only checks membership. Checked: apps/web npm run typecheck, node --test app/lib/workspace-nav.test.ts and app/lib/apps.test.ts (19; new: /-/routines is the routines mode), and the page rendered alone with mock data in headless Chrome at 1280 and 390 wide. The rail, the More sheet and the palette were not looked at in a browser.yesterday

reactions.tsxMerge branch 'main' of https://g1t.sh/flagon-io/g1t2d ago

releases.tsxPeople 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.4d ago

repo-about.tsxA repository's pages fail one card at a time: each page still fails on what it is about (the pull request, the issue, the commit, the run, the file, the list), and every other read goes through part(), so a service that does not answer leaves Unavailable in that card's place, not a blank card or a crashed page. Pull request: the diff, Sessions, Decisions, What happened, the preview, the merge queue's findings, Labels, Milestone, Notifications and the reviewer and assignee pickers each say so in place (settings stay strict: unread, they would let checks be ignored). Issue: Labels, Milestone, Notifications, assignees, links from outside g1t, Work and Decisions. Commit: its pull request (a stream that could reject into an Await with no errorElement), comments and the issues it closed. Code, tree and file: branches (inside the branch menu), deployments, the fork's source, the About sidebar (Packages no longer says "No packages published" when it could not be read) and a file's CODEOWNERS check; environmentsFor and forkSourceFor no longer swallow failures. Actions: workflows; a run's artifacts and job summaries; a check run's annotations. Deployments: environments, history and g1t.page hosting each on their own, never "No deployments yet" or "members can turn on hosting" because of a failure; a deployment that cannot be read is a 503, not a 404. Work: Live now, the queue, What happened, Just landed. Lists: label and milestone filters, branch rows' pull requests and previews, activity (no longer "No activity yet"), fork descriptions, compare's branches and changes, new pull request's forks and a named fork. Overview: Needs you, deployments, observability. Boundaries around the README, About, the run graph, annotations, summaries, report cards and the sidebar boxes. Kept quiet on purpose, each a decoration or an extra the service checks again: teams for mentions, ended claims, merge choices (settings answer), job-by-job checks, watcher and tag counts, the star count, release suggestions, compute notes, the plan on Deployments. Checked: apps/web tsc -b; npm test (987, 1 skipped).yesterday

repo-lifecycle.tsxArchiving, transferring and deleting a project are on its General settings, and "Type … to confirm" reads as one sentenceyesterday

repo-live.tsxMerge branch 'worktree-agent-a5c94df323642630e'4d ago

repo-settings-heading.tsxArchiving, transferring and deleting a project are on its General settings, and "Type … to confirm" reads as one sentenceyesterday

repo-view.tsxA commit's hover hint is its subject, cut on a word past 160 characters (commitHint, lib/commit-message.ts): on flagon-io/g1t's Files list a commit whose subject runs to a paragraph filled the screen with its tooltip. The Files list, Branches, Compare and Tags each use it; Branches, Compare and Tags showed the whole message, body and trailers too. The commit's page has it all. Checked: apps/web tsc -b; npm test (988; new: a commit's hint).yesterday

route-error.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).yesterday

rules.tsxMerge branch 'forking': repository forking, pull request merge methods and every repository setting for pull requests, commits, pushes and issues2d ago

run-graph.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.6d ago

runners-page.tsxMerge branch 'worktree-agent-a56293a6f836cd343'3d ago

runners.tsxMerge branch 'main' into ask-integration3d 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.6d ago

secrets.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.4d ago

security-suite.tsxMerge branch 'worktree-agent-ac950b9c891220ad3'3d ago

security.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.4d ago

session-entries.tsxSessions show by who is looking, and nothing that looks like a credential is kept: on a public repository anyone could read every prompt, command and subagent report a session recorded (coordination_repo only asked whether they could read the repository). Now whoever ran a session sees all of it; a member of the workspace sees what it did (title, tool calls, messages, notes, skills, files, subagents) but not the prompts someone else typed nor a tool's output, which show as kept back (SessionEntry.withheld), and a title without swearing (soften); anyone else sees that it runs, who runs it, its harness, state and times and the issues and pull requests it is tied to, nothing it recorded, touched, was asked or reported, nor its title, branch or model (SessionDetail.limited). The same holds for lists (Live now, Work), a pull request's session (outsiders see only g1t's notes; prompts and tool output only to their author, by the session that recorded them) and its sessions list's prompt (members only). Pending updates are shaped too: an outsider's own session on a public repository hears of members' sessions without their titles, prompts, tasks, results, branches or models.yesterday

settings-section.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.6d ago

shell.tsxRoutines has its place in the app, every control off: a mode of its own in the rail after Artifacts (for every member, not only those with Code), in the phone's More sheet and the command palette, at /<workspace>/-/routines, full width like Home and Apps. A routine is standing work for @g1t, and not only about code: say what, say when (a schedule, once, when something happens, by hand), say where it lands (your DM, a channel, an artifact, a pull request), and whose it is (yours, run as you; or the workspace's, kept by a team). The page draws all of it and none of it can be used: the composer is a disabled fieldset, Yours shows an empty list and the workspace's and Runs tabs are disabled, and the starting points (Keep up, Team, Code, Watch) cannot be picked. A notice says Routines are not on yet. Nothing is read or saved; the loader only checks membership. Checked: apps/web npm run typecheck, node --test app/lib/workspace-nav.test.ts and app/lib/apps.test.ts (19; new: /-/routines is the routines mode), and the page rendered alone with mock data in headless Chrome at 1280 and 390 wide. The rail, the More sheet and the palette were not looked at in a browser.yesterday

spike-banner.tsxThe policies are published, and g1t is written to at support@g1t.sh. Terms, Privacy, Refunds, Acceptable use and Subprocessors lose the draft banner (POLICIES_DRAFT is false, updated 2026-10-14, with the change in the policies' history): the terms name Delaware as governing law, say plainly that the plan renews each month until cancelled, and leave statutory consumer rights (an EU or UK consumer's 14 days to withdraw, how to ask, refunds within the legal deadline) above the no-refund and no-proration rules; writing to us before disputing a charge is a request, never a condition. Privacy clarifies analytics consent and what credential redaction can and cannot catch, and drops assurances about provider contracts and transfers that were not verified. Every contact (support, security, privacy, billing, abuse, legal) is support@g1t.sh, an alias for support@flagon.io, in the policies, SECURITY.md, the security page, pricing's enterprise link, the spike banner, a suspended account's sign-in message and the guides that named hey@flagon.io. Email sign-up is protected by Cloudflare Turnstile: the site's public key is set (the challenge still turns on only with both keys present), and Privacy and Subprocessors say so. Cloudflare Web Analytics' beacon is out of the site's script policy, as it no longer loads.2d ago

standalone.tsxThe left-hand navigation takes less room and reads at a glance. The dock becomes a rail: a 56-pixel column of icons with the g1t mark on top, the current app marked by a filled square, hover hints naming each with its shortcut, the apps you pinned in a scrolling band, and Apps, People, Workspace and your account at the foot. Each mode's sidebar sits flush against it, 240 pixels wide, opening on Search or jump to and listing its groups under small labels in 36-pixel rows; Ctrl B hides it and the page grows into the room. Every mode's list is built on the shadcn Sidebar now in the kit, so Workspace, Code, People, Notifications, account settings, Chat, Artifacts and Agents all share one frame; the phone keeps its bottom bar and drawer. The workspaces guide describes the rail, the sidebar and the page.6d ago

star-button.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.6d ago

start-plan.tsxMerge Stripe Tax, the card fee on card payments, and one free workspace per person1w ago

statement.tsxBilling is ready to take real money, and stays on Stripe's test key until the switch. The g1t plan is $21 a month, all-in, with $10 of usage included: the card processing fee is part of the price, and no payment carries a fee line any more (old fee rows still read as they were). Card, billing address, tax IDs, invoices and cancelling are on Stripe's billing page (Manage billing), whose configuration billing keeps in step; Checkout asks for the billing address and a tax ID; g1t's Billing page keeps usage, the spend limit, budget alerts and prepaying. Members other than owners and billing managers no longer see billing details or invoices, from the page or the API.3d ago

teams.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.4d ago

theme-switch.tsxPeople 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.4d ago

token-form.tsxAn access token can be regenerated: a new secret, its name, permissions, repositories and reach kept, and the old secret refused at once. Its page (yours under Settings, a workspace's under its settings for owners) has Regenerate with a new expiry, within the workspace's rules on lifetime, and shows the secret once; identity's regenerate_token logs it to the security log or the workspace's audit log, and refuses a revoked token. The token form's quick permissions have All, every resource at its highest level. A project's Observability settings no longer list the token g1t gives its apps on g1t.page: it is g1t's, and the page says apps there need none.4d ago

token-list.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.6d ago

token-regenerate.tsxAn access token can be regenerated: a new secret, its name, permissions, repositories and reach kept, and the old secret refused at once. Its page (yours under Settings, a workspace's under its settings for owners) has Regenerate with a new expiry, within the workspace's rules on lifetime, and shows the secret once; identity's regenerate_token logs it to the security log or the workspace's audit log, and refuses a revoked token. The token form's quick permissions have All, every resource at its highest level. A project's Observability settings no longer list the token g1t gives its apps on g1t.page: it is g1t's, and the page says apps there need none.4d ago

token-scopes.tsxThe top of every page is one surface: the breadcrumb, search, spend, Ask g1t, bell and + share one height, corners and spacing, Ask g1t is a plain tinted button with the g1t mark drawn on whole pixels, a page's own header sits directly under the bar at the same left edge, and every section, conversations and open artifacts included, draws the same rounded panel. Tables written in chat render as tables, and the site's file, checkbox, radio, number and date controls are the design system's. Button, Separator, Breadcrumb, Table and FileDrop join the shared components; the chat guide says how tables work.6d ago

topics.tsxTopics sit in About on the files pages, under the description1w ago

trust-page.tsxInvite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look1w ago

usage-card.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.4d ago

usage.tsxPeople 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.4d ago

user-card.tsxPeople 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.4d ago

webhooks.tsxMerge branch 'worktree-agent-a6ec0a89d7fe7a9ae'4d ago

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

work-icons.tsxMerge branch 'worktree-agent-ad7c6d88d93adc817'1w ago

work.tsxA session g1t starts on Claude Managed Agents acts as g1t for the person who started it: on flagon-io/demo #1 the session closed the issue and the timeline said "syntaqx closed this as completed", because its token was a plain personal access token for @syntaqx (create_access_token, scoped to the repository), so every comment, close, review and pull request it made read as theirs. It now holds a run credential of a new kind, session (credentials::RunCredentialKind::Session, made by identity's create_run_credential, up to 12 hours, revoked when the session ends as before): it resolves to g1t on behalf of the person, may use every API and MCP operation credentials::SESSION_SCOPES allow (the scopes the old token had) and never one in NEVER, in its repository only, with the person's role there capped at Write, and pushes with git to that repository (any branch, so a new repository's first version still goes to its default branch) and to the working copies of its pull requests (decide_git_at, resolved by repos from the fork's source). Past the API and git it is the person with acting kept (as_person), so the session, its claims, its pull requests' forks and its pushes stay theirs and their role decides, while what it writes is recorded as g1t's for them: issues and pull requests it opens are g1t's, requested by them (work::authorship), and its comments, reviews and the events it notes (close, reopen, labels, assignees, milestones, blocked-by, ready, draft) are written as g1t with acting_for the person (work rows::By, into the acting_for columns of migration 0033), shown as "g1t ... on behalf of @syntaqx" on the issue and pull request pages; the person can still edit them, and a session's approval counts only where agents' approvals do. The system prompt says the token is g1t's for that person. The sessions guide and the identity architecture page say what a session acts as. Deploy order: every Worker that reads a viewer (api, repos, work, packages, events, identity and the rest) before integrations, which is the only one that makes the new kind; no migration. Checked: cargo test -p g1t-contracts (316) -p g1t-work (201) -p g1t-identity (183) -p g1t-integrations (76) -p g1t-repos (363) -p g1t-api (209) -p g1t-packages (112); cargo check --target wasm32-unknown-unknown of g1t-work, g1t-identity, g1t-integrations, g1t-repos, g1t-api, g1t-packages; apps/web tsc -b shows no errors in components/work.tsx (the rest need typegen).yesterday

workspace-security-tabs.tsxUsage, Billing settings and prepaid AI credit; fixes from the UX audit1w ago

workspace-skeletons.tsxAgents in any harness coordinate through one inbox, the merge queue lands only what an attempt itself tested, and workspaces have Insights. Each session keeps the coordination updates that concern it (session_updates, migration 0038): claims, releases, hand-offs and expiries, overlaps, dependency changes, decisions, integration results and sessions starting and ending, about the issues and pull requests it is on or tied to, or every one while it is on nothing yet; never its own start, end or claims. An update is written in the same batch as the change it announces, guarded so it exists only once the change is made, with an id derived from the change, so a retry or two requests at once deliver it once; a blocker clearing and queue results follow their change under a key that names it. get_session's `updates` lists up to 100, oldest first, and reading never clears them; record_session_entries' `acknowledge` clears exact IDs for that session only and says how many were its (`acknowledged`). The CLI has `g1t session updates` and `g1t session acknowledge ID --note` (the decision note and the acknowledgement in one idempotent call, `--session` over G1T_SESSION), and those and `heartbeat` say which files the working copy changed (git status; G1T_TOUCH=0 turns it off), so overlapping edits are noticed whichever harness makes them; a pair of sessions is told again when another file in common joins. The Claude Code hooks fetch the inbox in the background, show it at every prompt and before tools when it changes or every two minutes, refresh after an acknowledgement, and never acknowledge. The AGENTS.md snippet, the skills, MCP's instructions and llms.txt say the same steps for every harness: scope claims (Scope, Interfaces, Depends on, Checks), proceed on complementary work, agree ownership before overlapping edits, record public summaries and evidence, never private reasoning. Claims resolve ownership in one statement, so simultaneous claims by one session converge. The merge queue: every attempt has its own id and branch (0037); a claimed build, an accepted build, a report and a callback each check their attempt; a dispatch registers its runs first and Actions fails the dispatch when it cannot; an attempt is decided only by its own runs (and other tools' statuses set after it was claimed), never an earlier attempt's or the pull request's own on the same commit (0040 keeps what it built and how many runs it registered); landing re-reads the rules, honours a bypass asked for when queued (0039), checks no predecessor remains, carries the exact tested commit to Git's compare-and-swap, records publication intent that fences removal, closing, drafting and changing base, resumes after a crash, and a publisher that lost a race no longer undoes the winner's landing; a retried attempt's branch is deleted; an entry whose branch or pull request is gone leaves the queue with a note instead of blocking those behind it; diagnosis rebuilds exactly what was tested and names a failing combination, not a proven cause. A session's page shows what awaits its agent as the coordination feed does. Workspace Insights (/:owner/-/insights): delivery metrics across a workspace's readable repositories (work service delivery_insights). Deploy Work migrations 0037 to 0040 first (the pipeline does), then Repos and Actions before Work, and the site with Work. Checked: cargo test for g1t-work (143), g1t-repos (311), g1t-actions-service (108), g1t-api (201), g1t (149), g1t-rules (72), g1t-contracts (306) and wasm32 builds; cargo check --workspace; the conformance suite against freshly built API and Work Workers (5, none skipped); the Claude Code hooks (49); the site's typecheck, tests (919) and a production build; the deploy tool's 92 tests; the docs build; and two unscripted local rehearsals in which two concurrent agents, given only a task and AGENTS.md, found each other, agreed a split and made complementary edits.2d ago