Skip to content

Task Management

As you use Kodik, every conversation is saved as a task. The task history panel lets you navigate past work, pick up where you left off, and keep things tidy.

See Agent Overview for how tasks are structured.

Click the History button in the Kodik sidebar to open the task history panel. Tasks are sorted newest-first by default.

Image

The search bar filters tasks by their initial message text or by the workspace path they were started in. Searches are case-insensitive and match substrings.

Image

Switch between Newest (default) and Oldest to change the sort order. Results are paginated; scrolling loads the next page automatically (100 tasks per page).

Toggle Current workspace only to see only the tasks that were started in the workspace you have open right now.

Star a task to add it to your favorites. Toggle Favorites only to see only starred tasks.

Each task in the history list has the following actions:

  • Open — resume the task in the Kodik chat. The agent’s conversation history, file state, and model are restored to where the task was last left.
  • Export — save the full API conversation transcript as a Markdown file. The export includes all messages, tool calls, and tool results from the task’s history.
  • Delete — remove the task and its stored data. Favorited tasks are protected: they are skipped by bulk-delete operations unless you explicitly include them.

Click New Task (or use the keyboard shortcut) to start a fresh conversation. You can choose the workspace mode:

The agent works directly in your current workspace, reading and writing files in place. All changes are visible immediately in your editor alongside any other work in progress.

Kodik creates a dedicated Git worktree for the task under the .worktrees/ directory at your repository root. The agent works inside that isolated branch, so its changes are completely separate from your main working tree until you decide to apply them.

  • Requires at least one Git commit in the repository (the worktree is branched from HEAD).
  • The branch name is generated from the task title, prefixed with kodik/ by default (configurable via kodik.git.branchPrefix).
  • While the task is active, the composer shows a Worktree badge. Open it to see the worktree name and reveal the folder in Explorer.
  • Review actions such as Keep and Keep all accept pending review state inside the task worktree only; they do not patch your main checkout.
  • To bring work back to your main branch, use the worktree folder/branch with normal Git workflows.
  • Clean inactive worktrees are pruned automatically (default: keep the 15 most recent). Active worktrees and worktrees with uncommitted or task-only work are preserved.