Skip to main content

​
Overview

When Dexter takes on anything non-trivial, it works out loud. Three surfaces make that visible in the conversation: the task list, goal approval, and question prompts. Together they let you follow what Dexter is doing, catch problems before they land, and answer the questions Dexter needs answered — without ever guessing at hidden state. This page walks through each one: where it lives, what it looks like, and how to respond.

​
The Task List

For any multi-step effort — cleaning a dataset, building out a simulation model, comparing a set of scenario runs — Dexter creates a task list so you can see the plan and its progress in real time. Where it lives. A Tasks chip in the dock just above the chat input box, with a count of completed tasks, so the current plan stays in view while you type. Click the chip to expand the full list; reports generated in the conversation sit alongside it under a Reports chip. What you see per task. Each task has a short, plain-language title (“Validate cycle times against historical data”, “Build the paint-line model”) and a status:
  • Pending — queued, not started yet.
  • In progress — Dexter is actively working on it (one at a time).
  • Completed — done.
A task can declare a dependency on another; Dexter won’t pick it up until the prerequisite is done. How it updates. Dexter flips a task to In progress the moment it starts, and to Completed the moment it finishes — not in a batch at the end. If Dexter hits a blocker mid-task, it creates a new task for the blocker and links it, rather than silently abandoning the work. If a pre-planned list turns out to be wrong, Dexter clears it and rewrites one that matches the actual work.
The task list is editable through chat. If you see a task that shouldn’t be there, or one missing that should be, say so — Dexter will restructure the list.

​
Goal Approval

When you set a goal, Dexter first shapes it with you and then presents it once as a Goal proposal card, shown right where you’d type your next message. The card states the goal and the criteria Dexter will check to know it’s done. How to respond.
  • Approve & start goal — Dexter starts working toward the goal.
  • Request changes — opens a comment field. Say what needs to change; Dexter revises the goal and proposes it again.
  • Cancel — closes the card without a decision. It’s recorded as Review dismissed, and no goal is set.
A small card stays in the conversation as the record of your response and shows the goal directly. For a long goal, use Show full goal to expand it. After you approve, Dexter doesn’t ask you to approve the goal again; it keeps working until it has verified the goal is done.

​
Question Prompts

When Dexter needs input from you, it uses a structured question, which takes the place of the message box until you answer. How often Dexter asks depends on the response mode. Four shapes: The freeform field is always there on select-type questions — you don’t need an “Other” option in the list. Sign-offs on produced work. When Dexter needs you to check a finished piece of work — a completed analysis, derived numbers, a plan that would be costly to unwind — it shows the work first, in its reply, in a report, or as the artifact itself in the platform, then asks a short approval question. Look at the work before you answer; reject with a comment to send it back. Batches. Dexter may ask several questions in one card when they’re related and independent — step through them (“Question 1 of 3”) and they’re sent together. If one question only makes sense after another is answered, Dexter asks the first batch, then a follow-up shaped by your answers.
You don’t have to answer right away. Minimize a question to read back through the conversation first, attach a file with Attach if the answer is a document, or Dismiss it — Dexter is told you declined and finds another way forward, such as rephrasing the question or raising the gap in chat.

​
Limits

  • Tasks are per-conversation. A fresh conversation starts with an empty list.
  • Goal proposals and questions are pause points. While one is waiting on you, Dexter has paused and won’t continue until you respond.
  • Long conversations shed early context. Questions answered long ago may need re-answering in a fresh conversation — or, better, move the answers into Memories or Rules so every future conversation starts with them.
There is no undo on an approval. If you approved something that shouldn’t have landed, tell Dexter — it will roll the change back where possible, or you can roll the factory back to a saved version. Some changes, such as files already exported, can’t be undone.