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.6cc1290History
- ..
- abilities-prompt.ts
- abilities.test.ts
- abilities.ts
- access.test.ts
- access.ts
- archived.test.ts
- archived.ts
- audience.ts
- budget.test.ts
- budget.ts
- builder-call.ts
- builder.test.ts
- builder.ts
- builtin.ts
- card-views.ts
- cards.test.ts
- cards.ts
- computer.test.ts
- computer.ts
- connectors.test.ts
- connectors.ts
- customize-fetch.ts
- customize-rpc.ts
- customize.test.ts
- definition.test.ts
- definition.ts
- desk.ts
- effort.test.ts
- file-markdown.ts
- files.test.ts
- files.ts
- handle.test.ts
- handle.ts
- handoff.test.ts
- handoff.ts
- happened.ts
- index.ts
- installs.test.ts
- installs.ts
- marketplaces.ts
- mcp-client.ts
- memory.ts
- meter.ts
- money.ts
- ooxml.ts
- orchestrator.test.ts
- orchestrator.ts
- pdf.ts
- person-budget.ts
- plugins.ts
- policy.ts
- ports.ts
- prompt.test.ts
- prompt.ts
- recall.test.ts
- recall.ts
- recommend.test.ts
- recommend.ts
- reply.ts
- routines.ts
- routing.test.ts
- routing.ts
- schedule.ts
- sessions.test.ts
- sessions.ts
- skill-draft.ts
- skill-library.test.ts
- skill-library.ts
- skill-rpc.ts
- skill-zip.ts
- skills.test.ts
- skills.ts
- store.ts
- suggest.ts
- surface.test.ts
- surface.ts
- team-move.test.ts
- team-move.ts
- teammates.test.ts
- teammates.ts
- templates.ts
- tools.test.ts
- tools.ts
- transcript.ts
- triggers.test.ts
- triggers.ts
- turn.test.ts
- turn.ts
- views.ts
- welcome.test.ts
- welcome.ts