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
- ..
- accordion.tsx
- alert-dialog.tsx
- alert.tsx
- avatar.tsx
- badge.tsx
- breadcrumb.tsx
- button.tsx
- card.tsx
- checkbox.tsx
- collapsible.tsx
- combobox.tsx
- command.tsx
- dialog.tsx
- dropdown-menu.tsx
- field.tsx
- file-drop.tsx
- hint.tsx
- hover-card.tsx
- index.tsx
- input.tsx
- kbd.tsx
- label.tsx
- popover.tsx
- progress.tsx
- radio-group.tsx
- scroll-area.tsx
- select.tsx
- separator.tsx
- sheet.tsx
- sidebar.tsx
- skeleton.tsx
- slider.tsx
- switch.tsx
- tab-strip.tsx
- table.tsx
- tabs.tsx
- textarea.tsx
- toggle-group.tsx
- tooltip.tsx