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 while a turn is running, pending steps wait. The plan updates as Wingtip learns more, and you can collapse it.
• The activity card - each turn’s commands and file operations fold into one collapsible card. 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. Back returns to the approve buttons without sending.

Allowing and denying actions

On the default Manual posture, Wingtip asks before sensitive actions. Approval requests dock just above the composer:

• A single request reads “Wingtip wants to run {tool}.” with Approve and Deny. Where the action has a consequence worth stating - creating a Pylon agent that will then run on its own schedule, for example - the request says so in full instead of naming the tool.
• Some actions also offer Accept always, which approves this kind of action from now on without asking. The row then reads Always accepted.
• Multiple requests stack under “{n} actions need your approval” with an Approve all shortcut; each decided row shows Approved, Always accepted, or Denied. A batch is only sent once every row has been decided, and Approve all leaves any row you already denied denied.

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

Whether you are asked at all is governed by the approval posture selector beside Plan first in the composer: Manual asks; Bypass permissions does not. Manual is the default, and the setting is durable - it applies to all of your Wingtip sessions, not just this one, until you change it. Which postures the selector offers is controlled by your organization, so Bypass permissions may not appear for you.

One thing Manual does not undo: an action type you previously approved with Accept always stays accepted and will not prompt again. Manual governs whether Wingtip asks in the first place, not the choices you have already made permanent.

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. The questions and your answers stay in the transcript afterwards, so the exchange is still there when you scroll back.

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.” A queued message can still be edited or removed before it sends.
• Stop a run with the stop button (it replaces Send while Wingtip is working and the box is empty).

What you can’t change mid-session

The start-screen options - role, template, document template, data source, connectors, skills - are read once at session start. To work with different options, select New chat in the sidebar and start a fresh session. Templates are the exception: the rail’s Templates panel can apply one to the session you are already in, so you do not need a new chat just to use a template. 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.
• Session history: your Wingtip sessions are listed in the left sidebar under the Wingtip navigation rows, with the open one highlighted. Select a row to reopen it. The row menu renames the session (or double-click the title, where your organization has inline rename enabled) and deletes it; the delete dialog is titled Delete conversation? and warns “This will hide the conversation from your list. You cannot undo this action.”

Next steps

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