Tasks & AI

Queue & Steer

Separate follow-up work from corrections.

Prepare a follow-up for later or adjust the current task while it runs.

01
Follow-up messages sit compactly above the composer.Actual Linqbase interface · demonstration project
TURN IDEAS INTO POSSIBILITIES

Separate follow-up work from corrections.

When work is already running and you want to add information.

A new idea during an active task might be a next step or a correction to the current step. Queue and Steer make that distinction explicit.

Queue holds a message for later. Steer delivers new context at a point the running engine can handle. Reorder, edit or remove pending messages in the compact queue.

YOUR NEXT STEP

How to get started.

From your first choice to the result. Here is how to use this feature in your own project.

  1. 01

    Choose Queue to process the message after the current task.

  2. 02

    Choose Steer to provide information during execution, where supported by the engine.

  3. 03

    Edit, remove or reorder queued messages. A waiting message can also be sent as an immediate steer.

IN PRACTICE

How it could work for you.

Queue the contact page for later, but steer immediately when the phone number is wrong.

How to assess the result

Steering does not instantly interrupt every command. Check when the instruction was received.

GET STARTED IN LINQBASE

Where to find it.

Composer → Chat settings → Follow-up behaviour; queue above the composer

Available actions depend on your plan, mode and project state. Features that require a task become available within an appropriate conversation.
SAVE & CONTINUE

What is saved?

Waiting messages and their order are saved with the conversation.

GOOD TO KNOW

What you need to know

Steering is processed when the engine can accept it. An already running command cannot always be interrupted immediately.