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.

Accessing Task History

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

Browsing and Filtering

Search

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.

Sort Order

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

Filter by Workspace

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

Archived Sessions

Toggle Archived sessions to show sessions you have archived. Archived sessions are hidden from the normal history list but are not deleted automatically.

Favorites

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

Task Actions

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.
• Rename — change the title shown in history and recent-session surfaces.
• 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.
• Archive / Unarchive — hide the task from the default history view or restore it from the archived view. Archiving keeps the session data on disk and does not schedule it for deletion.
• Delete — remove the task and its stored data. This action applies only to the selected task.

Starting a New Task

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

Local 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.

Worktree Mode

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).
• Resume an existing worktree: the footer’s worktree menu lists the repository’s existing worktrees below New worktree — pick one to resume it. The new chat then runs inside that worktree, keeping its branch and uncommitted changes, instead of branching a fresh one. (The keep-limit cleanup below can still remove an aged worktree, so resume one before it is reaped.)
• 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.
• Worktrees are kept after the task ends, after you undo its changes, and after you delete the chat — a worktree you started is never auto-removed for those reasons.
• When Automatically delete old worktrees is on (default), the keep limit (default: 15) is a hard cap: starting a new worktree force-removes the oldest worktrees beyond the limit, including any uncommitted or unmerged work in them. Only a worktree a running task is currently using is spared, and the same prune runs on startup. Turn the setting off to manage worktrees yourself.

Working directory

The working-directory selector in the chat input footer (to the left of the local/worktree menu) sets the folder a new session runs in. It defaults to the opened workspace folder.

• The button shows the working folder’s name. The menu lists the opened workspace folder(s), your recently-opened folders (the same list shown on the Welcome screen), and a Browse for folder… entry that opens your operating system’s folder picker — so you can point a session at any folder on your machine, including one outside the workspace.
• The chosen folder becomes the session’s working directory: every tool the agent runs (file reads/writes, terminal commands, glob, search) operates relative to it.
• The choice is persisted with the session (resuming restores it) and resets to the workspace default after you send, so a one-off folder choice never leaks into the next session.
• With worktree mode, the worktree is created from the chosen folder’s Git repository.
• If the chosen folder no longer exists when the session starts, it falls back to the workspace folder and tells you.