Skip to content

Writing Time Entries Through a Tool

Source: hooks/ways/ea/tasks/time/entries/entries.md

Frontmatter
Field Value
description posting time entries to Harvest, Toggl, Clockify or Kantata through its api, connector, mcp or cli, checking existing entries on each date so none are duplicated, dry running the post and reading back what landed, and locking in the week only once the user has had a look
vocabulary api connector mcp cli programmatically post entries tracker existing duplicate dry-run read back what have i logged fill in my week from my calendar submit lock it in approver
pattern \b(harvest|toggl|clockify|kantata)\b
refire 0.15
scope agent, subagent

When the time system is reached through an API, an MCP server or a CLI:

  • Resolve each date to YYYY-MM-DD in the time zone the system uses.
  • List the existing entries for a date before writing to it. Hand-entered time and leave are common, and a duplicate costs a correction in the system.
  • Dry run the write where the tool offers one, then commit, then list the date again and report what landed. A commit can partly fail.
  • When the tool cannot update, delete or submit, say so and point to the system's own interface. Pass account-policy errors to the human.

Submitting

Submitted time is hard to undo, and submission often locks the period. Leave logged entries unsubmitted until the human confirms the hours. A request to log and submit covers both steps, but propose the entries first when the hours are estimates. Before submitting a week, list the whole period and flag weekdays with gaps.

See Also

  • tasks/time(ea) — parent: proposing entries and logging on approval
  • trust/delegation(meta) — submitted time carries the human's name