task

The task command creates, lists, shows, edits and removes tasks, and can pull candidates from Jira and from plugins such as the GitLab plugin.

Usage

kasl task [COMMAND]

Running kasl task without a subcommand creates a task interactively.

Commands

`add` - Add a task

kasl task add [OPTIONS]

-n, --name <NAME>: Task name. Required for non-interactive creation.
--comment <COMMENT>: Task comment or description.
-c, --completeness <COMPLETENESS>: Completion percentage (0-100).
--tags <TAGS>: Comma-separated tags to assign. Tags are created automatically if they do not exist yet. This is the only place tags are set - task edit never touches them.
-t, --template <TEMPLATE>: Create from a named template.
-l, --from-template: Pick a template interactively.

Without --name (or a full set of non-interactive options), kasl task add prompts interactively. Outside an interactive terminal it errors instead of hanging: “task name is required; pass –name outside an interactive terminal” - so it’s safe to call from scripts as long as --name is provided.

`--template` and the flag overrides

--template NAME fills the task from a saved template, but any of --name, --comment, --completeness or --tags given alongside it wins over the template’s value for that field - the template supplies defaults, not fixed values. Fields you don’t override, and don’t have a flag for, fall back to the template outside a terminal; in a terminal they are offered as prompts seeded with the template’s value. --tags is independent of the template either way: templates carry no tags, so tagging a templated task always goes through --tags.

`list` - List tasks

kasl task list [OPTIONS]

-a, --all: List tasks from every date, not just today.
--tag <TAG>: Only tasks carrying this tag. A tag belongs to the task, not to one day’s row: a task carried into a new day - by task find, or marked done today - keeps its tags, and --tag lists every day of it.
--json: Print the tasks as one JSON document - see JSON output. An empty list is {"tasks": []}, exit code 0.

`show` - Show tasks by id

kasl task show [ID]... [--json]

ID...: One or more task ids to show. Omit them on a terminal to pick from today’s tasks.
--json: Print them as one JSON document - see JSON output.

Of several ids, the ones that exist are shown. When none of them does, the command fails with exit code 1, so a script can tell a missing task from one it got.

`edit` - Edit a task by id, or several interactively

kasl task edit [ID]

[ID]: Task id to edit; omit to pick several interactively.

Editing only ever touches name, comment and completeness - tags are left as they are; assign them with task add --tags instead.

An edit that takes a task taken from the inbox to 100% asks what to do with its issue in Jira - leave it (the default), close it, or comment on it. See Closing the loop.

`remove` - Remove tasks by id, or all of today’s

kasl task remove [OPTIONS] [ID]...

[ID]...: Task ids to remove.
--today: Remove every task recorded for today.
-y, --yes: Remove without asking for confirmation.

`find` - Find incomplete tasks and import from Jira and plugins

kasl task find

Shows a spinner while gathering incomplete local tasks, Jira issues resolved on the day, and what plugins find in the day - for the GitLab plugin, the commits you pushed (first line of the commit message, short SHA beside it).
Presents a single consolidated MultiSelect (incomplete tasks first, then a separator, then Jira and plugin candidates). A plugin’s candidates show as ● name (ref), and the summary line names each source, for example Found: 2 incomplete, 1 jira, 3 gitlab.
Filters out tasks already logged today, near-duplicate names, and names from task_discovery.ignore_names.
After import selection, optionally add items to the persistent ignore list.
Selected incomplete tasks prompt for an updated completeness percentage before insert.
An unfinished task whose Jira issue was resolved is marked resolved in Jira, ticked in advance, and proposed at 100%: the lasting form of the offer a sync makes once. See Closing the loop.
Carrying any other task taken from Jira to 100% asks what to do with its issue, as task edit does.

Examples

# Create a new task
kasl task add --name "New Task" --comment "This is a test task" --completeness 50

# Create task with tags
kasl task add --name "Fix bug" --tags "urgent,backend" --completeness 0

# Display today's tasks
kasl task list

# Display all tasks
kasl task list --all

# Display tasks with specific tag
kasl task list --tag "urgent"

# Find and import incomplete, Jira and plugin tasks
kasl task find

# Show specific tasks
kasl task show 1

# Edit a specific task
kasl task edit 1

# Edit several tasks interactively
kasl task edit

# Create task from template, picked interactively
kasl task add --from-template

# Use a named template, non-interactively
kasl task add --template "daily-standup"

# Use a template but override its name and add tags
kasl task add --template "daily-standup" --name "Standup - sprint planning" --tags "meeting"

# Remove specific tasks
kasl task remove 1 2 3

# Remove specific tasks without confirmation
kasl task remove 1 2 3 -y

# Remove all today's tasks without confirmation
kasl task remove --today -y

Sample Output

Running kasl task list after adding one task:

+---+----+---------+---------------+------+
| # | ID | TASK ID | NAME          | DONE |
+---+----+---------+---------------+------+
| 1 | 1  | 1       | Review PR 318 | 100% |
+---+----+---------+---------------+------+

The TASK ID, COMMENT and TAGS columns only appear when at least one listed task actually has that data - an all-local, comment-less, tag-less list renders as just #, ID, NAME, DONE.

With --plain the same rows are tab-separated under a header row, and no name is cut to the terminal’s width:

$ kasl task list --plain
#  ID  TASK ID  NAME  COMMENT  DONE  TAGS
1  1  1  PROJ-412 Fix session timeout on the settings page  stale cookie jar  100%  backend
2  2  2  Review PR #318: pause merging    100%
3  3  3  PROJ-419 Draft migration for protected pauses  backfill pending  60%  backend, db

JSON output

kasl task list --json and kasl task show --json print the tasks as one document (conventions: kasl in scripts and CI). Every listing of tasks - the day in report --json, a tag’s tasks in tag show --json - uses the same shape for a task:

{
  "tasks": [
    {
      "id": 3,
      "chain_id": 3,
      "created_at": "2026-08-08T10:05:41",
      "name": "PROJ-419 Draft migration for protected pauses",
      "comment": "backfill pending",
      "completeness": 60,
      "tags": ["backend", "db"],
      "issue_key": null
    }
  ]
}

Field	Meaning
`id`	The task’s own id - the table’s `ID`.
`chain_id`	The first task of the chain this one continues across days - the table’s `TASK ID`; a task that starts a chain carries its own id.
`created_at`	When the row was written, local time.
`completeness`	0-100; a task with none recorded counts as done, as the table shows it.
`tags`	Tag names.
`issue_key`	The inbox issue the task was taken from, whichever source listed it; `null` for a task of your own.

tag - Manage tags for task categorization
template - Create and use task templates
report - View tasks in work reports
export - Export task data for analysis

task

Usage

Commands

add - Add a task

--template and the flag overrides

list - List tasks

show - Show tasks by id

edit - Edit a task by id, or several interactively

remove - Remove tasks by id, or all of today’s

find - Find incomplete tasks and import from Jira and plugins