# Asking about a Task --- A Task's page has an **Ask** tab. It opens a conversation with an agent that has read the Task — what was asked, what each run did, what the review and QA found — and its code. Use it to understand a result — _"why did the review flag this?"_, _"what did QA check for criterion 2?"_, _"why did the run fail?"_ — or to work out what to change. It is an ordinary Assistant [session](/docs/assistant/what-is-a-session/), tied to the Task. ## Opening it The tab appears once the Task's first run has finished, whatever its outcome — succeeded, failed, no changes or stopped — and stays while a re-run is in progress. A Draft has no Ask tab, nor does a deleted Task. The tab reads: "Ask an agent about this Task: how it was implemented, what the review and QA found, why something failed." Click **Ask about this Task**. As with any session, the first answer can take a few minutes while the agent gets set up. The message box reads: "Ask how this Task was implemented, what the review and QA found, or what to change". Asking needs the same permission as starting or re-running a Task. Each person has one open Ask session per Task: opening the tab again returns to it. It ends like any session (see [Sessions end on their own](/docs/assistant/running-a-session/#sessions-end-on-their-own)); then **Start a new Ask session** starts another. **Open on the Assistant page** opens the same session there. ## What the agent reads The Task's record: its title, description, spec and acceptance criteria; each repository's branches, pull request and its state; and its runs, oldest first (the newest 10). Each run comes with the agent's summary, the files it changed, the review and what it fixed, QA's verdicts, the build and test checks, what happened in order, the run's log and the feedback a re-run was given. A long log keeps its newest 1 MiB; the agent says so when an answer depends on a part that was cut. For a Task that [deploys after merge](/docs/tasks/deploy-after-merge/), also each repository's deploy — the service it deploys to, its status and the reason, the commit that went out, the variables it was missing, and the deploy's build log (its newest 1 MiB) — and the QA run on production, with its verdict for each criterion and its log. It doesn't have the deployed service's own logs. The code: each repository is checked out at the Task's branch while its pull request is open, otherwise at the base branch, which holds a merged change. The agent can read the code and its git history, but can't change either. See [It won't touch your code](/docs/assistant/what-is-a-session/#it-wont-touch-your-code). The record is read once, when the session starts. A run or a deploy that finishes later isn't in it: start a new Ask session to ask about it. The agent and model are the Task's own. A Task that runs on opencode is asked about with your organization's default model instead, because opencode has no interactive sessions. ## Changing what the Task did Ask for a change while none of the Task's pull requests has merged, and the agent ends its answer with feedback for the agent that will make it. **Re-run with this feedback** opens the Task's [re-run](/docs/tasks/creating-and-running-a-task/#stop-re-run-delete) dialog with that feedback in its box; edit it, then click **Re-run with feedback**. The button is offered only when the Task can be re-run and isn't running. A session that started before the Task's latest run doesn't offer it, because it hasn't seen that run; the tab says: "This session started before the Task's latest run, so it hasn't seen that run and won't offer a re-run. It ends after 30 minutes without a message; then start a new Ask session." Once that session has ended, the tab says instead: "This session started before the Task's latest run, so it hasn't seen that run. Start a new Ask session to ask about it." The dialog's allowed hosts aren't filled in from an Ask session; that happens only from the Task's **Re-run with these hosts**. Once one of the Task's pull requests has merged, or for new work beyond this Task, the agent writes a spec instead, as in any session. **Create task** under it turns it into a new Draft Task (see [From Spec to Task](/docs/assistant/from-spec-to-task/)). Converting closes the Ask session. --- Source: https://deployment.io/docs/tasks/asking-about-a-task/