Use case
I want an agent using hey-cli to answer "What is on my schedule today?"
The result should be the same events that I see in HEY Calendar Day View.
Would you be open to a PR for this? If so, could I get some direction on what would you'd prefer?
Some implementation details that come to mind:
- Add typed occurrences in
hey-sdk
- Following the existing
occurrences_url through the SDK’s generic Get
- New endpoint that represents HEY Day View
Steps to reproduce
hey recordings
- Look at Day View
I expected to see only events in Day View in hey recordings output.
wgj@wgj-mba ~ % hey recordings 842516 --starts-on 2026-08-10 --ends-on 2026-08-11
warning: system keyring unavailable, credentials stored in plaintext at /Users/wgj/.config/hey-cli/credentials.json
Calendar::Event:
ID Title Starts Ends
169129265 GSD 2026-08-10T15:00 2026-08-10T16:00
168443092 Reading Lesson 2026-07-28T21:00 2026-07-28T21:30
167608775 Cook Dinner 2026-07-21T19:00 2026-07-21T20:30
167584206 GSD 2026-04-27T15:00 2026-04-27T16:00
wgj@wgj-mba ~ % hey recordings 842544 --starts-on 2026-08-10 --ends-on 2026-08-11
warning: system keyring unavailable, credentials stored in plaintext at /Users/wgj/.config/hey-cli/credentials.json
Calendar::Event:
ID Title Starts Ends
166875844 Jiu Jitsu 2026-07-10T18:00 2026-07-10T19:30
166875837 Randori 2026-05-30T16:00 2026-05-30T17:30
166875839 Babysitting both 2026-03-22T22:30 2026-03-23T01:30
166875834 State of the Triad 2026-02-06T00:00 2026-02-06T01:00
166875831 House cleaning 2026-01-15T17:00 2026-01-15T20:00
166875780 Jiu-Jitsu Orientations 2026-01-07T23:45 2026-01-08T00:45
166875782 ***** Birthday 2024-08-18T00:00 2024-08-18T00:00
166875785 *************** birthday 2024-05-09T00:00 2024-05-09T00:00
166875818 State of the Triad 2022-11-18T00:00 2022-11-18T01:00
166875823 D/scussion 2020-09-27T01:00 2020-09-27T03:00
Current gap
Testing showed that:
GetRecordings can omit unrealized recurring events shown in Day View.
- The occurrences response can omit ordinary one-time events.
- Realized events can appear in both responses.
- Both responses can include events outside the requested day.
Neither endpoint is sufficient by itself.
Proposed PR
I'd like to add a day-view sub command, that has parity with HEY's Day View.
hey day-view [YYYY-MM-DD]
hey day-view 2026-08-10 --calendar 123 --calendar 456
The command would:
- Use the HEY account time zone.
- Use all calendars by default.
- Include timed, all-day, multi-day, and recurring events.
- Exclude non-event records and Nighttime.
- Merge recordings and occurrences.
- Filter to the requested day.
- Deduplicate by id or occurrence_id, never by title and time.
- The existing recordings command would remain unchanged.
Use case
I want an agent using
hey-clito answer "What is on my schedule today?"The result should be the same events that I see in HEY Calendar Day View.
Would you be open to a PR for this? If so, could I get some direction on what would you'd prefer?
Some implementation details that come to mind:
hey-sdkoccurrences_urlthrough the SDK’s genericGetSteps to reproduce
hey recordingsI expected to see only events in Day View in
hey recordingsoutput.Current gap
Testing showed that:
GetRecordingscan omit unrealized recurring events shown in Day View.Neither endpoint is sufficient by itself.
Proposed PR
I'd like to add a
day-viewsub command, that has parity with HEY's Day View.The command would: