Devin Not Working? Fix Task Failures, Access & Session Errors

Task stuck or looping

Signs: Devin keeps retrying the same command, or the timeline shows no new steps for >5 minutes.

What to do:

1. 1
   Check the "Session" view: Look at the terminal output for the last command — this tells you exactly what command Devin is stuck on.
2. 2
   Send a hint via chat: Type something like: "The error is because X, try Y instead" — Devin reads chat messages mid-task and will adjust.
3. 3
   Redirect away from failing tests: If looping on a failing test, send: "Skip fixing that test for now, move on to the next task".
4. 4
   No restart needed: Devin responds to natural language mid-task — you don't need to stop and start a new session to course-correct.

Common loop causes:

• Package install failures (network issues, wrong Node/Python version)
• Test failures with unclear error messages
• Missing environment variables (tell Devin what values to use or to mock them)

GitHub integration not working

Devin needs its GitHub App installed to push code.

Setup steps:

1. 1
   Open Devin integrations: Go to app.devin.ai → Settings → Integrations → Connect GitHub.
2. 2
   Install the GitHub App: On GitHub: Settings → Applications → Devin → Configure.
3. 3
   Select repositories: Choose "All repositories" or specific repos Devin should access.
4. 4
   Automatic PR flow: Devin creates branches and opens PRs automatically once authorized — it never pushes directly to main.

If Devin says "permission denied" when pushing:

• The GitHub App may not have access to that specific repo
• Check: GitHub → Your Org → Settings → Installed GitHub Apps → Devin → Configure

Environment setup failures

Devin sets up a fresh environment for each session. Common setup failures:

• 1. Missing .env / secrets: Devin can't access your secrets. Use Devin's "Secrets" feature in app.devin.ai to securely pass env vars, or tell Devin to use mock values for testing.
• 2. Wrong language version: If your project needs Node 18 but Devin uses Node 20, specify in chat: "Use Node 18 for this project" or add a .nvmrc file to your repo.
• 3. Database required: If your project needs a live DB, Devin can set up SQLite or use a local Postgres — specify which to use, or point to a test database connection string via Secrets.
• 4. Long build times: Devin has a session time limit. If builds take >10 minutes, the session may expire before the task completes. Optimize your build or split the task.

Devin goes in the wrong direction

Preventing wrong output before starting:

• Write a precise task description: "In src/api/users.ts, add a DELETE /users/:id endpoint that calls userService.delete(id). Add a test in tests/api/users.test.ts"
• Reference specific files: "The pattern to follow is in src/api/posts.ts"
• Specify what NOT to do: "Don't modify the database schema"

Add a DEVIN.md file to your repo root:

# Devin Instructions

## Setup
npm install && npm run db:migrate

## Conventions
- Use TypeScript strict mode
- Tests in tests/ directory using Vitest
- API handlers in src/api/, services in src/services/
- Never commit .env files

## Do not modify
- src/lib/auth.ts (complex auth logic, ask first)

Understanding Devin's limits