apps/web · flagon-io/g1t

.agentsInitial g1t: services, event bus, intents and attempts2w ago

.vscodeInitial g1t: services, event bus, intents and attempts2w ago

appHome'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

publicMerge branch 'main' into worktree-agent-a654d8ba46392beddyesterday

scriptsThe site's build stops a bundle whose pages throw as they load (#51 ): after react-router build, apps/web/scripts/load-check.mjs loads each route's modules from the client build, root then the route, each in a fresh worker as a browser would, and fails the build on any that throws. Deploy and CI build the site with npm run build, so the bundle Deploy #356 shipped (every page's script dying on "Cannot read properties of undefined (reading 'filter')") would have stopped there. Where you're needed's rows say Open, not Merge, for a pull request ready to merge, since it opens the pull request. Checked: the check fails all 258 routes of that bundle with production's error and passes all 258 of today's (5 s, no browser); the site's typecheck and tests (955).yesterday

workersAn agent can put an image in a pull request, an issue or a comment without committing it: on flagon-io/session-lab #2 a cloud session asked to show a screenshot of its preview in the pull request's description found no way to upload one (not in g1t --help, g1t api --list or the docs), so it committed the PNG, linked it at that commit and removed it in a second commit. The site has no comment-image upload either; images only ever came from repository files. Now upload_attachment (POST /repos/{owner}/{repo}/attachments, issues:write, the issue tool's attach action over MCP) takes name, data (the file base64-encoded, as upload_sarif takes its file) and an optional content_type, and answers in snake_case with id, name, url, markdown (![name](url), ready to paste), content_type and size. The work service decides, as add_comment does: a confirmed account that can read the repository, which is not archived. The type is read from the bytes (PNG, JPEG, GIF or WebP; a content_type that says otherwise is refused), at most 10 MB; too large is the new FailureCode too_large (413), another type the new unsupported_type (415), in Rust and TS contracts and the OpenAPI error codes. The bytes go in the usercontent namespace (AVATARS, now bound to work) under attachments/<id>, where the id is 256 random bits so the address is its permission, as Docs files' is; a row in the new attachments table (migration 0048) names the repository, and repo.purged deletes the bytes, then the rows. The usercontent origin serves /attachments/<id> as it serves avatars (stored type, nosniff, sandboxed). The API forms url from USERCONTENT_URL as the site does (g1tusercontent.com for g1t.sh, SITE_URL/-/usercontent elsewhere; the self-host config now passes it to the API). The CLI has g1t attach FILE... (prints each image's Markdown; --json the fields, a list for several) and --attach FILE (repeatable) on g1t issue create, issue comment, pr create, pr comment and pr ready, which uploads and appends the Markdown after the text. A session's run credential gets upload_attachment through issues:write, bound to its own repository (tested), and the cloud session's system prompt says to upload screenshots with g1t attach and never commit images just to link them. Docs: the CLI guide (Images in descriptions and comments), pull requests (Images), sessions, the MCP reference, self-hosting's USERCONTENT_URL row, reference.json and the regenerated openapi.json, CLI ops table and CLI reference. Deploy order: apply work migration 0048 and deploy work (new AVATARS binding), then the site (usercontent serves /attachments), then api, then integrations (prompt) and the docs; g1t attach and --attach ship with the next CLI release, which cloud sessions need before the prompt's advice works. Checked: cargo test -p g1t-contracts (319), -p g1t-work (209), -p g1t-api (211; openapi regenerated with G1T_WRITE_OPENAPI), -p g1t (112 + 51; ops_table and cli_reference regenerated with G1T_WRITE_OPS and G1T_WRITE_DOCS), -p g1t-integrations (76); cargo check -p g1t-api, -p g1t-work and -p g1t-integrations --target wasm32-unknown-unknown; node --test apps/web/app/lib/token-scopes.test.ts.yesterday

.gitignoreInitial g1t: services, event bus, intents and attempts2w ago

CLAUDE.mdThe web app's standing rule for failures, where every session working on it reads it (apps/web/CLAUDE.md): what a page is about is read strictly and fails the page inside its frame; everything beside it is a part() that says Unavailable in its own place; a failure never reads as an empty or false state; a form whose data failed is not shown; quiet fallback only for what nobody would miss, said why; complex cards in a Boundary; no streamed promise rejects into an Await without an errorElement. New and changed pages follow it; older ones are brought up to it as they are worked on.yesterday

package.jsonThe site's build stops a bundle whose pages throw as they load (#51 ): after react-router build, apps/web/scripts/load-check.mjs loads each route's modules from the client build, root then the route, each in a fresh worker as a browser would, and fails the build on any that throws. Deploy and CI build the site with npm run build, so the bundle Deploy #356 shipped (every page's script dying on "Cannot read properties of undefined (reading 'filter')") would have stopped there. Where you're needed's rows say Open, not Merge, for a pull request ready to merge, since it opens the pull request. Checked: the check fails all 258 routes of that bundle with production's error and passes all 258 of today's (5 s, no browser); the site's typecheck and tests (955).yesterday

react-router.config.tsInitial g1t: services, event bus, intents and attempts2w ago

tsconfig.cloudflare.jsonA doc opens at once: the page carries the document's saved state, so the editor mounts without waiting for its live room, which connects in the background and sends only what changed, with a quiet dot that turns green when it's synced; edits made before then are kept and sent once. The editor's code is preloaded from the page and fetched early when you hover a doc, the app's shared code ships in a few chunks instead of a hundred small ones, socket tickets come with the page instead of a round trip, and the artifacts service answers a page, a sidebar and a room in parallel lookups instead of a dozen in a row, reporting its database round trips in Server-Timing. The artifacts guide says how a doc opens, and CONTRIBUTING's Speed section has the numbers.6d ago

tsconfig.jsonMoney is written one way. A single formatter turns millionths of a dollar into dollars, rounding half up on whole micros rather than on a float, so the same sum reads the same on every page: under a cent reads <$0.01 on a total and exactly nothing is $0.00, while the statement's lines, a session's receipt, the price book and an agent's effort costs carry up to four places where the fraction of a cent is the point; the six formatters that each rounded their own way are gone. This month is the calendar month in UTC from its first day to today everywhere, and billing counts the month's not-yet-closed usage in any range that reaches into the current month, so the top bar's pill, Spend, Home and Usage ask for the same days and get the same figure; Home now reads the usage report the others read instead of adding up statements. Usage's pending sentence says what of that usage the close will charge after the discount and included usage, which the billing API returns as pending_charged_micros. A reconciliation test holds the pill, Spend, Home and Usage to one number for one month. The usage and billing guide says how amounts are written and what this month means.6d ago

tsconfig.node.jsonInitial g1t: services, event bus, intents and attempts2w ago

vite.config.tsMerge remote-tracking branch 'origin/main' into claude/cool-newton-7nm8r94d ago

wrangler.jsoncThe 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