Task

Task is Enia's execution engine. When you click Apply on a Signal card or ask Enia to make code changes in Chat, a Task is created to execute the work in the background.

How Tasks Work

Task Creation

Tasks are created from two sources:

Source	Trigger	Example
Signal	Click Apply on a Signal card	Applying a security fix
Chat	Ask Enia to modify code	"Refactor this function to use async/await"

Task States

Queued → Running → Finished / Failed / Stopped

State	Description
Queued	Waiting to execute (tasks run sequentially)
Running	Currently executing
Finished	Completed successfully
Failed	Execution encountered an error
Stopped	User cancelled the task

Note: Only one task runs at a time. Others wait in the queue.

Task Actions

Available Actions

State	Actions
Queued	[@] Reference in Chat, [Del] Delete
Running	[@] Reference in Chat, [Stop] Cancel
Finished	[@] Reference in Chat, [Undo All] Revert, [Redo] Re-run, [Del] Delete
Failed	[@] Reference in Chat, [Undo All] Revert, [Redo] Retry, [Del] Delete
Stopped	[@] Reference in Chat, [Undo All] Revert, [Redo] Retry, [Del] Delete

Understanding Actions

[@] Reference in Chat: Opens Chat with the task context pre-filled. Use this to discuss or iterate on a task.

[Undo All]: Reverts all file changes made by this task back to their pre-task state.

Warning: Undo All requires confirmation. If you made manual edits during task execution, those edits may also be reverted.

[Redo]: Re-runs the task from the beginning.

[Stop]: Cancels a running task. Partial changes remain applied.

Command Confirmation

When a task needs to run shell commands (like npm install), it pauses for your approval:

Button	Action
Run	Execute the command
Run for Task	Execute and auto-approve similar commands for this task
Skip	Skip this command, continue with next step

Request Consumption

Each task execution is dynamically priced based on task complexity.