Questions and confirmations

Clarification supplies information

The Assistant asks a clarification when it cannot safely bind required input. The CLI can present several questions as one batch so you can answer the complete set before Elyxis resumes the pending work.

Give direct answers in the same order. If you do not know an answer, say so and ask for eligible options instead of inventing a value.

Confirmation authorizes a change

A confirmation is a separate safety boundary. It should identify the proposed action and enough context for you to judge it.

Examples include:

• creating or updating a resource;
• changing selected durable session context;
• archiving, restoring, or deleting something; and
• another tool mutation that requires approval.

Approve deliberately

Type y or yes only when the displayed action matches your intent. The server retains the proposed action and approval replays that action; the Assistant should not re-plan a different mutation from the word “yes.”

For a session-context confirmation, approval applies the displayed selection. For a tool mutation, approval executes the retained tool input once and the final response reports its outcome.

Reject or revise

Press Enter, type n, or leave the interaction to reject. Rejection means the proposed change should not execute.

To revise:

1. reject the current confirmation;
2. state the correction precisely;
3. review the newly proposed action; and
4. approve only if the new confirmation is correct.

Expired or repeated decisions

Pending confirmations are not permanent. If a confirmation expires or has already reached a terminal decision, issue the original request again and review the newly proposed action. Do not assume a repeated “yes” will reuse old pending state.