Your first Agent Dev session

From a fresh install to a working local agent: run the setup checks, let the guided terminals install and sign in your provider, watch the readiness indicator turn green, and send your first prompt.

Your first Agent Dev session, start to finish

What you need

From install to first prompt

  1. Open Agent Dev

    Sign in, pick Agent Dev on Wingman Home, and press Resume Agent Dev. The window switches to the full workspace: the chat panel on one side, the embedded dashboard on the other.

  2. Run the Get Started checks

    The first time you enter a workspace, the dashboard opens the Get Started setup modal. It checks terminal-agent readiness — whether a coding CLI is installed and signed in — and points you at anything missing. You can rerun the same checks any time from the Welcome page or the /onboarding page.

  3. Let the guided setup work

    If a provider is missing, the panel opens guided terminals for it: one for the install command, one for the CLI sign-in. Run what each terminal shows, then close it — Agent Dev re-checks when the terminal closes and moves on from there. Leaving it open holds the check. No pasting status back and forth.

  4. Watch the readiness indicator

    The small status indicator above the composer tells you where you stand without covering your draft. Only a compact green dot proves that the selected provider is ready. Amber checking or degraded dots are diagnostic, not proof of readiness; click one for details or a retry. When setup or repair is required, the indicator expands to a red Fix now button that opens the guided fix.

  5. Send your first prompt

    Type a goal in plain words and send it. The agent reads before it writes, plans before it acts, and asks before it runs anything — approvals are covered in Run the agent & review changes.

    prompt

    Look around this workspace and tell me how it is put together.
    Then suggest one small first task.
  6. Approve the Wingman connection

    The first time the agent uses a Wingman tool, an MCP OAuth approval link appears right in the panel. Open it, approve the sign-in in your browser, and come back — the session picks up where it left off. It is a one-time step, and the only sign-in the tools need: no tokens to paste.

After your first prompt