Claudeagent and ClaudeagentA workflow step can open a g1t.page build with POST /repos/{owner}/{repo}/deployments/builds (the workflow tool's start_deployment_build over MCP), sending its job's own token and, optionally, the project's slug and the commit; the project may be left out when the repository has one project with Deployments on. It answers with the build's id and token for g1t-runner deploy, whether it is production or a preview, the app's address, whether the run was trusted, the project's root directory, build command and output directory, and the variables and secrets builds of that kind get. It needs deployments:write, which a job's permissions give with deployments: write or pages: write, and no token but a job's is let through. The API reference, its example, and the MCP reference say so.7fdf622History
- ..
- invites
- access.rs
- account_deletion.rs
- admin.rs
- aliases.rs
- avatars.rs
- crypto.rs
- deletion.rs
- deploy_keys.rs
- device.rs
- directory.rs
- dock.rs
- email.rs
- emails.rs
- github.rs
- invites.rs
- job_tokens.rs
- lib.rs
- members.rs
- oauth.rs
- paid.rs
- people.rs
- profiles.rs
- rename.rs
- run_credentials.rs
- security.rs
- shared_invites.rs
- sounds.rs
- teams.rs
- throttle.rs
- token_reach.rs
- tokens.rs
- two_factor.rs
- workspaces.rs