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
syntaqxCustomize is in the public API and the MCP server, and reaches Claude Code on runners. REST has it under /workspaces/{workspace}/customize: the marketplaces a workspace reads (list, add by address, remove, refresh), Discover, its installed plugins (list, one by name@marketplace, install, switch on or off, update in place, uninstall), the agents plugins brought, and its connectors (list, one, add from the directory, a plugin's server or an address, put a key on one, remove, list its tools again, grant to every agent, a team or one agent, and take a grant back), each passing through to the agents service's method; members read with workspace:read and owners change with workspace:admin, OAuth sign-in stays on the site, and the bundle a run loads, GET …/customize/bundle, is agents:run for a job's agent token or a workspace's, never a person's, which the API refuses before asking. The MCP server gets one customize tool with an action per operation, removing a marketplace, uninstalling a plugin and removing a connector marked destructive; the scope tables in Rust and TypeScript carry the operations in the same order; implement, revise, answer, review, plan and update runs' tools credentials may read the bundle; and the reference carries an example and notes for every route, the docs' OpenAPI copy regenerated. On a runner, before Claude Code starts, the harness reads the workspace's bundle with the run's agent token, fetches each switched-on plugin at its pinned commit (GitHub's tarball of the commit, a shallow clone of a repository here, or the marketplace's zip checked against its sha256) into /work/.g1t/plugins/<name> and passes each with --plugin-dir, writes the library's skills that reach the agent as one more plugin, g1t-library, and merges the connectors that reach it into the --mcp-config file beside g1t's own server, their keys kept out of the transcript; one note says what was loaded, and nothing from Customize fails a run. The self-hosted runners guide says what a run gets from Customize and how it appears in Claude Code, the working-with-g1t guide too, and the API and MCP references list the resource.