# How Taskade EVE Plans, Asks, and Acts
> See what Taskade EVE is doing while it builds your app: live tool calls, self-planned todos, clarifying questions, and automatic sign-in detection.
- Source: https://www.taskade.com/learn/genesis/eve-reasoning
- Section: Taskade Genesis
- Updated: 2026-09-22
- Index of all pages: https://www.taskade.com/learn/llms.txt
## Overview
When you ask Taskade EVE to build something, the work happens in front of you. A plan appears at the top, tools light up as they run, and any uncertainty turns into a clarifying question instead of a wrong guess. Nothing happens off-screen.
> **TL;DR:** Three signals tell you what [Taskade EVE](https://www.taskade.com/learn/agents/eve-assistant) is doing during a Taskade Genesis build: a self-planned todo list, tool-call cards inline, and an Ask Questions card when the request is ambiguous. Sign-in is detected automatically when your app needs it. Together they keep every build legible.
## The build loop in one picture
Three signals run in a tight loop while Taskade EVE works. You can interrupt any of them.
```mermaid
flowchart TD
PROMPT[Your prompt]:::input --> PLAN[Self-planned todos
numbered, each step status-tracked]:::plan
PLAN --> CALL[Tool-call cards
edit · search · integrate · preview]:::call
CALL --> ASK{Ambiguity?}:::ask
ASK -- yes --> Q[Ask Questions card
1-3 short choices]:::q
Q --> CALL
ASK -- no --> AUTH{Needs accounts?}:::auth
AUTH -- yes --> SIGNIN[Auto-offer GenesisAuth
one click to enable]:::signin
AUTH -- no --> DONE[Plan recap
+ versioned snapshot]:::done
SIGNIN --> DONE
classDef input fill:#11111b,color:#cdd6f4,stroke:#00d4aa
classDef plan fill:#0d1b2a,color:#7dd3fc,stroke:#38bdf8,stroke-width:1.5px
classDef call fill:#0d1a0e,color:#86efac,stroke:#22c55e,stroke-width:1.5px
classDef ask fill:#1a140a,color:#ffb74d,stroke:#e65100,stroke-width:1.5px
classDef q fill:#1a140a,color:#ffb74d,stroke:#e65100
classDef auth fill:#1a0d24,color:#ce93d8,stroke:#6a1b9a,stroke-width:1.5px
classDef signin fill:#1a0d24,color:#ce93d8,stroke:#6a1b9a
classDef done fill:#2a1225,color:#ff8fa3,stroke:#ff2d60,stroke-width:2px
```
Here is what each signal looks like on screen.
| Signal | When it shows | What you see |
| --- | --- | --- |
| Self-planned todos | At the start of a build | A plan card, each step marked pending, in progress, or completed |
| Tool-call cards | On every action Taskade EVE takes | Inline cards that fold into one summary row when the run finishes |
| Ask Questions card | When your request is ambiguous | Multiple-choice questions, one at a time, with a Something else box |
## Self-planning todos
Open any new build and the first thing you see is a plan card. Taskade EVE writes a numbered todo list before it touches a single file.
Each step shows its status: pending, in progress, or completed. Read the whole plan in five seconds and decide whether the direction is right. If it is not, stop the run and rewrite the prompt. You have not lost any work yet.
The Taskade Genesis build window shows the same plan while your app builds. Its **Plan** list marks each step as Taskade EVE works through it. Its **Built so far** list names each project, agent, automation, and file as it lands. A step that needs a fix shows as **Fix needed**.
The plan stays in the thread, so you can scroll back and compare what shipped against what was listed. To agree on the plan before anything is generated, start the prompt with `/plan`. See [Taskade EVE Slash Commands](https://www.taskade.com/learn/genesis/eve-commands) for the full reference.
## Tool-call cards
Every action Taskade EVE takes shows up as a card in the chat thread.
- Edit a page, component, or style.
- Search your workspace for matching content.
- Call an integration like Slack, Stripe, or Google Calendar.
- Render a preview of what changed.
Each card surfaces the input, the result, and a one-line summary. If a tool call fails, the card carries the error and the next attempt right next to it. You never have to dig into logs to figure out what changed. Read [Tools for AI Agents](https://www.taskade.com/learn/agents/agent-tools) for the wider tool catalog.
When a run of steps finishes, its cards fold into one summary row. The row counts what the run made, for example **Built in your workspace · 1 project, 2 files**. It also adds an error count when a step failed. Short notes between steps fold into the same row.
- Click the row to open every card in the run.
- A card that waits for your approval stays open.
- If a run has one step and that step fails, its card opens on its own.
- A row that you open or close stays that way.
## Ask Questions when unclear
If a prompt has more than one reasonable interpretation, Taskade EVE pauses. Instead of guessing, it asks multiple-choice questions in a single card, one question at a time. Pick an option, pick several when the card says **Select all that apply**, or open **Something else** and type your own answer. Click **Skip** to let Taskade EVE decide. The build resumes inside the same thread.
Common triggers: which calendar to use, which currency to display, who the audience is, whether the app is public or gated. The full flow lives in [Ask Questions](https://www.taskade.com/learn/genesis/eve-ask-questions).
## Automatic sign-in detection
When the app you described needs end-user accounts, like a CRM portal, a course hub, or an internal tool, Taskade EVE notices and offers to enable sign-in. One click adds [GenesisAuth](https://www.taskade.com/learn/genesis/genesis-auth) to the right pages and turns every visitor into an [App User](https://www.taskade.com/learn/genesis/app-users) you can manage.
Decline the offer and Taskade EVE keeps the app fully public. You can flip the choice later without losing data.
## Stop, redirect, or rewind
You stay in control through the whole run.
1. Click **Stop** to end the current run immediately.
2. Type the correction as your next message. If Taskade EVE is still working, press **Enter** to queue it under **Up next**. The message goes out when the current turn ends, and Taskade EVE works from the new instruction.
3. Open [version history](https://www.taskade.com/learn/genesis/version-history) to roll back to an earlier state.
Because every change lands as a versioned snapshot, exploring is cheap. Try the bold idea, compare it side by side, and revert in one click if it does not work.
## Why this matters
Most AI build tools treat reasoning as private. Taskade EVE treats it as a product surface. You can show a teammate the plan, screenshot the tool-call trail for review, or hand the whole thread to a stakeholder as documentation. Transparency is the feature.
## Related guides
- [Taskade EVE Assistant](https://www.taskade.com/learn/agents/eve-assistant). The meta-agent overview
- [Taskade EVE Slash Commands](https://www.taskade.com/learn/genesis/eve-commands). Drive Taskade EVE with `/build`, `/plan`, `/automate`
- [Ask Questions](https://www.taskade.com/learn/genesis/eve-ask-questions). How clarifying cards work
- [Edit Apps Visually with the Element Selector](https://www.taskade.com/learn/genesis/visual-editor). Click any element and edit with a prompt
- [Taskade EVE Memory](https://www.taskade.com/learn/genesis/eve-memory). Persistent memory across builds
- [Tools for AI Agents](https://www.taskade.com/learn/agents/agent-tools). The full tool catalog