Added calendar events, move contacts, and extensions commands

[guilhermeyo]

Hi,

I use hey-cli and fizzy-cli, so the code was familiar. Added some commands I wanted for myself.

Didn't touch the SDK. Everything goes through the legacy client with form-encoded POSTs that handle 302 redirects, same as the web UI. Tried the endpoints with curl first.

What I added

hey event — calendar events

hey event list
hey event create "Meeting" --date 2026-04-06 --start 10:00 --end 11:00
hey event create "Holiday" --date 2026-04-06 --all-day
hey event create "Standup" --date 2026-04-06 --start 09:00 --end 09:30 --reminder 30m --reminder 1d
hey event edit <id> --title "New title" --start 14:00 --end 15:00
hey event delete <id>

List goes through the SDK (Calendars().GetRecordings). Create/edit/delete hit /calendar/events via the legacy client since those return 302s.

hey move — move contacts between boxes

hey move <topic-id> --box feedbox
hey move --contact <contact-id> --box trailbox

Gets the contact from the topic creator via Topics().Get, posts to /boxes/{id}/designations. Asks for confirmation unless you pass --yes.

hey ext — email extensions

hey ext list
hey ext create sales --member user@domain.com
hey ext edit <id> --name support
hey ext delete <id> --yes

List scrapes HTML at /accounts/{id}/domains/extenzions because there's no JSON endpoint. Account ID comes from Identity().GetIdentity. Edit/delete use POST with _method override.

How it's built

• Legacy client extended with PostForm, PatchForm, Delete for 302 redirects
• Followed existing code structure
• Unit tests with httptest servers
• --json on everything

Cool thing I found

The API accepts any reminder duration for calendar events, not just the presets in the web UI. I set a reminder days in advance to get notified the morning of an event instead of minutes before, which is really useful.

Code

All on my fork: https://github.com/guilhermeyo/hey-cli/tree/feature/new-commands

Is there any plan to add these natively? I can adjust the hey-sdk and send a PR for each one if that helps. It's been working well for me as is.

[monorkin]

Hey @guilhermeyo a PR to the SDK and the CLI with these additions would be welcome.

[neeldhara]

+1, accessing hey using hermes agents and the ability to add/modify calendar events would be most helpful!

[guilhermeyo]

Hello @monorkin, I started working on the SDK + CLI PRs for calendar events.

Listing works fine through Calendars().GetRecordings(), pure JSON, no issues.

For mutations, I noticed that todos have a JSON endpoint (POST /calendar/todos.json), which the SDK already uses. But calendar events only have the form-encoded route (POST /calendar/events) used by the web UI with Turbo; POST /calendar/events.json returns 404.

Should I add form-encoded request support to the SDK for these endpoints, or is there a better approach you'd prefer?

[monorkin]

@guilhermeyo I'll take a look at the SDK and try to create any missing methods for you.

[monorkin]

@guilhermeyo I think I added everything you need. Can you check?

[guilhermeyo]

@monorkin Thanks, I will check it.