Gleap AI agents can read Cursor cloud agents through Composio, for engineering teams that fix some customer bugs with Cursor while support and bug reports run in Gleap. A custom agent can list your Cursor agents and read an agent’s conversation, so the teammate on a Gleap ticket knows how the fix is going.
What a Gleap agent can do in Cursor
- Which cloud agents are running: List Agents shows your Cursor cloud agents and their status, for example the one an engineer started for a customer’s bug.
- What the agent did: Get Agent Conversation reads a cloud agent’s conversation, so the Gleap teammate can summarize progress without asking the engineer.
- Which repositories Cursor can reach: List GitHub Repositories shows the repositories connected to your Cursor account.
- Models and key checks: List Available Models and Get API Key Info show which models the key can use and whom it belongs to.
Example: a customer asks whether the fix is coming
A customer asks in the Gleap widget whether the export bug they reported last week is being fixed. An engineer had handed that ticket to Cursor. The teammate asks the agent on the ticket, which finds the matching Cursor cloud agent, reads its conversation and reports that a pull request is open and waiting for review. The teammate tells the customer the fix is in review, without promising a date.
How to connect Cursor
- In Gleap, open AI & Automation, then Agents, and select the custom agent that should use Cursor, or click Create agent.
- Under Tools, click Add tool, search for “Cursor” and select it.
- Enter a Cursor API key and any other details the form asks for, then click Connect Cursor.
- Open the Cursor tool and check its five actions; all of them read data.
- Publish the agent and test it in chat before you turn on a trigger.
Kai Code is on Team, Pro and Enterprise, and Kai Support can use connected apps as tools on the same plans. Custom agents are on the Team, Pro and Enterprise plans.
FAQ
Does Gleap integrate with Cursor?
Yes, in two ways. Custom agents can read Cursor cloud agents through Composio’s Cursor toolkit with a Cursor API key. Separately, on plans with Kai Code, a Gleap ticket’s fix button offers Open in Cursor, and Kai Code Bridge can run sessions with Cursor on your own machine.
What can a Gleap AI agent do in Cursor?
Through Composio, five read actions: list cloud agents, read an agent’s conversation, list available models, list connected GitHub repositories and read the API key’s details. It cannot start or stop Cursor agents.
Which Gleap plan includes the Cursor integration?
Kai Code and the Open in Cursor hand-off are on Team, Pro and Enterprise, and Kai Support can use connected apps as tools in its customer conversations on the same plans. Custom agents that use Cursor are part of the Team, Pro and Enterprise plans. Cursor’s own plan decides whether cloud agents are available. AI usage in Gleap is billed separately; see pricing.
Should we fix a ticket with Kai Code or with Cursor?
Both start from the same Gleap ticket. Kai Code works inside Gleap and reports its pull request back to the ticket; Open in Cursor hands the task to an engineer’s Cursor. Your team reviews and merges the pull request either way.
