These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
Integrations
Connect code activity with project decisions
- Code and collaboration
- Code and communication providersTeams · in and out
- Service intake
- Ticket and incident sourcesin
- Delivery reporting
- Analytical and time consumersout
- Agents
- Your agentWorks within the permissions you assign
Code and collaboration
- Code and communication providers. Configured git connections supply authenticated pull-request events with repository, branch and check context. Slack, Teams and email carry permitted notifications without changing the underlying business decision.
Service intake
- Ticket and incident sources. Approved helpdesk and service-management connections promote a ticket or incident into one scoped issue while retaining the original source identity.
Delivery reporting
- Analytical and time consumers. Permitted analytical consumers receive dated issue and iteration outcomes. Work logs can be exported to a separately configured time or billing system; they are not billing approvals here. Actual deployment evidence remains with the delivery platform.
How connections are governed
service accounts, audit, pausingPin reviewed composition and connector revisions. Authenticate incoming events, retain provider EventID and OperationKey, and reconcile unknown outcomes before another attempt. Bind repositories and target branches explicitly. Neither a merge event nor a notification supplies a human verification or deployment result.
The API is one more client of the same interface. Agent reference →
# Example work after configuration
$ curl -s erp.ai/skill.md
› Show why this issue cannot enter review and which current WIP limit applies.
› Compare this sprint’s original commitment with its frozen closing outcomes.