Skip to main content
Glama

Tasketier

build release license

What: A task tool for Windows that keeps all data on the PC. A global hotkey opens a one-line box. You type the task with inline marks (@tomorrow, @15:30, !, #tag) and press Enter. A list window shows Inbox, Today, Upcoming, Done and All. A tray icon keeps the app running. tasketier.exe gives the same store a command line and an MCP server. A Claude Code plugin in this repo tells an LLM how to use it.

Why: Tasks that come to mind during the day get lost, because writing them down takes too much attention. Capture must take less than two seconds from any window. The daily look-through must show what is due, what is planned for today and what is done. An LLM must be able to add and query tasks from a running session.

Status: working. Capture box, list window with the five views, inline edit, plan star, undo, alarms, settings, help, tray, autostart, CLI, MCP server, plugin, installer. Every gate of scripts/verify.ps1 passes.

Screenshots

The capture box opens from any window with Ctrl+Alt+A. The line below the text shows what the parser read from it, before you press Enter:

The capture box with "Call the dentist @fri @15:30 ! #health" typed and the parsed due, priority and tag shown below

? or F1 shows every mark:

The capture box with the inline syntax help unfolded

The list window, Today view. Overdue tasks come first, in red. Then the tasks due today. Then the task planned for today, with the star. The marks stand in front of the title, the tags under it:

The list window with the Today view: the priority mark and the alarm bell in front of each title, the tags under it, the due day on the right and a pencil at the end of each row

The alarm: a digital clock in the corner of the screen that beeps and rattles until you answer it. Done completes the task, the three middle buttons snooze, Disarm acknowledges. The SNOOZE bar on top and Esc snooze one minute:

The alarm clock: an orange body with a SNOOZE bar, a dark display with the due time in seven-segment digits and the task title, and the buttons Done, 5 min, 15 min, 1 h, Disarm

Related MCP server: TickTick MCP CLI

How to run

dotnet build Tasketier.slnx
dotnet test  Tasketier.slnx
dotnet run   --project src\Tasketier.App                 # tray, hotkeys, the list window
dotnet run   --project src\Tasketier.App -- --capture    # the capture box
dotnet run   --project src\Tasketier.App -- --tray       # icon only, as at Windows start-up
dotnet run   --project src\Tasketier.App -- --data D:\t  # another data folder; runs beside the normal instance
dotnet run   --project src\Tasketier.Cli -- add "Buy milk @tomorrow #home"
dotnet run   --project src\Tasketier.Cli -- list --view today
dotnet run   --project src\Tasketier.Cli -- mcp          # the MCP server on stdin/stdout
.\scripts\verify.ps1
.\build-installer.ps1

Verify: .\scripts\verify.ps1 runs four gates. Build with warnings as errors (analyzers, code style, nullable). Unit tests with coverage. The dotnet format check. Cyclomatic complexity (lizard, limit 9). The script exits non-zero on any FAIL or NOT VERIFIED.

Prerequisites: Windows 11 (the installed app runs on Windows 10 1607 or later). .NET SDK 10.0.400 (net10.0 and net10.0-windows). git. lizard (pip install lizard==1.17.31) for the complexity gate. Inno Setup 7 (C:\Program Files\Inno Setup 7) for the installer. nuget.config clears the machine-level feeds, so the build is the same on every machine.

Install

.\build-installer.ps1 writes out\installer\Tasketier-Setup-<version>.exe. The installer:

  1. Copies TasketierApp.exe (the tray app) and tasketier.exe (the CLI and MCP server) into C:\Program Files\Tasketier.

  2. Adds that folder to PATH.

  3. Offers a start-with-Windows task.

  4. Downloads the .NET Desktop Runtime 10.0 from Microsoft when it is missing. The installer checks the SHA-256 of the download.

Tasks and settings live in %LOCALAPPDATA%\Tasketier. An uninstall keeps them.

The Releases page has the installer of each version. CI (.github/workflows/build.yml) runs scripts/verify.ps1 and build-installer.ps1 on every push and keeps the installer as an artifact. A tag v1.2.3 makes the release with the installer and its SHA-256.

Use

Action

How

Add a task from anywhere

Ctrl+Alt+A, type, Enter. Esc cancels. The focus returns to the previous window. When you click elsewhere, an empty box closes, and a box with text stays on top until you press Enter or Esc.

Open the list

Ctrl+Alt+L, or a left click on the tray icon

Complete

The checkbox, or Space on the selected row

Plan for today without a date

The star (☆ becomes ★). The task stays in Today until it is done or unstarred.

Edit

The pencil at the end of the row, F2, or a double-click on the title. The row becomes one edit field with the whole line in inline syntax. Enter saves, Esc cancels.

Delete

Del. Ctrl+Z brings the task back.

Undo

Ctrl+Z. The app keeps the last 20 changes of the session, captures included.

Filter

Type in the filter box (Ctrl+F). The filter matches the title or a #tag.

Alarm

@alarm on a task with a time: an orange digital clock in the corner 3 minutes before, with Done, Snooze 5 / 15 / 60 min and Disarm. It beeps until you answer it. The SNOOZE bar, Esc and a close without an answer (for example Alt+F4) snooze 1 minute. Only Disarm acknowledges. A snooze is stored with the task, so it also comes back after a restart. @alarmN sets N minutes, for example @alarm5 or @alarm15. Settings changes the default lead. The tray app must run. When the app starts more than one hour after a due time, it does not show that alarm.

Help

? or F1 in the capture box or the list. Also in the tray menu.

Settings

Tray menu: both hotkeys, the alarm lead, the data folder, start with Windows (the per-user Run entry in the registry, which the installer also writes)

You can change both hotkeys in Settings. When another program holds a chord, the tray shows a message, and that hotkey stays off until you change it. The defaults avoid chords that common tools hold, such as Ctrl+Alt+Space and Ctrl+Alt+T.

Inline syntax: Words are the title. #tag adds a tag. ! is high priority, !! is urgent. Both also work as a suffix: Pay rent!!. @today, @tomorrow, @mon to @sun, @2026-11-03, @+3d and @+2w set the due day. A weekday means the next such day after today. @15:30 sets the time. Without a day, the time means today. @none removes the date. @alarm sets an alarm at the default lead before the due time (3 minutes unless Settings changes it). @alarmN sets one N minutes before, for N from 0 to 1440. An alarm needs a time. An unknown @ mark is an error. The box shows it before you press Enter.

Views: Today shows overdue tasks first, in red, then tasks due today, then tasks planned for today. Upcoming shows tasks due after today, by day. Inbox shows tasks with no date that are not planned. Done shows tasks completed in the last 30 days. All shows every task: the open ones first, in the same order as Today and Upcoming, then the done ones, newest first.

Command line: tasketier add|list|show|done|undone|edit|delete|plan|unplan|search|mcp|version. --json prints records for scripts. --data <folder> points at a different tasks.json. tasketier help shows all commands.

LLM access (MCP and plugin)

tasketier mcp is an MCP server on stdin and stdout. Its tools are add_task, list_tasks, get_task, complete_task, reopen_task, update_task, delete_task, plan_today and search_tasks. Each tool returns the changed records as JSON. A failed call returns its message.

The Claude Code plugin in plugin\ contains a skill and the server registration. The skill says which tool to use for which request, the inline syntax and the working rules. The registration starts ${ProgramFiles}\Tasketier\tasketier.exe mcp. To install the plugin in Claude Code:

/plugin marketplace add meet-brad-ch/Tasketier     # or a local clone: /plugin marketplace add C:\Apps\Projects\Tasketier
/plugin install tasketier@tasketier

The app, the CLI and the server share one file under a cross-process lock. The app reloads when the file changes. A task that Claude adds appears in the list at once.

Storage

The tasks are one JSON file: %LOCALAPPDATA%\Tasketier\tasks.json. You can move the folder in Settings, for example to a synced folder. Each write goes to a temporary file first and then replaces the real file in one step. The first write of each day copies the previous file to backups\tasks-<date>.json. A damaged file causes an error that names the file. The app never replaces a damaged file. There is no network access and no telemetry.

Layout

  • src/Tasketier.Core/ — a library without UI code: task model, inline-syntax parser, JSON store (mutex, atomic replace, daily backup, file watcher), view queries, alarm scheduler, service, undo, settings.

  • src/Tasketier.App/ — WPF (TasketierApp.exe): capture window, list window, alarm card, help window, settings window, tray icon, global hotkeys, instance signals, autostart.

  • src/Tasketier.Cli/ — console (tasketier.exe): the commands and the mcp server (ModelContextProtocol 2.3.0).

  • plugin/ — the Claude Code plugin. .claude-plugin/marketplace.json at the root lists it.

  • tests/Tasketier.Core.Tests/, tests/Tasketier.Cli.Tests/ — xUnit. The CLI tests start the real exe as an MCP server and drive it with the SDK client.

  • installer/Tasketier.iss, build-installer.ps1 — the Inno Setup installer.

  • scripts/verify.ps1 — the quality gates.

  • tools/make_icon.py — draws the icon. tools/make_alarm_sound.py — writes the alarm beeps. tools/shoot_windows.ps1 — takes the README screenshots from a seeded data folder (see its header).

  • docs/img/ — the README screenshots.

Design

  • WPF on .NET 10. One framework-dependent exe for the app, one for the CLI. The installer bootstraps the runtime.

  • The app is TasketierApp.exe and the CLI is tasketier.exe. Both live in one folder, and Windows file names ignore case, so both cannot be Tasketier.exe.

  • One JSON file, not a database: a person can read it, there is no dependency, and the store holds some hundreds of tasks at most. A cross-process mutex keeps the app, the CLI and the MCP server from writing at the same time.

  • LLM access is a stdio MCP server and a CLI in one exe over the shared store, not an HTTP server inside the app. It works when the app does not run, and the WPF app stays free of ASP.NET Core.

  • The installer writes to C:\Program Files\Tasketier with elevation, because the .NET runtime bootstrap needs elevation. The plugin's .mcp.json finds the server through ${ProgramFiles}.

  • All text follows Simplified Technical English (ASD-STE100): short sentences, active voice, one meaning per word.


Keep this file honest. It is the only project document that is committed. LOG.md is gitignored, so anything that must survive a fresh clone belongs here, not in the log.

Available Tools

9 tools
add_taskA

Add a task from one line of text. Inline syntax: words are the title. #tag adds a tag. ! means high priority, !! means urgent. @today, @tomorrow, a weekday like @fri (the next Friday after today), @2026-11-03 or @+3d set the due day. @15:30 sets the due time, today when no day is given. @none removes the date. @alarm sets an alarm at the user's default lead before the due time (3 minutes unless Settings changes it). @alarmN sets one N minutes before (N from 0 to 1440). An alarm needs a due time. The desktop app shows it. Returns the stored task, with its id.

Inputs: text (required).

complete_taskA

Mark a task done now. This clears its snooze, and a done task does not ring its alarm. The task moves to the done view of list_tasks. A task that is already done gets a new completion time. To undo, use reopen_task. An unknown id fails with 'There is no task with id N.' Returns the task.

Inputs: id (required).

delete_taskA

Delete a task. There is no undo. Returns the removed task.

Inputs: id (required).

get_taskA

Get one task by id and change nothing. Returns the task as JSON. Fields without a value are not in the JSON. Use it when you know the id. To find tasks by text, use search_tasks. To see a view such as today or inbox, use list_tasks. An unknown id fails with 'There is no task with id N.'

Inputs: id (required).

list_tasksA

List the tasks of one view, in the view's order. The views: 'today' = overdue first, then due today, then planned for today. 'upcoming' = due after today. 'inbox' = no date and not planned. 'done' = completed in the last 30 days. 'all' = every task: open ones first (overdue, then by due day, undated last), then done ones, newest first. Returns a JSON array of tasks.

Inputs: view, filter.

plan_todayA

Put a task into the Today view without a due date (planned = true), or remove it from Today (planned = false). Returns the task.

Inputs: id (required), planned.

reopen_taskA

Reopen a done task, so it is open again. Only the done state changes: the title, tags, priority, due day, plan and alarm stay. A task that is already open does not change. To mark a task done, use complete_task. An unknown id fails with 'There is no task with id N.' Returns the task.

Inputs: id (required).

search_tasksA

Find every task, open or done, whose title or tag contains the text. The match ignores case. Open tasks come first. Returns a JSON array of tasks.

Inputs: text (required).

update_taskA

Replace the title, the tags, the priority, the due day, the due time and the alarm of a task from one line of text. Parts that are not in the text are cleared. The plan for today and the done state stay. Inline syntax: words are the title. #tag adds a tag. ! means high priority, !! means urgent. @today, @tomorrow, a weekday like @fri (the next Friday after today), @2026-11-03 or @+3d set the due day. @15:30 sets the due time, today when no day is given. @none removes the date. @alarm sets an alarm at the user's default lead before the due time (3 minutes unless Settings changes it). @alarmN sets one N minutes before (N from 0 to 1440). An alarm needs a due time. The desktop app shows it. Returns the task.

Inputs: id (required), text (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: add/get/update/delete cover CRUD, complete/reopen handle done state, list/search retrieve tasks differently, and plan_today manages the Today view. The inverse pairs and retrieval tools are explicitly cross-referenced in descriptions, leaving little room for misselection.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: complete_task, delete_task, reopen_task, get_task, add_task, list_tasks, plan_today, search_tasks, update_task. The only minor variation is plural 'tasks' in list/search, which is natural and still predictable.

    Tool Count5/5

    Nine tools is well-scoped for a task manager, covering creation, retrieval, updates, deletion, completion lifecycle, search, and planning without redundant operations. Each tool earns its place.

    Completeness5/5

    The surface covers full task lifecycle: add, get, list, search, update, delete, complete, reopen, and plan for today. Inline syntax handles tags, priority, due dates, times, and alarms, so no obvious CRUD or workflow gaps remain.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers