Features and benefits

The handoff, productized.

DeveloperAI is the webhook layer between a Jira board and a Cursor cloud agent. It is opinionated on purpose: one active repository, one source branch, one merge target, and a workspace that stays dark until every key checks out.

What it does

  • Status trigger. Jira issue-updated events are ignored unless the status actually moves to the name you configured, usually In Progress.
  • Branch per ticket. A clean branch named after the issue key is created from your selected source branch and pushed.
  • Ticket context. The agent prompt includes the key, summary, type, priority, and description, plus instructions to commit on that branch and stop before merging.
  • Cursor cloud agent. Launch uses your API key. Completion comes back through a signed webhook.
  • Merge into your target branch. On finish, the ticket branch is merged into the branch you picked and then deleted. No pull request is opened.
  • Jira comment and transition. The ticket gets a summary plus the commit link, then moves to your In Review status.
  • Local cleanup. The temporary clone and ticket branch on the server are removed when the run ends.
  • Run history. Issue key, status, branch, and PR link stay on the workspace dashboard for the retention window of your plan.

Why teams use it

  • The boring part disappears. Nobody has to clone, branch, paste the ticket, and remember to move the status after the PR exists.
  • The merge is the finish line. When the agent is done, the ticket branch lands on the target you picked and the working branch is removed.
  • You already pay for the model. Cursor usage bills your Cursor account. DeveloperAI does not mark up tokens.
  • One board, one repo. Pinning the repository and branch keeps a noisy Jira project from opening work in the wrong codebase.
  • A locked workspace is a feature. Missing a key, a branch, or an active plan means the webhook refuses the event instead of failing halfway through a ticket.
  • Caps you can explain. Each plan has a monthly run limit. At the cap, new runs wait. There is no metered tail.

Encrypted vault

API tokens are encrypted at rest with AES-256-GCM. The dashboard shows that a key is connected, not the key itself.

Per-workspace webhook

Every account gets its own Jira URL and secret. Another customer’s ticket cannot land in your repo.

Bring the accounts you have

GitHub personal access token, Jira Cloud API token, Cursor API key. No marketplace install required to get started.