# How to send a coding task to Cursor from a conversation

Work out a change in a conversation, then hand the coding task to Cursor's cloud agents from the same place. Add your Cursor API key once, pick a Cursor model, and send the task with your GitHub repository link. The reply shows the Cursor job and, when it finishes, the result.

If you already use Cursor, you can hand a coding task to it straight from a GPTree conversation: work out the change with your AI model, then send the task to Cursor's cloud agents without switching tools. Cursor works on your GitHub repository, and GPTree tracks the job in the conversation.

Cursor is not one of the apps under Connect tools, and it does not need Graft: it has its own settings page.

## Set it up once

1. Open **Settings**, then **Cursor** (under Connections).
2. Paste your Cursor API key (you get one from your Cursor dashboard) and select **Save Key**. GPTree checks the key with Cursor straight away and shows **Cursor API key verified**.
3. Keys are encrypted and only ever sent to Cursor.

Once the key is verified, Cursor models appear in the model menu alongside your other models, for example **Cursor · Composer 2** and **Cursor · Auto**.

## Send a task

1. In the conversation, open the model menu and pick a Cursor model. You can pick it for the whole conversation or for a single message.
2. Write the task in your message, with the link to your GitHub repository (https://github.com/owner/repo). GPTree remembers the repository for that conversation, so later tasks there can leave it out.
3. Send it. The reply says the task was submitted to Cursor, with its status and an **Open in Cursor** link.
4. GPTree keeps checking the job. When Cursor finishes, its summary, the result and any branches it created are added to the reply.

Only the message you send goes to Cursor, not the whole conversation. If the task depends on code or a decision from earlier in the conversation, paste it into the message, for example "Review this function for edge cases" followed by the code.

## By voice

Say "switch this pane to Cursor", or "send this to Cursor". Voice switches the pane to Cursor, and your next message in that pane goes to Cursor as the task, so say the task with your repository link. "Open Cursor settings" opens the setup page.

## Run it on your own machine

With the Graft bridge connected on a computer that has Cursor's command line tool, **Cursor · Local CLI (Graft)** runs the task there instead of in Cursor's cloud. **Cursor · Auto** uses your machine when the bridge is connected, and the cloud otherwise.

## If something goes wrong

- **"Cannot send to Cursor: no repository detected"**: add your GitHub repository link to the message and send it again.
- **"Cursor API key is not verified"**: open Settings, Cursor and select **Verify Stored Key**, or save a new key.
- **No Cursor models in the menu**: the key is missing or not verified yet. Check Settings, Cursor.