From ticket to production — automatically.
Connect your project. Link your board. gShip AI picks your tickets, writes the code, runs QA, and deploys — while you focus on what matters. We're open for contributions! Help us build the future of autonomous shipping.
Want to contribute? Join our developer community and help shape the future of gShip AI.
Everything you need to integrate gShip into your existing development environment.
npm install -g @google/gemini-cli
gemini --yolo
| Field | Description |
|---|---|
| Project Name | A unique display name for your project. |
| Repo Root Path | The absolute path to your local repository. |
| Azure DevOps Config | (Optional) Base URL, Repository Name, and Branch. |
.env file if you manage multiple
projects under the same organization.
| Guardrail | Detail |
|---|---|
| Risk Gate |
Halts for review if package.json or
.env are modified.
|
| Timeout | Pipeline polling expires after 10 minutes. |
| Loop Guard | Maximum 10 agent steps per ticket to prevent infinite loops. |
| Advanced Op | Command / Action |
|---|---|
| Reject & Fix | Send STAGED ticket back with comments. |
| Dual-File Sync |
State kept in shared-memory/*.json and
tasks/*.md.
|
| Manual PR |
node server/scripts/azure-pr.js <id>
<branch>
|
| Issue | Solution |
|---|---|
| Polling Timeout | Verify pipeline status in Azure DevOps; check triggers. |
| Wrong UI Status |
Clear browser cache or check shared-memory/ JSON.
|
| Agent Fails |
Ensure CLI is authenticated (gemini --yolo).
|
Five steps from backlog to production. Every step handled by AI agents that understand your codebase.
Not another copilot. A full engineering team that ships autonomously.
Follow the autonomous setup guide and modernize your engineering lifecycle today.