syntaqxThe docs have a guide to the Claude Code plugin, under Coding agents: installing it with the CLI it needs, what each hook records and what it never records (what a tool returned, Claude's replies, your files), the context Claude starts with, its skills and commands, what happens when the CLI is missing or signed out, opting out with G1T_RECORD_PROMPTS=0 or G1T_RECORD=0, moving off the earlier hook, and the AGENTS.md lines and MCP setup for Codex and other agents. Connect a coding agent, Sessions and why-blame, Integrations and llms.txt point to the plugin instead of the hook installer, and llms.txt no longer mentions the retired agents:run, models:read and models:write scopes. g1t.sh/install/claude.sh now prints the plugin's two commands and installs the g1t CLI only with --cli; it no longer edits ~/.claude/settings.json, so setup.mjs is gone. For anyone still on the earlier hook, it updates ~/.g1t/hook.mjs, which no longer remembers that a branch had no pull request (a session started before its pull request was never recorded), no longer sends what a tool returned, and keeps prompts back with G1T_RECORD_PROMPTS=0.cac4250History
README.md
GitHub's workflow schema
workflow-v1.0.json is GitHub's schema for workflow files, copied unchanged from
actions/languageservices, file
workflow-parser/src/workflow-v1.0.json, at commit
4043eda158e16579cc5fb1b0b07a4bce2a76f0b5 (5 August 2026). It is MIT licensed;
LICENSE is that repository's licence, copied from the same commit.
g1t does not read it at run time. src/syntax.rs lists the keys each part of a
workflow may have, and its tests check those lists against this file, so they
cannot drift from GitHub's. To update it, copy the file again, write the commit
here, and run cargo test -p g1t-actions.