Arranging Your Work

Last updated: November 2026

Arrange the Dashboard so it shows the work you need to see. The Dashboard is a set of views, such as Todo and Tasks, and each view keeps its own arrangement. Above a view’s list, the toolbar has these controls:

• View opens a menu that sets the layout (List, Board, or Graph), the grouping, the sort, and the filters.
• The search box finds items in the list, and also takes filters. See Search.
• Panel layout arranges open panels side by side in 1 row, or in a grid of several rows. See Lay panels out in a grid.
• Refresh fetches the view’s items from your providers again.

What you choose in the View menu is saved to the view at once. To learn what each part of the screen is, see The Kepler Interface.

To open several tasks at once, use the open button on a section header, or Open group on one of your groups.

In a narrow window, the search box becomes a search icon. Click it, or press Cmd/Ctrl+F, to open the search box.

---

Views

Each view lists one kind of work:

• A Todo view lists pull requests and issues from your connected providers.
• A Tasks view lists your tasks.

Kepler starts you with a Todo view, a Tasks view, and an Agent Graph view, which is a Tasks view in the Graph layout (see Layouts). The views appear on every page. Click a view to open the Dashboard on it.

A view keeps its own layout, grouping, sort, filters, and search text, and every window shares the same views. See What Kepler remembers.

A view’s menu. Click the view you are on, or right-click any view, to open its menu:

Menu item	What it does
Rename (F2)	Renames the view. Double-clicking the name does the same
Change icon	Picks the view’s icon
Show counts on views	Shows or hides task counts on every view
View options	Opens the View menu
Duplicate view	Adds a copy of the view with the same settings
Move left, Move right	Moves the view 1 place
Views position	Sets where the views sit
Delete view	Removes the view after a confirmation

You cannot delete your last Todo view or your last Tasks view.

Add a view. Click New view after the views, then choose Todo, Tasks, Agent Graph, or Duplicate current view. Name the new view, set it up in the menu that opens, and choose Done.

Reorder the views. Drag a view to a new place, or use Move left and Move right in its menu. On the Dashboard, Cmd/Ctrl+Shift+[ and Cmd/Ctrl+Shift+] show the previous or next view, and Cmd+Option+[ and Cmd+Option+] (Ctrl+Alt+[ and Ctrl+Alt+] on Windows and Linux) move the view you are on. See Keyboard shortcuts.

If the views run out of room, they fold into 1 button. Click it to see every view.

Change a view’s icon

To pick another icon for a view, open the view’s menu and point to Change icon. Search for an icon or choose one from the grid. The first icon is the view type’s default.

Where the views sit

By default, the views sit in a row below the title bar. To move them, choose Views position in any view’s menu, then Title bar, Below title bar, or Left side. On the left side, Settings moves to the foot of the column.

Along the left side, the views start as icons. To show their names, click Expand views at the foot of the column, or drag the column’s edge. Collapse views returns to icons.

Settings → Appearance → Dashboard has the same choices, and also View style: Tabs or Pills. See Dashboard settings.

Status and counts on views

A Tasks view shows its agents’ most urgent state as a mark on its icon, using the same levels as the tray icon, such as Needs your answer. Only the tasks that the view’s filters keep count.

A view with filters also shows how many tasks match them. To hide the counts, turn off Show counts on views in any view’s menu.

Hover a view to see its state, its task count, and its filters.

Choose what a Todo view lists

A Todo view’s View menu has a Scope switch:

• Mine, the default, lists work created by you, assigned to you, mentioning you, or awaiting your review.
• All lists everything open in Kepler’s repos, plus your work elsewhere.

Under All, Repos and Updated choose which repositories and how recent the work is. See The Dashboard’s views.

---

Layouts

The layout switch at the top of the View menu sets how Kepler shows the view:

Layout	What you get	Use it to
List	A compact list you read from top to bottom	Scan everything at once
Board	One column per section of the list	See how far along tasks are, and move tasks between stages
Graph	The Agent Graph of the view’s tasks. Tasks views only	See what every agent is doing. See The Agent Graph

List is the default. Each view remembers its own layout, so a Todo view can show a list while a Tasks view shows a board. List and Board both use the view’s grouping and filters.

Board shows the sections of the current grouping as columns side by side, so Group by sets what the columns are. When you group by Progress, the columns are the stages, from Exploration to Done, and they stay in place even when empty.

When Your groups is on and another grouping is chosen, the Board becomes a grid. Each group is a row (a lane), and the grouping’s sections are columns across every lane. See Your groups.

All columns on the board have the same width. To resize them, use one of these methods:

• Drag the gap after any column. All columns resize at once.
• Focus the gap and press the arrow keys. Home sets the narrowest width and End the widest.
• Double-click the gap to return to the default width.

Each view remembers its own column width. When a column has more tasks to load, Load more appears at the bottom of the column. From the keyboard, ← and → move to the nearest column that has a card.

On the board grouped by Progress, you can also move a task to another stage by hand. See Set a task’s progress.

Graph replaces the list instead of arranging it. While it is chosen, the View menu shows the graph’s own controls in place of Group by and Sort by. See The Agent Graph.

---

Group

Group by in the View menu divides the list into sections.

Each type of view has its own groupings:

View	Group by	Default
Todo	Type, Needs my attention, Priority, Age, Your role, Assignee, Provider, Repository, Milestone, Status, None	Type
Tasks	Inbox, Progress, Activity, Repository, None, and the Your groups switch above them	Inbox

On a Tasks view, the Your groups switch above Group by divides the list by groups you make yourself, either alone or with another grouping inside each group. See Your groups.

Inbox

Inbox is the default on Tasks views. It groups tasks by what each task needs from you, not by how far the work has progressed. Sections that need you come first, and the sections for work you have put away come last:

Section	What it holds
Needs attention	Something waits on you, such as a question, an approval request, a failed turn, failing CI, or a review that requests changes
Unread	A session finished a turn you have not looked at, or a hold lifted
Running	An agent is working on it
Important	A task you starred with Star in its menu
Recent	Moved in the last 24 hours
On hold	You or an agent put it on hold. Starts folded
Earlier	Moved more than 24 hours ago. Starts folded
Done	Finished, waiting only on the decision to archive it
Not started	No session has started in it yet. Starts folded
Later	You or an agent set it aside for later. Starts folded
Archived	Tasks you archived. Starts folded

A finished turn stays unread until you look at it.

To step through the tasks that need you in Inbox order, use Go to next task needing attention, Go to next unread task, or Go to next task needing attention or unread. Run them from the palette’s Commands tab, or give them a key in Keyboard shortcuts. They have no key by default.

Inbox lists every task exactly once:

• A task that is both unread and blocked on you appears under Needs attention.
• A task under Running or Done appears only there, not also in a time section.
• A starred task lists under Important unless it needs you, is unread, is held, is running, or is done.

Drop a card on an Inbox section. To act on a task, drag its card onto another Inbox section:

Drop on	What happens
Unread	Marks the task unread
Recent or Earlier	Marks an unread task read
Important	Stars the task
On hold or Later	Puts the task on hold, or sets it aside for later
Done	Marks the task done. Refused while an agent is still working
Archived	Opens the archive confirmation

A section that refuses the card fades, and says why when you hover over it. To see what a drag looks like, see Set a task’s progress.

On hold and Later are for tasks you do not want to work on now, so a held task stays there even while an agent works on it. A held task still moves up when something needs you: an unread turn or a blocked prompt lists it under Unread or Needs attention.

The other groupings

Progress and Activity group the same tasks in 2 different ways:

• Progress shows how far the work has progressed: Exploration, In Development, In Review, On hold, Later, Done, Archived. Group by Progress to see where each task is in your workflow.
• Activity shows what the task’s agent sessions are doing now, from Waiting and Error down to Idle and Ended. A task lists under its most urgent session’s state, or under No sessions, Done, or Archived. Group by Activity to see what needs a person.

Repository is the only grouping that can list a task twice. A task with worktrees in several repositories appears under each repository.

Tasks views have no Status grouping. A task’s status is its progress stage, so group by Progress instead.

On Todo, Needs my attention groups each item by what it needs from you now, most urgent first, from Ready to merge and Changes requested down to No action needed. Each section header has a ? button that explains what the section holds.

On Todo, Priority reads an item’s priority from its labels, such as P0 to P4 or urgent. Kepler does not read a tracker’s own priority field, so an issue with no priority label is Unprioritised, and every pull request goes under Not applicable.

Age groups by when an item was created: Today, This week, This month, Older, and No date. Assignee groups by who an item is assigned to on each provider, with Unassigned for the rest.

On Todo, Milestone groups items by their milestone, with open milestones before closed ones. Items with no milestone go under No milestone.

On Todo, Status groups issues by their tracker’s own workflow state, such as a Linear In Progress or a Jira To Verify, instead of putting every open issue in one section.

Items with no repository or provider go under No repository and No provider. A pull request whose provider did not report its author goes under Unattributed. An issue goes under Not applicable, because issues have no author or reviewer role to group by.

Your groups

The other groupings arrange tasks by what Kepler can see. A group is one you make yourself: a name and a color you give to tasks that belong together, such as the tasks for one feature or one release. A task can be in 1 group at a time, and groups are available only on Tasks views.

Create a group. The New group form asks for a Group name and a Color. Choose Create group to save the group. Each active group needs its own name.

Put tasks in a group. You can add tasks to a group in 4 ways:

• From a task’s menu. A task’s ⋮ and right-click menus, on the Dashboard and on the task page, have Add to group. Its submenu lists your groups with their colors, with the task’s current group checked. Below them, New group… opens the form with this task already in it, and Remove from group appears for a task that has a group. A task with sub-tasks also offers Group with its {count} sub-tasks, which opens the form with the task’s name and with the task and its sub-tasks in it.
• By dragging one task onto another. Hold a dragged task over another task until a pill appears: Create group, or Add to {group} when that task has a group. Drop the task on the pill. Create group opens the form with both tasks in it. From the keyboard, use the menu.
• From a selection. Right-click inside a selection of 2 or more tasks and choose New group with {count} tasks…, Add {count} tasks to group, or Remove {count} tasks from group. See Act on several tasks at once.
• By dropping into a group’s section. With the list grouped by your groups, drag a task into another group’s section to move it there, or onto Ungrouped to remove it from its group.

To add an archived task to a group, restore the task first.

See a task’s group. Under any grouping, a task in a group shows its group’s color: a bar on the left edge of a List row, or a chip with the group’s name after a Board card’s title. Hover over the bar or chip to see the group’s name and a summary of its tasks. Click it to open the group’s menu without opening the task:

Item	What it does
Open group	Opens every active task in the group in panels. Offered when the group has more than 1
Show only this group	Sets the Group filter to this group
Group by your groups	Turns on the Your groups switch, keeping the current grouping inside each group
Remove from group	Takes this task out of the group
Edit group…, Archive group, Delete group…	Act on the group itself, as from its header (below)

Group the list by your groups. Turn on the Your groups switch in the View menu:

• With None chosen, each group is a section, in your own order whatever the sort, followed by Ungrouped for tasks without a group. Each group’s archived tasks are in a folded Archived section just after the group. A group with no tasks still has its section, so you can drop tasks into it.
• With another grouping chosen, such as Inbox, each group has its own sections of that grouping. On the Board, each group becomes a lane, and the grouping’s sections become columns across every lane.

A group’s header. Each group’s header shows the group’s color and name, then its count of active tasks and a dot for each state its tasks’ sessions are in. A folded group therefore still shows whether something in it needs you. Select on a group header selects every task in the group.

To open the group’s menu, right-click the header or click its ⋮. The menu acts on the group, never on its tasks:

Item	What it does
Edit group…	Renames the group or changes its color, in the same form
Move group to top, Move group up, Move group down, Move group to bottom	Moves the group in your order
Manage groups…	Opens Settings → Tasks → Groups (below)
Archive group	Archives the group. Offered only when every task in it is archived
Delete group…	Removes the group after a confirmation. Its tasks stay, ungrouped

You can also drag a group’s header to move the group before or after another group.

Archive or delete a group. When a group’s work is done and every task in it is archived, archive the group. The group leaves the Dashboard, and you can reuse its name. If you restore one of its tasks, the group comes back too, and the task stays in it. Deleting a group never deletes its tasks. They stay where they are, without a group.

Manage every group in Settings. Settings → Tasks → Groups lists every group, including archived groups. There you can create, edit, reorder, restore, and delete groups. See Groups.

Agents can put tasks into groups too, through Kepler’s workspace tools. See What an agent can do with a task’s resources.

Fold a section

To fold or unfold a section, click its header. The header shows the section’s count beside its name.

On the Board layout, a folded column shrinks to a narrow strip with its name and count. Click the strip to expand the column.

Some sections start folded:

• Archived, when you group by Activity or Inbox, because it holds work you have put away.
• On hold, Earlier, Not started, and Later, in the Inbox grouping.

Under Your groups, folding a group hides the sections inside it, and you can fold each of those sections separately too.

Kepler remembers folds across restarts, for each view and grouping. A section you folded stays folded, and a section you unfolded, such as Archived, stays open.

---

Sort

Sort by in the View menu orders the items inside each section. It does not change the order of the sections, with 2 exceptions:

• Repository sections follow the sort, and each section’s place depends on its first task.
• Your own groups always keep the order you gave them.

Each type of view has its own sort options:

View	Sort by	Default
Todo	Updated, Created, Name, ID, Type	Updated
Tasks	Updated, Created, Name, Manual	Updated

Dates sort newest first. Name and ID sort in ascending order. Type puts pull requests before issues, with the most recent first within each. On a Tasks view, starred tasks come first in each section, except under Manual. Each view remembers its own sort.

Put tasks in your own order

Manual sorts a Tasks view in an order you set yourself, inside each section, in any grouping, on List or Board. Each Tasks view keeps its own Manual order. To move a task, use one of these methods:

• Drag its row or card to a place in its own section. A line with a dot shows where it will land. Under Manual, a row shows a drag grip when you hover over it.
• Choose Move up, Move down, or Move to top of {section} from the task’s ⋮ or right-click menu. These items appear only while the list is sorted by Manual.
• Drag one task of a selection to move all the selected tasks together. They land as one block, in the order they were listed. See Act on several tasks at once.

You do not have to switch to Manual first. If you drop a task in a new place in its own section while the list is sorted another way, Kepler saves the order you see, including your move, as the view’s Manual order, and switches the sort to Manual. If you switch to Manual yourself, Kepler also keeps the current order, so no task changes place.

If the view already has a saved Manual order, a drop under another sort would replace it, so Kepler asks first. To keep the move, choose Switch and replace Manual. To put the task back, choose Cancel, press Escape, or click away.

---

Set a task’s progress

By default, Kepler sets a task’s progress stage from its Git branches and pull requests (see Status). Sometimes Git and the pull requests do not show what you know. For example, a review was sent back, or the work was merged somewhere Kepler cannot see. In those cases, set the stage yourself.

You can set the stage in these ways:

• The progress control. Click the stage name on a task row, in the panel header, or in the task page header to open the Progress menu: Automatic, then each stage, On hold, and Later.
• The task menus. A task’s ⋮ and right-click menus have the same choices under a Progress submenu, plus Reopen while the task is Done.
• Drag a card. In any grouping, on List or Board, drag a task’s card or row. When grouped by Progress, drop it on another stage. On a touch screen, press and hold the card to pick it up. Press Escape to cancel the drag. If you drop the card in its own section, Kepler reorders it (see Put tasks in your own order).
• The Mark as bar. While you drag, a Mark as bar appears over the toolbar with chips for what the card can become: Read or Unread, the stages, On hold and Later, Reopen for a Done task, and Archive task. For an archived task, it shows only Restore. Drop the card on a chip.
• From the keyboard. When a card has focus on the Board grouped by Progress, press Cmd/Ctrl+Shift+← or Cmd/Ctrl+Shift+→ to move it 1 column.

While you drag, each section that accepts the card has a dashed outline. Sections that do not accept it fade, and say why when you hover over them. On the Board, a folded column opens when you hold the card over it.

The control’s tooltip says whether the stage Updates as you work or was Set manually.

How a stage you set works with Git. Kepler keeps a stage you set until Git and the pull requests catch up with it or change. Then Kepler sets the stage from them again:

• If you set a stage ahead of Git and the pull requests (Done before the merge, or In Review before the pull request), the stage stays until they reach it.
• If you set a stage behind them (Reopen, or a review sent back to In Development), the stage stays until they change in any way. A reopened task therefore still follows its next pull request.
• To return the task to automatic stages sooner, choose Automatic, or drop its card on the column that Git and the pull requests already show.

Reopen on a task you marked Done returns it to the stage that Git and the pull requests show. If Git and the pull requests show the task as finished, Reopen sets In Development, and the task’s next pull request moves it forward again.

Dropping a card on Archived opens the archive confirmation. Dragging an archived card to another section restores the task first.

Agents can also set the stage, put a task on hold until a condition, or set it aside for later, through Kepler’s workspace tools. If an agent lifts a hold you placed, it tells you.

Hold a task, or set it aside for later

On hold and Later both put a task aside without changing its stage. Choosing any stage or Automatic lifts either one, and so does the task reaching Done.

• On hold is a pause. The task’s agents keep running, and the hold can lift by itself when something happens.
• Later sets the task aside for longer. It stops the task’s running agents but keeps their sessions, so you can resume them. Later never lifts by itself.

Hold until something happens. On hold in the Progress menu opens a submenu:

Choice	The hold lifts
Indefinitely	Only when you lift it
Until CI finishes	When CI on the task’s pull request finishes
Until a review arrives	When someone reviews the pull request
Until the pull request merges or closes	When the pull request is merged or closed
Until another task is done	When the task you pick reaches Done
For 1 hour, For 3 hours	After that long
Until tomorrow, Until next week	At 9:00 the next morning, or at 9:00 next Monday
Until a custom date…	At the date and time you choose, up to a year away

The pull request rows need an open or draft pull request linked to the task. When the task has several, each pull request row opens a submenu: wait on All running pull requests for CI, or Any pull request for a review or a merge, or pick one pull request.

While a task waits, its row says what for, such as On hold until CI finishes on #51. When the hold lifts, the row says why, such as Back from hold: CI passed. A hold that lifts on bad news, such as failed CI, lists the task under Needs attention. Any other reason lists it under Unread.

---

Filter

The Filters section at the end of the View menu has a submenu for each facet, such as Progress or Provider.

Each type of view has these facets:

View	Facets
Todo	Needs my attention · Review requests · Your role · Type · Linked work · Status · Priority · Age · Provider, then one section per connection with its own Repository · Assignee · Author · Reviewer · Issue type · Label · Project · Milestone · Iteration or Sprint
Tasks	Progress · Activity · Repository · Agent · Session · Group · Linked work

Facets with a fixed set of values, such as Progress or Priority, always list every value, even one that nothing matches. Other facets list only the values in your work, and Kepler hides a facet that has no values to choose from.

GitHub Enterprise and GitLab Self-Hosted get sections of their own. Milestone appears for providers that have milestones, such as GitHub, GitLab, and Linear.

Issue type, Label, Project, and Iteration use your provider’s own values (a Jira issue type, your team’s labels, a board name), not Kepler’s own names for them. Azure DevOps calls the last one Iteration and Jira calls it Sprint, so the facet uses each tracker’s word.

Linked work filters by whether an item is connected to work in the other type of view:

• In Todo, it filters each pull request or issue by its task history: Has an active task, Archived tasks only (worked on before, but every task is archived), or No tasks ever.
• In Tasks, it offers Has a PR or issue.

Activity matches a task when any of its sessions is in that state, so a task with one running session and one unread session matches both Running and Unread.

Session offers Has a session and Has a live session. To find tasks without a pull request, issue, or session, exclude the value.

Group lists each of your groups, including empty ones, and Ungrouped for tasks without a group. When the list is grouped by your groups, the facet also limits which group sections appear.

Include or exclude any value. Click a value to include it. To exclude a value instead, hover over it and click its minus button, or press Shift+Enter from the keyboard. An excluded value reads not {value}. On Todo, excluding a provider’s value removes only that provider’s items, so excluding a GitHub label never hides a Jira issue.

Values you include in one facet are combined. If you tick GitHub and GitLab under Provider, the list shows items from either provider. Excluded values remove items: Kepler hides an item that matches any of them. A facet with nothing chosen reads Any and does not narrow the list.

To find a value in a long facet, type in its Search filters… box. The filters you choose also show in the search box, and you can type them there instead. See Filter from the search box. When a narrow window folds the search box into an icon, the View button counts the filters instead. Hover over the button to see them.

---

Search

The search box finds items by title, reference, or repository, and finds tasks by their branch names too. Each word you type matches on its own, in any order, so login kepler finds a Fix login task in the kepler repository. Put a word or phrase in quotes to match whole words only: “log” leaves out login.

To find one task, paste its link (Copy task link) into the search box. A session’s link (Copy session link) finds the task that holds the session.

The search box fills the free space in the toolbar. To have it grow only as you type, set Search box to Grows as you type in Settings → Appearance → Dashboard.

When a search or a filter narrows the list, pills at the right end of the search box show how many rows are left or hidden. Each pill clears only its own search or filters:

Pill	What it counts	Clicking it
The search pill	The rows on screen out of every row: {count} of {total}	Clears the search
The filter pill	The rows your filters hide: {count} hidden	Clears the filters

While a search is on, the filter pill counts only hidden rows that match the search. If a search seems to miss something, the filter pill shows whether your filters are hiding it. On Todo, a count such as 40+ means more items are still loading.

When nothing matches, the empty list offers a button that clears the search, the filters, or both.

Search covers only the work the view has already loaded. On a Todo view, that is the work its scope lists. See Choose what a Todo view lists.

Filter from the search box

The search box also takes the view’s filters, written as qualifiers such as activity:waiting or type:pr, beside your search words. As you type, it suggests filters, then their values with their counts. A filter you set in the View menu appears in the box as a qualifier, and a qualifier you type sets the filter. When you type a qualifier:

• Put – before a qualifier to exclude its value, such as -progress:done.
• Put a name with spaces in quotes, such as group:"Release work".
• On a Tasks view, branch: filters by branch name.

A qualifier that can match nothing is underlined. Hover over it to see why, such as a group name that does not exist.

---

What Kepler remembers

Each view keeps its layout, grouping, sort, filters, search text, and, on Todo, its scope, in every window and across restarts. In each window, each view also remembers its open panels and their layout, its folded sections, and where you scrolled to. If you switch to another view and back, the panels you were reading are still open.

After a restart, each window reopens on the view it was showing, with that view’s panels.

---

Archive, restore, and clean up in bulk

Archive task puts a task away. The task moves from its current section to Archived, and Kepler stops its running agents. Its sessions and resources are kept, so you can resume them later. With Also delete worktrees ticked, archiving ends the task’s agents instead, and closes the Kepler terminals open in those worktrees.

When a task meets all of these conditions, the preview header and the task page header suggest archiving it, with Ready to archive? and an Archive button:

• The task is at Done.
• None of its worktrees has unpushed work.
• No agent is working or waiting on you.
• No session is running background work, such as a dev server.

Archive opens the usual confirmation. The X dismisses the suggestion for that task in every window.

The confirmation offers the same options as deleting a task: Also delete worktrees, Also delete branches (after you tick Also delete worktrees), and Also delete the branch on the remote (after you tick Also delete branches). You can therefore remove a finished task’s worktrees and branches from disk without deleting the task. With Also delete worktrees ticked, the dialog lists each worktree with what will happen to it, such as 2 uncommitted files, and names the worktrees it keeps, such as the repository’s main worktree. Kepler keeps a worktree that would lose work unless you tick the extra box that names what would be lost. To check before you decide, open the changes from the row of a worktree at risk.

With Also delete the branch on the remote ticked, Kepler also deletes each branch’s remote copy, unless that would lose work, such as a branch with an open pull request or commits that are not on the remote. A message says which branches it kept, and why.

Restore task replaces Archive task in an archived task’s ⋮ menu, and also appears in the task page’s header. It restores the task at once, without asking. A restored task stays in its group, and if that group was archived, Kepler restores the group too.

To archive, restore or delete several tasks at once, click Select on a section header in a Tasks view. The header becomes a bar with a select-all box and the actions, and the section’s rows show checkboxes. You can select in 1 section at a time, and while you select, clicking a row ticks it instead of opening its panel.

The bar has these buttons:

Button	What it does
Archive	Archives every selected task that is not already archived
Restore	Replaces Archive when every selected task is already archived
Delete	Deletes the selected tasks permanently
Cancel	Ends selection and clears the selection

Archive and Delete both ask you to confirm, with Archive tasks or Delete tasks as the confirm button. Both offer Also delete worktrees, Also delete branches, and Also delete the branch on the remote. Deleting cannot be undone, and the confirmation says so. The batch confirmation differs from the single-task dialog in 2 ways:

• The single-task dialog remembers what you ticked last time. The batch confirmation always starts with all 3 boxes unticked.
• The batch confirmation does not list what will happen to each worktree. Instead, Kepler keeps any worktree that would lose work, and a message afterwards says which ones and why. To see the list before you confirm, use the task’s own ⋮ menu.

Act on several tasks at once

The tasks you open with Shift-click or Cmd/Ctrl-click (see Open a panel) are also a selection you can act on. While 2 or more tasks are selected, right-clicking or dragging any one of them acts on all of them. Right-clicking or dragging a task outside the selection acts on that task only. A row’s ⋮ always acts on its own row.

Right-clicking inside the selection opens a selection menu instead of the task menu, and each item counts the tasks it acts on. With it you can set the progress of every selected task, mark them read or unread, star or unstar them, group or ungroup them, shut down their agents, and archive, restore or delete them. Shut down agents asks first while an agent is still working. The group and Progress items skip archived tasks. Archive, Restore, and Delete open the same batch confirmation as a section’s Select bar. For the full menu, see Task rows.

Dragging a selected task drags the whole selection. Each drop target says how many of the tasks it accepts. After the drop, Kepler reports how many tasks moved and how many stayed where they were. Under the Manual sort, the tasks land together as one block.

To clean up worktrees and local branches instead of tasks, open Settings → Repositories and choose Manage worktrees and branches. The Worktrees and branches page lists every worktree, and every local branch that no worktree has checked out. You can filter the list by Safe to delete, Needs update, Conflicts, Stale, or All. On this page, you can:

• Update several worktrees at once, which brings each branch up to date with its base.
• Delete worktrees and branches, including their copies on the remote.

See Settings.

---