Plan in Ask mode, then run in Agent mode

When you open a new session, Devin offers two modes: Ask and Agent. Using them in the right order is the easiest way to get a good first result.

Read the steps as text

1. Ask. Explore the code and build a plan. Nothing is changed.
2. Construct a Devin Prompt. Devin writes a scoped prompt from the Ask session.
3. Send to Devin. The prompt starts an Agent session.
4. Agent. Devin writes code, runs commands and opens a pull request.
5. Session Insights. After the session, generate an analysis of how it went.

1. Ask. Explore the code and build a plan. Nothing is changed.
2. Construct a Devin Prompt. Devin writes a scoped prompt from the Ask session.
3. Send to Devin. The prompt starts an Agent session.
4. Agent. Devin writes code, runs commands and opens a pull request.
5. Session Insights. After the session, generate an analysis of how it went.

What each mode does

Ask is a lightweight mode for exploring code and planning. In the docs’ words, it works “without making changes to the actual code.”

Agent is the full autonomous mode. It writes code, runs commands and creates pull requests.

The docs’ advice is plain: start in Ask mode unless you already have a fully scoped plan, then move to Agent mode to carry it out.

Step 1: Ask

From the main page, switch to Ask mode and select the repositories you want Devin to look at. Then ask real questions:

• Where is this behaviour implemented?
• What would have to change to add this?
• What could break?

You can also start from a repository’s DeepWiki page. Type a question in the chat box and click Ask, and Devin is scoped to that repository.

Step 2: Turn the answers into a prompt

When the plan looks right, click Construct a Devin Prompt. Devin writes a scoped prompt from everything in the Ask session. Read it and fix anything that is off. Then click Send to Devin.

Step 3: Agent

In Agent mode, pick the repository from the selector. It lists the repositories that have been added to Devin’s machine, which is why the setup in lesson 2.1 comes first.

You can add context with @ mentions. They can point to repositories, files, skills, secrets or other sessions.

Step 4: Look at how it went

After the session, open Session Insights and click Generate Analysis. It is the quickest way to learn what slowed the session down, and what to change in your next prompt.

A sensible first task

Choose something with a clear pass or fail result: a failing test to fix, a small refactor that existing tests cover, or a dependency update. The docs note that tasks with test suites, CI checks or other verifiable outcomes give the best results.

Next

The plan is only as good as the task behind it. The next lesson is about writing a task Devin can finish.