How It Works
- You ask the Modem Agent to implement something (e.g., “fix the login timeout bug”).
- Before delegating, the agent queries your Modem data for relevant context: bug reports, user feedback, error patterns, affected user counts.
- The agent composes a task description enriched with that context and sends it to Cursor or Devin.
- You approve the action (all coding agent tasks require confirmation before executing).
- The coding agent works asynchronously. You can check on progress through the Modem Agent.
Task descriptions are sent to the coding agent’s servers (Cursor or Devin). Only context relevant to the task is included.
Prerequisites
- A Modem organization with the GitHub integration connected (so the coding agent knows which repositories to work on)
- An API key for the coding agent you want to use (Cursor, Devin, or both)
Setup
Each team member configures their own API key. Keys are stored encrypted and never shared with other members.Add your API key
Scroll to the Coding Integrations section. You’ll see fields for Cursor and Devin. Enter your API key for the tool you want to use and click Save. Modem validates the key before saving it.
Cursor
Cursor’s Cloud Agents run on Cursor’s infrastructure. They can implement features, fix bugs, create pull requests, and investigate codebases.Getting your Cursor API key
- Open cursor.com/settings/keys
- Generate a new API key
- Copy the key and paste it into Modem’s Coding Integrations section
What Cursor can do
- Implement features and fix bugs across your connected GitHub repositories
- Create pull requests with the changes
- Investigate codebases: read source code, trace execution paths, audit implementations
- Target a specific repository and branch
Example prompts
Checking task status
After triggering a Cursor task, you can ask the agent to check on it: The agent will return the current status, a summary of work done, and a link to the pull request if one was created.Devin
Devin is an autonomous AI software engineer that handles complex, multi-step implementation tasks. Devin sessions run asynchronously and you can send follow-up messages to provide additional context or redirect its focus.Getting your Devin API key
- Open your Devin dashboard settings
- Navigate to the API keys section
- Generate a new API key
- Copy the key and paste it into Modem’s Coding Integrations section
What Devin can do
- Handle multi-step implementation tasks across multiple files and repositories
- Create pull requests with the changes
- Investigate codebases: map architecture, audit implementations, report findings
- Accept follow-up messages during an active session
Example prompts
Checking session status
The agent returns the session status, recent messages, and a link to the pull request if one exists. You can also view the session directly on the Devin dashboard.Context Enrichment
When you ask the agent to delegate a coding task, it automatically considers whether your Modem data can inform the work. For example:- “Fix the login timeout bug” — the agent queries topics and discussions about login timeouts first, then includes error reports, reproduction details, and user impact in the task description.
- “Address the top complaints from this week” — the agent finds the most-reported issues and provides the coding agent with specific details.
Troubleshooting
Agent says API key is not configured
Agent says API key is not configured
Go to Profile > Coding Integrations and verify your key is saved and active. You can test the connection from that page.
API key validation fails
API key validation fails
Make sure you copied the full key. For Cursor, generate a new key at cursor.com/settings/keys. For Devin, generate a new key from your Devin dashboard settings.
Task was triggered but nothing happened
Task was triggered but nothing happened
Check the task status through the agent. Cursor and Devin tasks run asynchronously and may take a few minutes to start. If the status shows an error, the coding agent may have encountered an issue with repository access or permissions.
Coding agent can't access my repository
Coding agent can't access my repository
Make sure the repository is connected through Modem’s GitHub integration. The coding agent can only target repositories that Modem has access to.