Vector OS
Join the beta ↗
← Back to guides

Workspace

Ask, Plan and Build

Choose whether to understand, prepare a change or apply an exact reviewed native plan.

Before you begin

  • A local project and Agent, a clear task, and reviewed selected context.
  • The intended personal/team scope and an acceptable bounded estimate.
  • For native work, a fresh eligible host/document connection.

Follow the steps

  1. Choose Ask to understand

    Select Ask for explanation or eligible read-only inspection. State the question and select only necessary context.

    Checkpoint: The request seeks information without authorizing a native model change.

  2. Choose Plan to inspect a proposal

    Select Plan when you want to review targets, dimensions, parameters or output before an effect. Make the requested change finite and explicit.

    Checkpoint: A proposal or immutable native plan can be inspected; no native changes are committed by planning.

  3. Check context, scope and estimate

    Review selected inputs, model/profile, included/omitted history and the wallet for this request. Resolve changed required context before Send.

    Checkpoint: The persisted request has one intended scope and frozen context.

  4. Send once and read its state

    Send the prepared request once. Read whether it is queued, running or awaiting approval. Additional messages remain FIFO pending items until admitted.

    Checkpoint: A request identity and structured state distinguish queued work from provider-running work.

  5. Use Build only with the exact approval

    Review the current native plan in Build. Check its host/document, targets, units, outputs and expiry, then approve once. Reject and replan if the document or requested arguments changed.

    Checkpoint: Only the frozen approved change can be dispatched. Streamed text or an incomplete tool proposal does not execute.

  6. Read the result at the right level

    Separate the model response, native receipt and artifact receipt. Stop requests future cancellation; it is not an Undo control.

    Checkpoint: A native task is only described as verified when the host readback establishes its intended effect.

Check the result

  • The chosen mode matches the task and only a current, explicit native approval permits a bounded change.
  • A completed model response, verified host effect and engineering acceptance are different outcomes.

If something goes wrong

  • A request is still queued.

    Edit or remove only undispatched items through the queue controls. Do not treat waiting as proof that an earlier active run stopped.

    Resume from: Known queue/run state.

  • Approval becomes stale or the task reaches a bounded stop.

    Review the current document/context and choose whether to continue explicitly. Do not assume automatic paid continuation.

    Resume from: Fresh plan or explicitly admitted continuation.

  • A run fails after a possible native dispatch.

    Preserve its operation reference and reconcile the effect before a replacement Build.

    Resume from: Original outcome, then a distinct safe new intent.

Need help?

Include your step and this reference.

Vector OS guide: /tutorials/ask-plan-build

Open Support

Guide updates

Ask, Plan and Build

Revision b6cd397c565a88afcb661aeeb2ecd6c96b61405b3f958f0d27a8339ae07c921a ·

Choose whether to understand, prepare a change or apply an exact reviewed native plan. The public workflow illustration changes only its illustration. Real Ask, Plan and Build require an eligible app, account and admitted capabilities. 1. Choose Ask to understand: Select Ask for explanation or eligible read-only inspection. State the question and select only necessary context. 2. Choose Plan to inspect a proposal: Select Plan when you want to review targets, dimensions, parameters or output before an effect. Make the requested change finite and explicit. 3. Check context, scope and estimate: Review selected inputs, model/profile, included/omitted history and the wallet for this request. Resolve changed required context before Send. 4. Send once and read its state: Send the prepared request once. Read whether it is queued, running or awaiting approval. Additional messages remain FIFO pending items until admitted. 5. Use Build only with the exact approval: Review the current native plan in Build. Check its host/document, targets, units, outputs and expiry, then approve once. Reject and replan if the document or requested arguments changed. 6. Read the result at the right level: Separate the model response, native receipt and artifact receipt. Stop requests future cancellation; it is not an Undo control.
Get helpCheck release status