Steer a Running Wingtip Session

What you’ll accomplish

You’ll know how to read what Wingtip shows you while it works, and how to intervene: approve or reshape its plan, allow or deny individual actions, answer its questions, and recover when something interrupts a run.

Reading the session

While Wingtip works you’ll see, from top to bottom:

• The Plan card - a checklist headed Plan with an n/total counter. Completed steps get a check and strike-through, the current step spins, pending steps wait. The plan updates as Wingtip learns more.
• The terminal card - each turn’s commands and file operations fold into one collapsible card: amber spinner while running, green check when done. Expand it when you want the detail; ignore it when you don’t.
• The reasoning strip - Wingtip’s narration collapses into a “Thought for…” strip, collapsed by default.
• working… - the busy indicator. When you reopen an existing session you’ll briefly see Loading session….

Approving and changing plans

With Plan first on, Wingtip stops after planning and shows a card titled “{your plan} - ready to build?”:

• Approve & build - Wingtip executes the plan as written.
• Request changes - a notes box opens (“What should change about the plan?”). Describe the change and select Send changes; Wingtip revises the plan and asks again.

Allowing and denying actions

For sensitive actions, Wingtip asks first. Approval requests dock just above the composer:

• A single request reads “Wingtip wants to run {tool}.” with Approve and Deny.
• Multiple requests stack under “{n} actions need your approval” with an Approve all shortcut; each decided row shows Approved or Denied.

Denying an action doesn’t end the session - Wingtip works around it or asks you what to do instead.

Answering Wingtip’s questions

When Wingtip is missing a detail it renders a short form in the conversation instead of guessing - pick the options or fill the fields and it continues. This is normal and usually means a better result.

Replying, queueing, and stopping

• Reply any time. The composer placeholder changes to “Reply to keep iterating…” - corrections, additions, and new directions all go here.
• Type while it’s busy and your message queues: “Queued - sends when the current reply finishes.”
• Stop a run with the red stop button (it replaces Send while Wingtip is working and the box is empty).

What you can’t change mid-session

The wizard options - role, template, data source, connectors, skills - are read once at session start. To work with different options, select New in the top bar and start a fresh session. Two related settings live in your Profile on the Wingtip tab: your Default role, and a New-job options toggle that brings the option rows back if you previously chose “Don’t show this again.”

If something interrupts a run

• Connection dropped: “The connection to this run dropped before it finished. Your work is still running in the background - reload to see the latest.” Reload; the session resumes.
• Long idle: a session left idle pauses after about 15 minutes and resumes on your next message. Sessions resumed after a long gap replay the most recent turns of history, and keep the model they started with.
• History: the History dropdown lists your recent sessions (most recent 40). Deleting a session is permanent - the confirm dialog says so.

Next steps

• Download, share, and reuse results
• Run your first Wingtip session - if you landed here first