Skip to content
Sign up

flagon-io/g1t

public
00

Where people and agents ship software together. The open-source git platform for the whole job: issues, agents, checks and deploys to the edge.

g1t.sh
gitagentscloudflarerustforgemcp
syntaqxThe site shows who is working on what: a repository's Work page, an issue's Work panel, a pull request's integration failure and decisions, and why-blame's decisions. The Work page (/<workspace>/<repo>/work, a tab beside Pull requests, Merge queue and Sessions) lists Live now, the active claims and the active and idle harness sessions grouped by issue, with an issue claimed twice marked; the merge queue's train; What happened, the latest 30 coordination events as a feed; and Just landed, the latest merges with a link to the session behind each. With nothing going on it says how to start: the Claude Code plugin's two commands, or g1t work claim from any harness. An issue's sidebar opens with a Work panel: its claims (who, which harness, since when, when each lapses, and ones released, expired or handed off lately dimmed), its sessions with their state and when each was last heard from, what it is blocked by and where each stands, and what it blocks; its author and Triage change blocked_by with Edit, through update_issue. Under its pull requests the issue shows the latest combination that failed in the merge queue (the pull requests tested together, the failing check linked to its run, what it fails with, and the fix or pass that answered it) and its decision records, each badged Claimed, Tested or Approved. A pull request shows that failure above its checks until it passes in the queue or merges, and its Session tab lists the harness sessions on it and its decisions above what was recorded. A session has a page of its own at work/sessions/<id>. Why-blame's panel adds How it was decided: the failed combination and its fix, then the proposals, the approval and the merge, from the decisions on the issue and all its pull requests.