Creating a task
Type your request into the composer on the home screen. Twill picks the repository (or repositories) at runtime from your connected repos — you don’t select one up front. The composer also gives you:- Agent & model — which coding agent runs the task (Claude Code, Codex, or OpenCode) and at what reasoning effort. Defaults come from your routing configs.
- Attachments — drop in screenshots, specs, or data files for the agent to reference.
- Voice input — press Alt+Space to dictate a task.
- Skills — type
/to insert a repository skill from your codebase.
Modes
| Mode | What it does |
|---|---|
| Agent | Implements the change and opens a PR. The default. |
| Plan | Researches first and posts a plan for your approval before writing code. See Plans & questions. |
| Ask | Answers questions about your codebase. Read-only, no PR. |
| Dev Env | Sets up or repairs the workspace dev environment. Changes persist for future tasks. See Your dev environment. |
| Schedule | Turns your prompt into a recurring automation. |
Following up
Reply in the task thread — in the web app or wherever the task started — and Twill continues with full context. Follow-ups reuse the task’s existing agent and environment, so iterating is fast: “also handle the empty state”, “the test you added fails on CI, fix it”, “revert the copy change”. When a PR linked to a task gets merged, the task is marked Completed automatically.Tracking progress
The task view streams the agent’s activity live: what it’s reading, running, and changing. From the task header you can also:- Open the live preview of the running app inside the task’s sandbox.
- SSH in from your terminal, VS Code, or Cursor to inspect or take over.
- Cancel a run that’s heading the wrong way — then follow up with a correction.