Skip to content
WhoseDev logoWhoseDev Docs

WhoseDev Agent

The WhoseDev Agent is the assistant in the side panel that can investigate your codebase, plan work, and make changes when you choose that mode. It combines instructions (your mode, rules, and project context), tools (file search, edits, terminal, and more), and the model you select.

How Agent works

Section titled “How Agent works”

Each turn, the agent receives your message plus workspace context according to your settings. It can call tools in a loop until it completes the task or needs your input. Tool calls appear in the activity timeline so you can follow what happened.

The agent respects the execution mode you choose for that turn:

Mode Mutates files Typical use
Ask No Explore, explain, and answer questions
Plan No (produces a plan artifact) Research and draft an approach before coding
Act Yes Implement, refactor, run commands, and verify

See Ask, Plan, and Act for mode selection and Planning workflow for the full plan-to-build path.

Switch modes

Section titled “Switch modes”
  • Press Shift+Tab while the chat input is focused to cycle Ask → Plan → Act → Ask.
  • Pick a mode from the composer dropdown.
  • Use Alt+1, Alt+2, or Alt+3 to set Ask, Plan, or Act in an agent session.

Model selection

Section titled “Model selection”

Use the model picker in the chat composer. Available models depend on your route (WhoseDev Cloud, direct provider, or local Ollama), your subscription, and workspace policy. Ask, Plan, and Act stay in the mode picker; a Cloud turn can still fail if that mode is not included. When Auto is available for managed cloud agent runs, WhoseDev can route to a capable model for the task. Greyed models may require another plan, be blocked by workspace policy, or be unsupported here.

See Models and routing.

Stay in control

Section titled “Stay in control”
  • Use Ask or Plan when you want to review before anything changes.
  • In Act, inspect diffs and terminal output before accepting results. See Editor basics — Review changes.
  • Turn off web research when you do not want the agent to search or fetch public pages.
  • Configure context settings to limit what workspace material is sent with requests.
Section titled “Related topics”