
c
. Creating a task adds it to your kanban board without automatically starting a coding agent.
Using Templates

- Click the Use a template dropdown
- Choose from available global or project templates
- The template automatically populates the task title and description
Templates save time by reusing common task structures. Learn more about creating templates in the Task Templates guide.
Starting Your First Task Attempt

1
Select your agent profile
Choose from available agents (e.g., CLAUDE_CODE, GEMINI, CODEX). Your default configuration from Settings is pre-selected.
2
Choose a variant
If your selected agent has variants, pick the appropriate one (e.g., DEFAULT, PLAN).
3
Set the base branch
Specify which branch the agent should work from. Your current branch is selected by default.
Use Create & Start to add the task and immediately create a task attempt with your default settings in one action.
What Happens During Execution
- Setup Scripts Run: Any setup script defined in your project settings runs automatically
- Agent Execution: The coding agent processes your task using the title and description
- Real-time Monitoring: Watch progress through streaming logs in the task interface
- Follow-up Questions: Continue the conversation after execution to refine results
For detailed task management after execution, see Task Details Full Screen Mode. To understand when you might need multiple attempts, see Creating Task Attempts.
Creating Tasks via MCP Clients
This is not the typical method for creating tasks but can be valuable for bulk task creation or migrating from other systems.
- Bulk task creation based on existing data or project specifications
- Migration from other systems like Linear, GitHub Issues, or Jira
- Automated task generation from project plans or requirements documents
For detailed setup instructions and examples, see the Vibe Kanban MCP Server documentation.
Example MCP Task Creation
Once configured with an MCP client, you can create multiple tasks from a project description:Understanding Task Columns
Tasks begin in the “To do” column and move automatically based on their progress:Action | Column |
---|---|
Task created | To do |
Task attempt started | In Progress |
Task attempt completed (success or failure) | In Review |
Task attempt merged | Done |
PR merged on GitHub | Done |
You can manually drag tasks between columns, but this won’t trigger any functionality. Task movement is primarily driven by coding agent actions and GitHub integration (which polls every 60 seconds).