DocsCore

Tasks

A task is a single AI request — KingCoding's smallest unit of work.

Anatomy of a Task

A task is one request you hand to an AI. It lives inside a project, moves through a status flow, and stays in history once finished.

  • Running — the AI is actively coding
  • Waiting for reply — the AI is asking you something
  • Awaiting review — the AI has produced a result and waits for your sign-off
  • Completed — you marked it done

Creating a Task

  • Click "New Task" on the project page
  • Describe what you want in plain language
  • Pick the provider (Claude Code / Codex)
  • Tweak the model and permission mode if needed
  • Hit Run

Execution Modes

Tasks support several modes that change how the AI behaves.

  • Run — fully autonomous mode with code changes and execution
  • Plan — proposes a plan first, runs after you approve
  • Ask — answers questions without touching code
  • King — planning, execution, and release for larger projects

Controls While Running

From the task detail screen you can:

  • Pause — interrupt the AI (resumable)
  • Resume — continue from a pause
  • Cancel — abort the task (with a confirmation dialog)

Follow-ups and Replies

When the AI is waiting for a reply, you answer right in the chat. You can also send extra instructions while it's running — "oh, also do X" — and it will pick them up at the next turn.

Attaching Files and Images

Drag and drop images or files into the task or follow-up input. The AI reads them as reference material. Mobile remote works the same way.

How Completion Works

When the AI proposes a result, the task is not done until you press "Complete". Look at the diff and reply with more changes if you need them — the same task keeps going.

Completed tasks move to the dashboard's "Completed" tab where you can revisit their history any time.