Skip to content

docs: document recent list/schedule/timezone improvements - #152

Merged
devondragon merged 1 commit into
mainfrom
docs/update-readme-changelog-recent
Aug 24, 2026
Merged

docs: document recent list/schedule/timezone improvements#152
devondragon merged 1 commit into
mainfrom
docs/update-readme-changelog-recent

Conversation

@devondragon

Copy link
Copy Markdown
Owner

Updates the CHANGELOG [Unreleased] section and the README for the changes shipped since the #132#141 wave. Docs only, no code changes.

CHANGELOG ([Unreleased])

New ✨ Added section plus one 🐛 Bug Fixes entry:

README

  • Added list_all_uncompleted to the motion_tasks operations (it was in CLAUDE.md but missing here)
  • Described the new dueDate on-or-before semantics, completedAfter/completedBefore, and the timezone header
  • Corrected the motion_schedules description to match the tool: working-hour templates with per-day hours, not calendar events / free-busy

https://claude.ai/code/session_01HbZLaLAKnrR3ZoZkZUk1Dn

Update the CHANGELOG [Unreleased] section and README for the changes
shipped since the #132-#141 wave:

- #151: account timezone + today's local date header on list/schedule
  responses
- #149: list_all_uncompleted honors dueDate/priority; list gains
  completedAfter/completedBefore; schedule working hours; motion_statuses
  in the essential tier
- #148: dueDate filter reduced to account-zone calendar date
- wrangler observability logs enabled

README: add list_all_uncompleted to motion_tasks operations, describe the
new dueDate/completion filters and the timezone header, and correct the
motion_schedules description to match the tool (working-hour templates,
not calendar events).

Claude-Session: https://claude.ai/code/session_01HbZLaLAKnrR3ZoZkZUk1Dn
Copilot AI lite review requested due to automatic review settings August 24, 2026 22:04
@devondragon
devondragon merged commit 6a2a383 into main Aug 24, 2026
3 checks passed
@devondragon
devondragon deleted the docs/update-readme-changelog-recent branch August 24, 2026 22:04

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

Only minor documentation wording/staleness nits were found; no functional or structural issues block merge.

Pull request overview

Updates repository documentation to reflect recently shipped Motion task listing/scheduling improvements and tool-tier changes, keeping public docs aligned with behavior introduced across the #132#151 PR wave.

Changes:

  • Documented motion_tasks list_all_uncompleted operation and clarified dueDate / completion-date filter semantics and timezone header behavior.
  • Corrected motion_schedules README description to match working-hours template output.
  • Expanded the [Unreleased] CHANGELOG with an ✨ Added section and a dueDate bug-fix entry summarizing shipped behavior.
File summaries
File Description
README.md Updates tool reference docs for motion_tasks and motion_schedules, including new ops and clarified filter/timezone semantics.
CHANGELOG.md Adds an ✨ Added section and a new bug-fix bullet documenting timezone/date context and dueDate filtering fixes.
Review details
  • Files reviewed: 2/2 changed files
  • Comments generated: 2
  • Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread CHANGELOG.md

### ✨ Added

- **Account timezone and today's date on list responses**: task-list responses (`list`, `list_all_uncompleted`) and schedule responses now begin with a one-line header, e.g. `Account timezone: America/Denver | Today: 2026-08-24 (Monday)`. Date-relative reasoning the model does itself (weekday, "now") previously had nothing in the payload naming the account's zone, so fresh agents inferred "now" from the newest `updatedTime` and sometimes reported the wrong day. The zone is already resolved for rendering, so this adds no API calls, and it lands on both the stdio and Worker entry points. (#151, closes #150)
Comment thread README.md

The primary tool for task management. Supports all Motion API parameters including `name`, `description`, `priority`, `dueDate`, `duration`, `labels`, `assigneeId`, and `autoScheduled`. You can reference workspaces and projects by name — the server resolves them automatically.

`list_all_uncompleted` spans every workspace in one call (it ignores `workspaceId`/`workspaceName`) and honors the `dueDate` and `priority` filters, so "what's due this week across all my workspaces?" resolves directly. On `list`, `dueDate` is an inclusive on-or-before-day bound that includes overdue tasks (so `dueDate: "today"` answers "what's due today?"), and `completedAfter` / `completedBefore` bound by completion date in your account's time zone for "what did I get done this week?". Dates are interpreted in your Motion account's time zone, and list responses lead with a header naming that zone and today's local date.
@claude

claude Bot commented Aug 24, 2026

Copy link
Copy Markdown

Review

Docs-only PR, verified against main. Every factual claim in the diff checks out against the current implementation:

  • motion_statuses is indeed in the essential tier (ToolRegistry.ts:75-87), matching the "now 8 tools" claim.
  • list_all_uncompleted does thread dueDate/priority through per-workspace queries (TaskHandler.ts ~577-611).
  • completedAfter/completedBefore exist on list and are validated via parseFilterDate (TaskHandler.ts:331-345).
  • formatScheduleList prints per-day working hours exactly as described, including the "recurring templates only, no calendar events" caveat (responseFormatters.ts:500-545).
  • The account-timezone header format quoted in the CHANGELOG (Account timezone: America/Denver | Today: 2026-08-24 (Monday)) is an exact match for formatAccountDateContext (dateFormat.ts:100-124).
  • wrangler.toml does have [observability.logs] / invocation_logs = true.

No code changes, so no bugs/perf/security concerns to raise there. A couple of very minor nits, neither blocking:

  1. Changelog heading convention: this PR introduces a ### ✨ Added section, but every prior release in this changelog uses ### 🚀 New Features for the equivalent content (see 2.6.0, 2.5.0, 2.4.0, 2.3.0, etc.). Might be worth matching the existing heading for consistency, unless there's an intentional shift toward Keep-a-Changelog-style categories going forward.
  2. README motion_schedules line is a bit long (single paragraph covering hours, caveat, and a suggested workaround) — readable as-is, but could optionally be split into two sentences for scannability. Not necessary.

Nice catch on the stale motion_schedules description ("conflict detection and workload breakdowns") — that was inaccurate for what the tool actually returns, and the new copy correctly reflects the working-hour-template behavior in formatScheduleList.

Overall: accurate, well-scoped, no issues found. Approving from a docs-accuracy standpoint.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants