flagon-io/g1t

public

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

git agents cloudflare rust forge mcp

The g1t CLI is 0.3.3: any harness reads and acknowledges its coordination updates. `g1t session updates [ID]` lists what other sessions did that concerns this one (claims, overlaps, dependency changes, decisions, merge queue results), which reading never clears; `g1t session acknowledge ID... --note TEXT` records the decision about them and clears exactly those IDs for this session (`--session` names another of yours), and says when an ID was not this session's. `session updates`, `acknowledge` and `heartbeat` first say which files the working copy changed (git status), so another session changing the same files is an overlap.detected for both, whatever harness either runs in (G1T_TOUCH=0 turns it off). The CLI guide lists both commands. Checked: cargo test -p g1t (105 and 44, the command reference current).

syntaqxcommitted 14h agoParentb4de9c3Browse files

348	348		\| `g1t session log TEXT` \| Records a note. `--kind` takes `note`, `prompt`, `message`, `tool_call` (or `tool-call`) or `skill` (a skill's name), `--tool` names the tool, and `--key` makes recording the same entry twice do nothing. `-` reads the text from stdin; put `--` before text that starts with a dash. \|
349	349		\| `g1t session attach` \| Points the session at an `--issue`, a `--pull`, a `--branch` or its latest `--head-commit`, or gives it a `--title`: what it is for, which replaces the title it had. \|
350	350		\| `g1t session touch` \| Says what the session touched: `--file PATH`, `--commit SHA`, `--branch NAME`, `--pull N` (one it opened), `--issue N`, each repeatable. Ties the session to the pull requests and issues they lead to; a file another active session touched too is an `overlap.detected` for both. \|
	351	+	\| `g1t session updates [ID]` \| What other sessions did that concerns this one (claims, overlaps, dependency changes, decisions, merge queue results), oldest first, up to 100. Reading never clears them. It first says which files the working copy changed, so overlapping edits are noticed (`G1T_TOUCH=0` turns that off). \|
	352	+	\| `g1t session acknowledge ID... --note TEXT` \| Records your decision about those updates (what changes in your plan, or why nothing does) and clears exactly the IDs given, for this session only; `--session` names another of yours. Saying the same again does nothing. \|
351	353		\| `g1t session end` \| Ends it, with an optional `--reason` and `--result` (what it reported; `-` reads it from stdin), and forgets it. Its subagents still going end with it. \|
352	354		\| `g1t session list` \| The repository's sessions; `--state active`, `--issue`, `--pull` (any session tied to it), `--path` (those that touched a file, or a folder ending in `/`), `--subagents` to list subagents under the sessions that started them. \|
353	355		\| `g1t session view [ID]` \| A session and what it recorded, its subagents and their results, the issues and pull requests it worked on, and the skills used; the current one without an id. \|

Comments

Sign in to comment.