@togglhq/cli 1.11.65 → 1.11.66

package/build/program.js

@@ -1,2 +1,2 @@
-import { t as createProgram } from "./program-C5GYCsU3.js";
+import { t as createProgram } from "./program-DfBQ3e83.js";
 export { createProgram };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@togglhq/cli",
-  "version": "1.11.65",
+  "version": "1.11.66",
   "description": "Toggl CLI for Toggl 2.0 API operations.",
   "license": "UNLICENSED",
   "type": "module",
@@ -56,7 +56,7 @@
   "devDependencies": {
     "@toggl/cli-core": "workspace:^",
     "@toggl/operations": "workspace:^",
-    "@toggl/queries": "2.2.63",
+    "@toggl/queries": "2.2.64",
     "@types/node": "22.19.11",
     "tsdown": "0.21.8",
     "typescript": "5.9.3",

package/skills/toggl-cli/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: toggl-cli
-description: Use the Toggl CLI to work with Toggl 2.0 tasks, projects, time entries, time blocks, workspaces, authentication, and CLI maintenance from an agent-friendly terminal workflow. Trigger when the user asks to inspect or modify Toggl 2.0 data through the terminal, authenticate Toggl, switch workspaces, install or refresh the Toggl agent skill, update the CLI, or automate Toggl 2.0 workflows.
+description: Use the Toggl CLI to work with Toggl 2.0 tasks, projects, time entries, workspaces, authentication, and CLI maintenance from an agent-friendly terminal workflow. Trigger when the user asks to inspect or modify Toggl 2.0 data through the terminal, authenticate Toggl, switch workspaces, install or refresh the Toggl agent skill, update the CLI, or automate Toggl 2.0 workflows.
 ---
 
 # Toggl CLI
@@ -11,7 +11,7 @@ Use the `toggl` command when the user wants to inspect or modify Toggl 2.0 data
 
 Use this skill when the task involves:
 
-- Listing, reading, creating, updating, or deleting Toggl 2.0 tasks, projects, time blocks, or time entries.
+- Listing, reading, creating, updating, or deleting Toggl 2.0 tasks, projects, or time entries.
 - Managing saved views, custom fields (admin), and task/project attachments (including file upload and download).
 - Finding workspace metadata such as statuses, users, and workspace IDs.
 - Authenticating the Toggl CLI, switching saved profiles, or switching the active workspace.
@@ -49,7 +49,6 @@ Do not use this skill for Toggl Track APIs, raw Toggl 2.0 API calls, or MCP serv
 - Tasks: `reference/tasks.md`
 - Projects: `reference/projects.md`
 - Time entries: `reference/time-entries.md`
-- Time blocks: `reference/time-blocks.md`
 - Rates and billables (Toggl 2.0 API vs Track): `reference/rates-and-billables.md`
 - Statuses and users: `reference/statuses-users.md`
 - Reports (`get-workload` vs `get-flexq-data`): `reference/reports.md`

package/skills/toggl-cli/reference/command-contract.md

@@ -31,7 +31,6 @@ Core resources and actions:
 | -------------- | ----------------------------------------------------------------------------------- |
 | `tasks`        | `list`, `get`, `create`, `update`, `delete`, and **`bulk`** subcommands (see below) |
 | `projects`     | `list`, `get`, `create`, `update`, `delete`, and **`bulk`** subcommands             |
-| `time-blocks`  | `list`, `get`, `create`, `update`, `delete`, and **`bulk`** subcommands             |
 | `time-entries` | `list`, `start`, `stop`, and **`bulk`** subcommands                                 |
 | `statuses`     | `list`                                                                              |
 | `users`        | `list`                                                                              |
@@ -44,7 +43,6 @@ Bulk mutations use a nested command: **`toggl <resource> bulk <verb>`** (for exa
 | -------------- | --------------------------------------------------------------------------- |
 | `tasks`        | `create`, `patch`, `delete`, `archive`, `restore`, `unarchive`, `duplicate` |
 | `projects`     | `patch`, `delete`, `archive`, `restore`, `unarchive`                        |
-| `time-blocks`  | `create`, `patch`, `delete`                                                 |
 | `time-entries` | `create`, `patch`, `delete`, `restore`                                      |
 
 `list` commands also have the `ls` alias.
@@ -103,7 +101,6 @@ Bulk endpoints expect JSON via `--data` or `--data-file` (arrays for patch-style
 ```bash
 toggl --json tasks bulk patch --dry-run --data '[{"id":111,"status_id":456789},{"id":222,"status_id":456789}]'
 toggl --json projects bulk patch --data-file ./project-updates.json
-toggl --json time-blocks bulk create --data '{"time_blocks":[{"task_id":12345,"start":"2026-04-01T09:00:00Z","duration":60}]}'
 toggl --json time-entries bulk patch --data '[{"id":9001,"description":"Updated"}]'
 toggl --json tasks bulk delete --data '{"ids":[111,222]}' --yes
 ```
@@ -125,10 +122,8 @@ Delete commands require `--yes`. Never add `--yes` unless the user clearly reque
 ```bash
 toggl --json tasks delete --task-id 12345 --yes
 toggl --json projects delete --project-id 123456 --yes
-toggl --json time-blocks delete --task-id 12345 --time-block-id 67890 --yes
 toggl --json tasks bulk delete --data '{"ids":[111,222]}' --yes
 toggl --json projects bulk delete --data '{"ids":[123456,123457]}' --yes
-toggl --json time-blocks bulk delete --data '{"ids":[101,102]}' --yes
 ```
 
 ## Dates
@@ -142,7 +137,7 @@ Examples:
 
 ```bash
 toggl --json time-entries list --date-from 2026-04-01 --date-to 2026-04-07
-toggl --json time-blocks list --date-from 2026-04-01T08:00:00+03:00 --date-to 2026-04-01T17:00:00+03:00
+toggl --json time-entries list --date-from 2026-04-01T08:00:00+03:00 --date-to 2026-04-01T17:00:00+03:00
 ```
 
 ## Discovery

package/skills/toggl-cli/reference/focus-concepts.md

@@ -11,7 +11,6 @@ Environment/Profile
   -> Workspace
     -> Projects
       -> Tasks
-        -> Time blocks
         -> Time entries
     -> Statuses
     -> Users
@@ -27,7 +26,7 @@ A profile stores credentials and the selected workspace. Use profiles when the u
 
 ### Workspace
 
-A workspace is the top-level context for projects, tasks, statuses, users, time entries, and time blocks. Most IDs only make sense inside the active workspace.
+A workspace is the top-level context for projects, tasks, statuses, users, and time entries. Most IDs only make sense inside the active workspace.
 
 Use workspace commands when the agent needs to list available workspaces, refresh workspace metadata, switch the default workspace, or override the workspace for one command.
 
@@ -59,12 +58,6 @@ A time entry represents actual tracked time. Starting a time entry begins the ru
 
 Use time entries when the user wants to track work, start a break, stop tracking, or inspect actual logged time.
 
-### Time Block
-
-A time block represents scheduled or planned work. Time blocks usually belong to a task and have explicit start/end times.
-
-Use time blocks when the user wants to schedule, plan, move, inspect, or delete calendar-like time blocks.
-
 ## Choosing the Right Command
 
 If the user wants to:
@@ -74,7 +67,6 @@ If the user wants to:
 - Move work through a workflow: resolve the task ID and status ID, then update the task.
 - Track actual time: resolve the task ID, then start a time entry.
 - Stop tracking: stop the current time entry.
-- Schedule planned work: resolve the task ID, then create a time block.
 - Find people: list users.
 - Change workspace context: list or switch workspaces, or pass `--workspace-id`.
 

package/skills/toggl-cli/reference/troubleshooting.md

@@ -70,7 +70,7 @@ Use `YYYY-MM-DD` for full days or RFC 3339 for exact datetimes:
 
 ```bash
 toggl --json time-entries list --date-from 2026-04-01 --date-to 2026-04-07
-toggl --json time-blocks list --date-from 2026-04-01T08:00:00+03:00 --date-to 2026-04-01T17:00:00+03:00
+toggl --json time-entries list --date-from 2026-04-01T08:00:00+03:00 --date-to 2026-04-01T17:00:00+03:00
 ```
 
 ## Destructive Operation Blocked

package/skills/toggl-cli/workflows/common-workflows.md

@@ -75,18 +75,6 @@ Stop the running timer:
 toggl --json time-entries stop
 ```
 
-## Plan a Time Block
-
-1. Resolve the task ID.
-2. Convert user-provided times to RFC 3339 datetimes.
-3. Dry-run when the time range was inferred.
-4. Create the block.
-
-```bash
-toggl time-blocks create --data '{"task_id":12345,"payload":{"start":"2026-04-06T09:00:00+03:00","end":"2026-04-06T11:00:00+03:00"}}' --dry-run
-toggl --json time-blocks create --data '{"task_id":12345,"payload":{"start":"2026-04-06T09:00:00+03:00","end":"2026-04-06T11:00:00+03:00"}}'
-```
-
 ## Switch Workspace
 
 List workspaces, refresh if needed, then switch:

package/skills/toggl-cli/reference/time-blocks.md

@@ -1,43 +0,0 @@
-# Time Blocks
-
-Use time block commands to inspect, create, update, and delete scheduled time blocks.
-
-## Commands
-
-List time blocks for a date range:
-
-```bash
-toggl --json time-blocks list --date-from 2026-04-01 --date-to 2026-04-07
-```
-
-Get one time block:
-
-```bash
-toggl --json time-blocks get --task-id <task-id> --time-block-id <time-block-id>
-```
-
-Create a time block:
-
-```bash
-toggl --json time-blocks create --data '{"task_id":12345,"payload":{"start":"2026-04-06T09:00:00Z","end":"2026-04-06T11:00:00Z"}}'
-```
-
-Update a time block:
-
-```bash
-toggl --json time-blocks update --data '{"task_id":12345,"time_block_id":67890,"payload":{"start":"2026-04-06T10:00:00Z","end":"2026-04-06T12:00:00Z"}}'
-```
-
-Delete a time block only after explicit user confirmation:
-
-```bash
-toggl --json time-blocks delete --task-id <task-id> --time-block-id <time-block-id> --yes
-```
-
-## Agent Workflow
-
-Use RFC 3339 timestamps for exact scheduled blocks. If the user gives local times, preserve the intended time zone offset when possible.
-
-Time block commands usually need both `task_id` and `time_block_id`. Resolve both IDs with a list or get command before mutating.
-
-Use `--dry-run` before creating or updating blocks when times were inferred from natural language.