docs/core-features/monitoring-task-execution.mdx
When you start a task, the main panel provides real-time visibility into everything happening during execution. Watch as agents think through problems, take actions, and respond to your feedback.
<Frame> </Frame>When you start a task attempt, Vibe Kanban orchestrates several steps to create an isolated environment and execute your task:
Vibe Kanban uses Git worktrees to create isolated environments for each task attempt. These environments are ephemeral and automatically cleaned up after execution completes.
<Info> Worktrees ensure task attempts don't interfere with each other or your main working directory. </Info>The first log you'll see is your project's setup script running (if configured). This installs dependencies and prepares the environment before the agent starts working.
Your task title and description are sent to the agent. You'll see this as the initial message that kicks off the work.
As the agent works, each action appears in real-time:
Expandable actions: Click on file change actions to expand them and see exactly which part of the file was modified.
When an agent takes an action that requires human approval, a row appears below the action with approve/deny buttons.
<Frame> </Frame>Click the tick to approve or the cross to deny the action. The agent will proceed or adjust based on your decision.
After every agent turn, your cleanup script runs (if configured). This is useful for running linters, formatters, or other post-execution tasks.
Vibe Kanban generates commit messages based on the last message sent by the agent. These automated messages may not always be the most descriptive.
<Tip> When merging to your base branch, use GitHub's "squash & merge" option to rewrite commits with a summary of what actually changed. Alternatively, ask your coding agent to clean up commits manually. </Tip>Click the task title in the top left to navigate to the task view.
<Frame> </Frame>This lets you:
When supported by your coding agent, you can edit previous messages in the conversation. This will revert the agent's work to that point and replay the conversation with your edited message.
<Warning> Editing a message reverts all subsequent agent work. Use this carefully when you need to correct or clarify earlier instructions. </Warning>Click the triple dot icon in the top right and select View Processes to see all running and completed processes.
<Frame> </Frame>This shows:
Each process displays its status and execution timeline. Click any process to view its specific output logs.
<Tip> For development server logs, the recommended way to view them is through [Testing Your Application](/core-features/testing-your-application) where you can see logs alongside the live preview. </Tip>