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

Cloud sessions work end to end: CLI, web, first push, attribution, deploy setup #55

Closedsyntaqx opened this

Sessions g1t starts on Claude Managed Agents struggled on flagon-io/demo #1: the CLI failed TLS in the sandbox, the push of a new repository's first version was blocked, they couldn't reach the web, Closes #1 on the first push didn't close the issue, and everything they did on g1t showed as the person who started them.

Shipped (on main and deployed):

  • 25309b9 CLI 0.3.5 trusts the system certificate store (released)
  • cf8330c the kickoff allows an empty repository's first push to the default branch; commits are by the person via setup
  • 538878a / 62073459 web search and fetch, and unrestricted sandbox networking
  • a20fe87 the session's report is its answer; no duplicate comment
  • 695f960 the session transcript reads cleanly
  • 9319d68 a new repository's first push closes the issues its commits name
  • 84f55cb an issue says what closed it (commit, pull request, session); close takes commit
  • c678dca sessions act as g1t on behalf of the person
  • b2c7528 what a session's push closes is g1t's, for the person
  • 56c1d3a deployment settings through the API, MCP and CLI; deploy on repository create
  • 42a2957 CLI 0.3.6 (deploy settings/enable/disable, repo create --deploy, issue close --commit)
  • 5925eaa plugin 0.2.6 (published)
  • 4e63b3f, 3c9af97, 84f4718 a pushed annotated tag starts its push: tags workflows, announced at its commit
  • e523a6f a piped git push … | tail is no longer recorded as a branch named "|"
  • 50116217 image attachments: upload_attachment (API), the issue tool's attach (MCP); the session prompt says g1t attach, never commit images
  • 132e163 CLI 0.3.7 (g1t attach, --attach; released by CLI release #8) and plugin 0.2.7 (published)
  • 960f565 the session's headless browser trusts the sandbox proxy (NSS store), never turning certificate checks off

Verified live:

  • flagon-io/session-lab #1: issue → session → web lookups → Vite build → first push with Closes #1 → deployed → checked live, with no help
  • flagon-io/session-lab #2 → pull request #3 by g1t, requested by @syntaqx; its events are g1t on behalf of @syntaqx
  • A comment's own create response carries the caller's token scopes and grants; other viewers don't see them (reads return the author without them)
  • Agents can attach an image to a pull request or comment (50116217, 132e163)
  • Annotated tag pushes start their workflows: v0.0.0-tagtest2/3 on flagon-io/automation-lab announced at 059b2e5 and started Machine size #7, #8
  • A cloud session's headless browser loads an https page with certificate checks on: flagon-io/session-lab #4 (session ses_01m4zxna17e5ht2qn8v42khk52) — headless Chromium first refused https://session-lab-flagonio.g1t.page with ERR_CERT_AUTHORITY_INVALID, ran BROWSER_TRUST from its prompt, then loaded the page and attached a screenshot, with checks on throughout

Noticed along the way: the kickoff prompt always says "make the change on a branch, open a draft pull request", even for an issue that asks for a check and no changes; the session rightly followed the issue.

Pull requests

None yet

Nobody has worked on this yet

Point your own agent at flagon-io/g1t#55.

Discussion

syntaqxcommented

Status 09:05 UTC:

  • 960f565 (headless browser trusts the proxy) is pushed; CI #306 and Deploy #385 are running.
  • cli-v0.3.7 (annotated, on 132e163) was pushed to g1t at ~08:59 and started no CLI release run, although 4e63b3f has been live in repos since Deploy #377 (07:22). So annotated tag pushes still don't announce git.push. I started CLI release #8 from the tag by hand (workflow_dispatch), as 0.3.5 and 0.3.6 were.
  • Not found yet: pushed_to (services/repos/src/pushed.rs) takes a tag as refused only when parents(after) returns Ok(Some), and Artifacts' readCommit is documented to throw on a non-commit, which would count as pushed. So either the store's readCommit follows a tag object to its commit in practice, or the tag never reaches announced. Next: reproduce with an annotated tag on flagon-io/automation-lab and log what pushed_to sees.
syntaqxcommented

Annotated tag pushes start their workflows, verified live 09:32 UTC.

  • Cause: Artifacts can't log an annotated tag's ref, so 4e63b3f announced cli-v0.3.7 at its tag object (a41bb23) and Actions found no workflows there.
  • 3c9af97 announces a tag at its peeled ^{} commit from the store's ref list. 84f4718 also reads the commit from the tag object in the pushed pack, as a safety net (I first thought 3c9af97 had failed; it hadn't, the event was just late to show up).
  • Check: annotated v0.0.0-tagtest2 and v0.0.0-tagtest3 on flagon-io/automation-lab were announced at 059b2e5 (main's commit) and each started Machine size (#7, #8). Test tags deleted.
  • CLI 0.3.7 was released by CLI release #8, started by hand from the tag.

Left on #55: one cloud session whose headless browser opens an https page with certificate checks on (960f565, deployed).

syntaqxclosed this as completed·

Sign in to comment.