Pick any line to see why it is the way it is: the commit, the pull request and issue it came from, and what the agent was thinking.
| g1t has a plugin for Claude Code, in its own marketplace at the repository's root (claude plugin marketplace add https://g1t.sh/flagon-io/g1t.git, then claude plugin install g1t@g1t). Its hooks record each session on g1t through the g1t CLI in a working copy of a g1t repository: SessionStart starts the session (g1t session start --harness claude_code --harness-session-id, idempotent on Claude's session id) and gives Claude the work context of the issue the session claimed or the branch names (g1t work context N, waited for under a second, else a line saying how to load it), or a line on how to claim one; UserPromptSubmit logs the prompt's first 2,000 characters; PostToolUse logs the tool's name and one line on what it was called with, with anything that looks like a secret hidden, and never what it returned, and after a git push that reached the remote sets the session's head commit; Stop sends a heartbeat and SessionEnd ends the session with Claude's reason. The hooks are one Node script with no dependencies that returns at once and runs the CLI in a detached process; when g1t is missing or signed out it records nothing and says so once, and it installs nothing. G1T_RECORD_PROMPTS=0 keeps prompts back and G1T_RECORD=0 records nothing. The plugin also connects g1t's MCP server, has the skills work-on-issue, fix-integration and coordinate and the commands /g1t:claim, /g1t:status and /g1t:handoff, and plugins/other-harnesses has the AGENTS.md lines that do the same with the CLI for Codex and other agents. node --test plugins/claude-code/test/hooks.test.mjs checks the hooks against a stand-in CLI, and CI runs it. | 1 | --- |
| 2 | description: Claim a g1t issue for this session and load its work context | |
| 3 | argument-hint: "<issue number> [note]" | |
| 4 | allowed-tools: Bash(g1t:*) | |
| 5 | --- | |
| 6 | ||
| 7 | Claim g1t issue $1 for this session. | |
| 8 | ||
| 9 | 1. Run `g1t work context $1` and read it: the definition of done, who else | |
| 10 | has claimed it, its pull requests and what blocks it. | |
| 11 | 2. Run `g1t work claim $1`, adding `--note "..."` with the rest of these | |
| 12 | arguments if there are any: $ARGUMENTS | |
| 13 | 3. Tell me in a few lines what the issue asks for, whether anyone else holds | |
| 14 | a claim on it (the claim command lists them), and anything that blocks | |
| 15 | it. If someone else is on it, ask me before starting work. |
