Repository navigation
feat(calendar): propose an event from a date said in an asset, sent only once approved - #688
Merged
Merged
Conversation
…nly once approved
A date said in an asset ("let's meet next Tuesday at 3") can be proposed as
an event for a Google Calendar connection an admin let add events: Propose
event under Dates said in the Entities tab, POST /api/v1/dates/propose, or
the MCP tool propose_event. The event is prefilled from the line (the day
at a time said in it, else all day; the line as its title; the addresses it
names and an email's sender and recipients, not emailed unless asked) and
waits in Approvals as an add_event. Only the person, signed in, approves
it; an API key, an app, MCP and the assistant can only decline, and
declining does nothing. GET /api/v1/dates says whether proposing is offered.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QFUNzy1QZy5HhKAyJxTAYJ
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Adeel · project thread
Description
Before: dates said in an asset ("let's meet next Tuesday at 3") were read as days, but turning one into a calendar event meant retyping it in the calendar.
After: next to each date said (the Entities tab, under Dates said), Propose event makes an event for a Google Calendar connection an admin let add events. It is prefilled from the line: the day said, at a time said in it ("at 3" is 15:00) or all day; the line as its title; and who it names (for an email, its sender and recipients), never emailed unless asked. It waits in Approvals as an
add_event, and nothing is added or sent until the person approves it there, signed in. Declining does nothing. Agents propose throughPOST /api/v1/dates/proposeand the MCP toolpropose_event, and can decline but never approve.GET /api/v1/datessays whether proposing is offered.How:
domain/event_proposals.pybuilds the event from the date's line and files it through the existing approvals flow and the Google Calendar write path.Motivation and Context
Item from the personal feature plan sheet (dates said become calendar proposals).
Screenshots (if appropriate):
n/a
Steps to reproduce (if appropriate):
With a Google Calendar connection allowed to add events and dates-said reading on, open an asset that says "let's meet next Tuesday at 3", choose Propose event under Dates said, then approve it in Approvals: the event appears in the calendar on that Tuesday at 15:00.
Types of changes
!in the title)Checklist:
make hookschecks it on commit).tests/api/test_event_proposals.py,tests/api/test_mcp.py,__tests__/said-dates.test.tsx).docs/accordingly (docs/processing.md#propose-an-event,docs/mcp.md,docs/assistant.md,docs/automations.md).## UnreleasedinCHANGELOG.md. Written aschangelog.d/date-proposals.md, per build(release): changelog fragments in changelog.d/ instead of one Unreleased section #581.Done questions (AGENTS.md)
POST /api/v1/dates/proposeand MCPpropose_event; agents can decline but not approve..envedit or manual step. Offered only where a calendar connection already allows adding events.docs/requirements.mdname the checks.make openapi, no drift).Local CI: the container runs several times slower than usual, so I ran the changed tests directly:
test_event_proposals.py,test_dates.py,test_mcp.py,test_setup_assistant.py,test_scaling_agents.py(71 passed),said-dates.test.tsx(3 passed). ruff, mypy, tsc and the threat model validator are clean, andmake openapishows no drift. GitHub CI decides the merge.Generated by Claude Code