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.

gitagentscloudflarerustforgemcp
syntaqxA session's transcript reads as what it said, with its tool calls between: "What it recorded" on a session's page (and What happened on a pull request's Session tab) drew every entry as a full-height row. A tool call said its tool twice ("bash bash: curl …", "g1t:issue g1t:issue: work"), a message's Markdown showed its ** and backticks as written, the prompt's <issue> and <comment> blocks were raw text in a <pre>, and a run of eight tool calls was eight bordered rows. Tool calls between two messages now run together (lib/session-entries.ts transcript): up to three in a tight list, more folded into one line ("7 tool calls · bash, write, read") that opens to it, each result folded under the call before it. Each call says its tool once (readToolCall takes the "<tool>: " off the front of its text, and finds the tool in the text when the entry has none, as from the Claude Code plugin): a command as code in one line, a long one unfolding in full; a file by its path with a file icon; an MCP tool by resource and action ("issue · claim", "pull request · create") with the g1t mark for g1t's, and its server's name for others (mcp__claude_ai_Google_Drive__… is Google Drive). Messages render with the site's Markdown, references linked within the repository. The prompt folds under its first line and opens to it rendered, its <issue> and <comment> blocks as quotes under a label (quotedBlocks). Relative times stay on prompts, messages, skills and notes. The sessions guide says how the transcript reads.