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

chatMerge main into project-descriptionsyesterday

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.3d ago

peopleThe 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

teamPeople 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.3d ago

actions-settings.tsxMerge GitHub pull request #8 (claude/cool-newton-7nm8r9): Docker deployments on g1t.page behind a switch that stays off until Cloudflare's container APIs are checked live, workflows a workspace manages in its repositories, tarball and zipball downloads, refs/pull/* kept to g1t alone, framework detection for g1t.page builds, and a workflow's event payload matching GitHub's.4d ago

ai.tsxMerge branch 'worktree-agent-ac7d6e0b40efe9fe8' into ship-batch2d ago

apps.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.tsA 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

audit-export.tsAgents get guardrails, run credentials, an audit log, a context hub, repository instructions and mentions; security upkeep; snake_case API1w ago

audit.tsxMerge branch 'worktree-agent-a4babc5b5815f6f3a'3d ago

billing.tsxMerge main into project-descriptionsyesterday

chat-settings.tsxMerge main into project-descriptionsyesterday

code-access.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

code-overview.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.3d ago

emoji.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

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

home-seen.tsThe front page is Home: where you're needed comes first, however long ago it started, with what's at stake and how long it has waited; then what happened since you were last here, in words, with the agent work that settled, what landed, what deployed, what was decided and what was spent, switchable to the last 24 hours or 7 days; then what's running now. Your last visit is kept with your account, so it's the same on every device; Today's old address leads here. The home guide says how.6d ago

home.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

insights.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

integrations-directory.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

integrations.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

layout.tsxGive visited workspaces their own project navigation2d ago

member-invitations.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

members.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

moved.tsThe front page is Home: where you're needed comes first, however long ago it started, with what's at stake and how long it has waited; then what happened since you were last here, in words, with the agent work that settled, what landed, what deployed, what was decided and what was spent, switchable to the last 24 hours or 7 days; then what's running now. Your last visit is kept with your account, so it's the same on every device; Today's old address leads here. The home guide says how.6d ago

new.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

onboarding.tsMerge branch 'worktree-agent-ac7d6e0b40efe9fe8' into ship-batch2d ago

overview.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

package.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

packages.tsxGive visited workspaces their own project navigation2d 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

permissions.tsxMerge main into project-descriptionsyesterday

personal-access-tokens.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

pins.tsNavigation: the workspace's own page with tabs, pins and recent in the sidebar1w ago

projects.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

repositories.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:yesterday

rules.tsxA page's tabs are paths, not ?tab= (#52 ): a profile's are /u/syntaqx/pulls, /issues and /stars; a pull request's Session and Files changed are /pull/12/session and /pull/12/files (the segment the desktop and phone links and the analytics already expected); the Branches page's are /branches/yours, /active, /stale and /all; rules' Insights is /settings/rules/insights and /<workspace>/-/rules/insights; and Notifications' Saved and Done are /notifications/saved and /notifications/done. A tab that is a page of its own gets an address of its own, which reads, shares and bookmarks well. What narrows a list stays in the query: state, repo, sort and before on a profile; q on Branches; branch, tag, problems and before on Rules; and on Notifications the severity tabs (?tab=needs and the like, which narrow any view and are kept as the panel in the top bar fetches them) and reason. The package page's ?tab=settings stays too: its name is a splat that can itself end in /settings (an npm package @acme/settings).yesterday

ruleset.tsxMerge rulesets: branch and tag rules, agent-first, enforced on push and merge1w ago

runners.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

secrets.tsxSocial cards for every page: og.g1t.sh1w ago

security-bypass.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

security-patterns.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

security-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

security.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

settings.tsxMerge branch 'worktree-agent-ac7d6e0b40efe9fe8' into ship-batch2d ago

soon.tsxMerge branch 'rm-boards'4d ago

statement-csv.tsMerge Stripe Tax, the card fee on card payments, and one free workspace per person1w ago

statement-entries.tsMerge branch 'worktree-agent-a985c01f43538af01'1w ago

team-new.tsxMerge branch 'worktree-agent-ad7c6d88d93adc817'1w 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

token-new.tsxOne kind of access token; presence and status; usernames keep their case; the tour is a miniature of the real app; icons for password managers1w ago

token.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

tokens.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

usage.tsxThe contracts no longer describe g1t's own agents, and workspaces can keep their AI providers. Every consumer had already stopped using them, so the TypeScript and Rust contracts drop the workspace-agent, ability, look, skill-library, context, runner-agent and mention modules, the chat and docs RPCs agents posted and read through, the folio agent methods, the agent_waiting notification, agent.asked and memory.changed events, AI credit, token and gateway billing types, model routes and sessions, team agents, agent tokens, plan, review, message and confidence types, command rules, cost caps and confidence rules. The agents:run and models:* scopes are no longer offered by any preset, OAuth default or permission form, but a stored token or grant that names them still reads; and the removed operations are gone from the scope table, so the API's check that every operation has exactly one scope is strict again. What stored data needs in order to parse (old run and credential kinds, an agent team lead, retired rules and webhook events, old guardrail and integration settings) still parses, and a run's token is still PrincipalKind::Agent, which now means a run's token and the @g1t rows written before. The customize, marketplace, skills and claude-plugin contracts stay only until the mobile app drops its Customize screens.4d ago

webhooks.tsxSocial cards for every page: og.g1t.sh1w ago

workspace-overview.tsxMerge branch 'worktree-agent-ac7d6e0b40efe9fe8' into ship-batch2d ago